What is an agent?

An agent is a configured principal that runs inside connect0. Where an MCP client (like Claude Code) acts on your behalf in the moment, an agent is a durable identity you set up once and then invoke — interactively, on a schedule, or from an inbound event. Every run it produces is metered and audited, so you always know what it did and what it cost.

What an agent is made of

Four things compose an agent:

• A persona — the system prompt and behaviour that shape how it responds. Edit it under the agent's Identity and Persona tabs.
• A model — the runtime model it thinks with, chosen from the catalog. See Choosing a model.
• Skills — the tools and capabilities it may call. Agents default closed: an agent can only call what you expose to it.
• Connections — the connectors and credentials it may use. Grant only what the task needs.

You configure each of these on the agent detail page, one tab per concern (Identity, Model, Skills, Tools, Connections, Persona).

Account vs project scope

An agent is an account-level principal, but it operates in the context of a project — that's what scopes its skill and connector resolution. You'll find and manage agents per project at /a/<account>/p/<project>/agents (the Agents Command Center). Runs and conversation threads roll up to the account, which is why usage and audit reporting span your whole account.

Lifecycle

An agent moves through a simple lifecycle: active (the default), locked (its runtime config is frozen and only an owner can change it), and archived (retired). Each run the agent performs has its own state machine — queued → running → succeeded | failed | timeout | budget_blocked | cancelled | awaiting_input — and every transition writes an audit row.

Where to go next

• Create an agent to configure your first one.
• Running agents to dispatch it and watch it work.
• About Zero — the first-party assistant that can set agents up for you.