agi-cli (AGI CLI) is an open-source meta-harness that runs every CLI coding agent — Claude Code, Codex, Gemini, Cursor, and more — from one interface. Install it with `curl -fsSL agi-cli.sh | sh`; it lands on your PATH as `agents` (alias `ag`). One install, one config, every agent.

Yes. agi-cli is free and open source under Apache-2.0. It runs agents on your existing subscriptions, so there are no per-token API costs and no agi-cli account — nothing to sign up for.

Which coding agents does agi-cli support?

Claude Code, Codex, Gemini, Cursor, OpenCode, Grok, Kimi, Droid and more — plus any model (Kimi, MiniMax, GLM, Qwen, DeepSeek) through OpenRouter profiles. You run them individually, pin versions per project, or spawn them as parallel teams.

How is agi-cli different from Claude Code?

Claude Code is one agent. agi-cli runs and orchestrates all of them — version-pinned per project like .nvmrc, in parallel teams with boundary contracts, with skills, MCP servers, secrets, and searchable sessions shared across every agent from one config source.

How do I install agi-cli?

Run `curl -fsSL agi-cli.sh | sh`. It works on macOS, Linux, and Windows.

Comparison

agi-cli vs Factory.ai

Factory.ai is a hosted software factory: its Droids take a task, work across a repo, and open a PR on managed infrastructure. agi-cli runs whatever agent you already have, on machines you control.

Muqsit Nawaz · Published July 17, 2026

What Factory.ai does well

Factory.ai sells an agent-native SDLC platform and it operates the whole thing: hosted control plane, remote compute, support SLAs, and an enterprise onboarding motion. Its Droid agent is part of the package — you do not bring an agent, you adopt theirs. Enterprises pay for that, which settles whether the category is real. It is.

Where agi-cli differs

agi-cli spawns the agent you already have — Claude Code, Codex, Gemini, Cursor, Droid, OpenCode — as a local subprocess, in a git worktree, on hardware you own. It is open source (Apache-2.0) and local-first: there is no hosted control plane because there is nothing to host.

agents run claude "work the auth refactor"

When one laptop is not enough, dispatch to a machine you control over SSH — a spare Mac, a VPS, a box on your tailnet. The source is cloned into a worktree on that machine and the logs stream back. No third party in the middle.

agents run claude "run the full test suite" --host mac-mini

Managed cloud is an option, not the default. agents cloud run sends a task to a cloud provider — Rush, Codex, or Factory itself — that clones the repo, does the work, and opens a PR.

agents cloud run "add rate limiting to the API" --provider factory

Side by side

Capability	agi-cli	Factory.ai
Source code stays on your machinesFactory: on-premise is enterprise, contact-sales	yes	partial
Run any agent (Claude Code, Codex, Gemini, Cursor)Factory runs its own Droid agent	yes	no
Open source (Apache-2.0)	yes	no
Bring your own compute — a spare Mac, a VPS, a cluster	yes	partial
Pin agent versions per project	yes	no
Managed cloud, support SLAs, enterprise onboardingthis is where Factory is strong	no	yes

Factory.ai capabilities summarized from its public product, pricing, and Droid Computers pages as of July 2026. Check current terms before relying on any single row.

When Factory is the right call

If you want a managed platform with support, an enterprise onboarding motion, and a team that operates the control plane for you, Factory.ai is built for that and agi-cli is not. agi-cli is per-developer infrastructure: you run it, you host it, you own the uptime. The trade is control for convenience, both directions.

FAQ

Is agi-cli a replacement for Factory.ai?

They are different categories. Factory.ai is a hosted platform that runs its own Droid agent on managed infrastructure. agi-cli is per-developer infrastructure that runs the agents you already have — Claude Code, Codex, Gemini, Cursor — as local subprocesses on machines you control.

Does agi-cli offer managed cloud runs?

Yes, as an option. agents cloud run dispatches a task to a cloud provider — Rush, Codex, or Factory itself — that clones the repo, does the work, and opens a PR. Local runs on your own machines remain the default.

Where does my code run with each tool?

With agi-cli, on your machines: the agent runs as a local subprocess in a git worktree, and remote dispatch goes to machines you own over SSH. With Factory.ai, on Factory's hosted cloud by default; on-premise is an enterprise, contact-sales path.

Try it

curl -fsSL agi-cli.sh/install.sh | sh

Install guide The longer argument →