Named agents
Describe an agent in a plain file: what it is for, an optional model, and the tools it may use. Scoped to one project or shared globally. /agents lists, filters, and invokes them in the CLI.
Loading features...
Loading features...
AGI Agents
An agent in AGI is a tool-using session you can hand work to: it reads files, runs commands, uses connectors, and reports back. What it may touch is set by explicit permissions, risky actions pause for approval, and the route it runs on is always visible.
How delegation works
Describe an agent in a plain file: what it is for, an optional model, and the tools it may use. Scoped to one project or shared globally. /agents lists, filters, and invokes them in the CLI.
Fan a task out to subagents that work simultaneously. Each reports running, completed, failed, or cancelled, and returns its output along with the files it modified.
Risky actions pause and ask first. The CLI raises an approval overlay before a tool runs, and Desktop puts the same explicit consent in front of MCP connectors and tools.
In the CLI, tool execution runs inside OS-level sandboxing. Seatbelt on macOS, bubblewrap on Linux. Turning the sandbox off is a loud, deliberate choice.
Lifecycle hooks fire across a session: before and after tool calls, on prompt submit, on stop. Wire your own guardrails, logs, and automations around an agent.
Schedule recurring runs and dispatch work with AGI Work. Scheduled and Dispatch are built in on AGI Desktop, the local-private compute host.
Where agents run
Agents live where the work is: the terminal, the desktop, the editor, and the browser. Every surface keeps the same rule: explicit permissions, visible routes.
| CLI | The agi binary: resumable sessions, named agents and subagents, hooks, and sandboxed execution. Works offline with local models. |
| Desktop | The local-private compute host: AGI Work Scheduled and Dispatch, MCP connectors, and tool approvals. |
| VS Code | @agi in the editor with workspace-scoped context and diff review before changes land. |
| Chrome | A side panel that captures page context on request and hands real work to Desktop over a paired bridge. |
Boundaries
Local, BYOK, and AGI Cloud are separate trust boundaries for agents too. A Local session never silently continues on your keys or managed compute. Moving work elsewhere is an explicit, visible step. AGI Cloud stays invite-only.
Start now
Download AGI for Local and BYOK agent work on Desktop and CLI. Join the waitlist for AGI Cloud. It opens by invite.