Build
Admin and Developer create, edit, and delete Agents; Researcher has view access.
Run
Max turns and max execution time bound what an Agent does at runtime.
Reach
Gateway sharing and key scope decide which projects and tools a run can use.
Spend
Budgets cap cost, tokens, and requests per minute, per scope.
Build
The workspace role decides who builds Agents, and the same three roles apply to every Agent in the workspace.
The Agent then carries its own capability scope: the tools, MCP servers, skills, and knowledge bases attached to it. A run reaches what the Agent carries.
Run
An Agent has no identity of its own: every run borrows the identity of the member or key that invokes it, and a key minted for its session carries that caller’s grants. A member’s session carries that member’s role, and an API key carries the key’s grants.- Tool approval: not supported. An Agent runs its tools without waiting for a human decision, and
requires_approvalon a tool andtool_approval_requiredon the Agent have no effect. See Tool approval. - Max turns and max execution time: 100 turns and 600 seconds by default, and execution time counts model thinking only, not tool calls. See Runtime constraints.
- Evaluators and guardrails: attach them to the Agent to score its output. Output guardrails are skipped when the Agent streams, because they cannot run on partial chunks. See Evaluators and Guardrails.
Reach
- MCP gateways: a run reaches the gateways attached to its Agent, each shared with projects. A key minted for an Agent session carries only that Agent’s gateways, and a gateway serves only the tools toggled on its Toolset tab. See Project access and Scope tools.
- API keys: the key’s permission domains, project scope, and
mcp_accessallowlist.mcp_accessis set through the API. A service account key outlives the member who created it, which keeps production runs working when people leave. See API keys.
Spend
- Budgets: cost, token, and requests-per-minute limits on a workspace, project, identity, API key, provider, or model. A request over the limit is rejected with
429. See Budgets. - Rate limits: the workspace plan sets requests per minute, and the daily cap applies on Free. See Rate limits.
Limits
Audit
Changes to Agents and Agent Schedules are recorded in Audit logs under theagent and agent_schedule entities, and each run leaves Traces.