Loading…
AGI CLI · Coming soon
The agent is a single Rust program, and it does not need a person at the prompt. Put --json-events before the subcommand and stdout becomes JSONL: one object per lifecycle event, covering every tool call, every model rotation, and the token count for each turn. A pipeline reads the run instead of scraping it.
Capabilities
Put --json-events ahead of the subcommand and every lifecycle event lands on stdout as one JSON object: spawning, ready_for_prompt, running_tool, tool_result, message_delta, turn_usage, fallback_triggered, finished. Failures carry a stable kind — api_rate_limit, auth_expired, network, stream_disconnect — so a job can branch on the kind instead of matching an error string.
Runs persist under ~/.agiworkforce/managed_sessions. agi session show prints the turn-by-turn transcript, and agi session fork --at-turn cuts a copy at one user turn under a name you pick with --as. The original stays as it was, and agi --resume picks either of them back up.
macOS uses Seatbelt, Linux uses bubblewrap, and agi sandbox puts a bare command through the same box. When bwrap or sandbox-exec is missing from PATH the run stops and prints the install line for your distribution rather than quietly running unsandboxed.
--no-sandbox suppresses Seatbelt or bwrap and paints a red no sandbox indicator in the TUI footer for as long as it is off. Riskier tool calls still ask before they run, and agi approvals list, allow, deny, session and remove show and edit the answers you saved.
Hooks fire on session start and end, before and after every tool call, on prompt submit, around compaction, and at model resolution, where a hook can swap the model before the request leaves the agent. Slash commands are markdown files under .agiworkforce/commands, and a nested file becomes a namespaced command such as /review:security.
As a client agi connects MCP servers over stdio, SSE, or Streamable HTTP, with OAuth tokens held in the OS credential store. As a server, agi mcp-server speaks the protocol and answers initialize and tools/list, but advertises an empty tool list on purpose — and its own help text says so instead of implying wiring that is not there.
Pass -m with a comma-separated list and a rate limit, a network error, a 5xx, or a dropped stream moves the turn to the next model. The TUI flashes a falling-back banner naming both models and the reason, and a fallback_triggered event goes out on the JSONL stream. Add --demo to watch the rotation fire without waiting for a real 429.
Tokens in and out, cache reads, dollars spent, and context percentage sit in the top-right of the TUI, and the context figure changes color as the window fills. Prices resolve from the shared models catalog rather than a table typed into the CLI.
Subcommands
Aliases exist where they earn their keep: e for exec, a for apply, completions for completion. Run agi with no subcommand and you land in the interactive TUI instead, where --no-tui drops you to the line-based REPL.
| exec | Run a task non-interactively (alias: e) |
| review | Review the working diff, or a range with --base |
| apply | Apply the latest diff as a git patch (alias: a) |
| sandbox | Run a command inside the OS sandbox |
| mcp-server | Speak MCP over stdio; advertises no tools yet |
| app-server | Serve an editor over stdio or a WebSocket |
| resume | Continue a previous session |
| fork | Fork a previous session |
| session | List, show, fork, archive, or delete sessions |
| history | Browse session history |
| models | List, scan, and set model configuration |
| approvals | Manage command and file-operation approvals |
| execpolicy | Show execution policy rules |
| features | Inspect feature flags |
| plugin | List and install plugins |
| marketplace | Search, install, and update marketplace plugins |
| ecosystem | Scan for installed AI tools and import their MCP configs |
| migrate | Import settings from another coding CLI |
| sync | Export and import your settings across machines |
| login | Sign in to AGI cloud, or a provider over OAuth |
| logout | Sign out of AGI cloud |
| auth-status | Show auth status for every configured provider |
| doctor | Run local preflight diagnostics |
| completion | Generate a shell completion script |
| init | Initialize ~/.agiworkforce/ and register the project |
| onboarding | Re-run the first-run onboarding wizard |
At the prompt
Coming soon
When archives are published the download page will show them: it asks the release channel as it loads and lists only the platforms it can confirm, for macOS, Linux and Windows alike. Until then the launch list is the honest way to hear about it, and the permission reference already sets out what the agent may do before it asks.
AGI CLI · Coming soon