Local CLIs
Run 25 agent CLIs inside Codey, side by side — with Codey's tools.
The agent CLIs already on your machine are first-class providers. Codey finds them, walks you through connecting the account you already have, and streams their work into a normal session. A local CLI keeps its own model and its own file tools, and gets Codey's workspace on top — browser, design systems, Blueprint, skills, and your MCP servers.
#Detect and connect
#Find what is installed
Open the Providers page and Codey looks each CLI up on your PATH, widening it with the directories CLIs usually install into — ~/.local/bin, ~/.bun/bin, ~/.npm-global/bin, /opt/homebrew/bin, and the Windows scoop and npm prefixes. Each binary is probed with --version before it is listed.
#Sign in with the CLI's own account
Connect runs the CLI's own login command — claude auth login, codex login, and so on. Codey never asks you to paste a vendor key and never bills you for a token. Where a CLI is already authenticated through an environment variable or its own config file, Codey reads that state instead of asking again.
#Enable it in Codey
Installed is not the same as enabled. The Providers page shows the difference — installed and ready, installed but signed out, or absent — and enabling is one action. A CLI that fails to launch is set aside for a minute rather than retried on every call.
#Stream the session
Run it as any other provider: streamed output, full session history, parent and child threads, and the same context breakdown. Resuming a CLI session reuses the CLI's own upstream session id, so context survives the round trip.
#The roster
| CLI | Provider id | Binary checked |
|---|---|---|
| Claude Code CLI | claude-code | claude, openclaude |
| Antigravity CLI | antigravity-cli | agy |
| Codex CLI | codex-cli | codex |
| Amp CLI | amp-cli | amp |
| Codebuddy Code CLI | codebuddy-cli | codebuddy, cbc |
| Cursor Agent CLI | cursor-agent | cursor-agent |
| OpenCode CLI | opencode-cli | opencode-cli, opencode |
| MiMo Code CLI | mimo-cli | mimo |
| GitHub Copilot CLI | github-copilot-cli | copilot |
| Qoder CLI | qoder-cli | qodercli |
| Aider CLI | aider-cli | aider |
| Qwen Code CLI | qwen-code-cli | qwen |
| DeepSeek TUI CLI | deepseek-cli | deepseek, codewhale |
| Grok Build CLI | grok-cli | grok |
| AtomCode CLI | atomcode-cli | atomcode |
| AMR (Vela) CLI | amr-cli | vela |
| Devin for Terminal | devin-cli | devin |
| Hermes CLI | hermes-cli | hermes |
| Kimi CLI | kimi-cli | kimi |
| Kiro CLI | kiro-cli | kiro-cli |
| Kilo CLI | kilo-cli | kilo |
| DeepSeek Reasonix CLI | reasonix-cli | reasonix, dsnix |
| Trae CLI | trae-cli | traecli |
| Mistral Vibe CLI | vibe-cli | vibe-acp |
| Pi CLI | pi-cli | pi |
#Codey tools inside the CLI
A CLI agent has hands on files and a shell. It has no browser, no design catalog, no Blueprint board, and no memory of your skills. For the length of a turn, Codey starts a tools server bound to loopback with a random per-turn token and injects it into the CLI natively — --mcp-config for Claude-family CLIs, mcp_servers.codey_tools settings for Codex, the session mcpServers field for ACP-family CLIs. Nothing is written into the CLI's own settings, and the server dies when the turn ends.
| Bridged tool | What it gives the CLI | Tier |
|---|---|---|
| codey_browser | The managed Desktop browser — the same tabs you are looking at | Pro · Desktop |
| codey_design_system | The design-system catalog and its authoring actions | Pro |
| codey_blueprint | Record an approved plan onto the Blueprint board | Pro |
| codey_websearch | Web search results inside the CLI turn | All tiers |
| codey_skill | The skills library, loaded on demand | All tiers |
| your MCP servers | Every MCP tool Codey has connected, under its own name | As configured |
- Permission travels with the call. Each bridged call is checked against the session's permission rules and its tier before it runs, then renders as a native tool card in your Codey session — same audit as a Codey agent.
- One gate, not two. The CLI's own approval prompts are switched off deliberately, so Codey's rules are the single place you say yes.
- File and shell stay the CLI's. Codey does not bridge its own
read,edit, orbashinto a CLI that already has them. - Nothing to enable. The bridge is implicit on every real model turn. Utility turns — titles and summarization — run without it.
- Billing stays honest. A CLI-driven session costs nothing through Codey; the tokens it reports are the CLI's own, and you pay that account directly.
Enabling a CLI lets that program call Codey's tools on your machine. The bridge lives for one turn, on loopback, behind a per-turn token — but treat every CLI you enable as software you trust.