Async Governance GlossaryDefinition

What Is AI agent?

Last updated: April 2026

Definition

An AI agent is a software entity that takes actions toward a goal with some degree of autonomy. Unlike a passive AI assistant that responds to direct prompts, an agent maintains state across steps, plans sequences of actions, and operates without continuous human input.

The defining property of an agent is action, not generation. A chatbot generates text. An agent does things — calls APIs, edits files, makes commitments, sends messages. That difference creates a different governance question: not what did the AI say, but what is the AI allowed to do.

In organizational contexts, the central question for agents is authority. An agent that acts on behalf of a person or team must have explicit, scoped, and revocable authority — declared in advance, not inferred from convenience.

Why AI agent Matters for Distributed Teams

Most organizational risk from AI is not from what AI says — it is from what AI does without authority. An agent that takes action on a real system without explicit authority creates accountability gaps that no amount of post-hoc review can fix.

The safe operating model treats AI agents the way the operating model treats human delegates: with declared scope, time-bounded authority, and clear audit trails.

Frequently Asked Questions

What is an AI agent?

An AI agent is a software entity that takes actions toward a goal with some degree of autonomy. Unlike a passive assistant that only generates text, an agent maintains state, plans sequences of steps, and operates with reduced human input.

How is an AI agent different from a chatbot?

A chatbot generates text in response to prompts. An AI agent takes actions — calling APIs, editing files, sending messages. The difference is whether the system does things or only says things.

Related Terms

Get the vocabulary that makes distributed teams work

One email per week on async governance. No spam.

See ai agent in action.

StandIn is built around these concepts. Engineers publish declared state before going offline. The next shift starts with full context.