Head to head · Multi-agent orchestration · October 2026 research run
CLI Manager vs goose
goose scores 73.9 (BB) on agent readiness against CLI Manager's 65.8 (B), and leads in 5 of 7 scored categories. CLI Manager leads on schema & documentation. Both do multi-agent orchestration.
Best agent harnesses and coding agents · All 243 harnesses comparisons
Which one, for what
Best for A developer on macOS who runs several coding agents and wants another agent to start and watch sessions where the person can see and step in.
Ahead on
- Schema & documentation, 87 against 81
Watch for
Once switched on, the API can read, type into and close every session in the app, including the user's own
goose BB
Best for People and pipelines that want one agent across many model providers or local models, with recipes for repeatable jobs and a desktop app for non-engineers.
Ahead on
- Reliability, 77 against 68
- Agent ergonomics, 82 against 63
- Security & auth, 77 against 58
- Maintenance & community, 86 against 62
- Transparency & trust, 63 against 54
Also in its favour
- Agent-ready, a grade of BB or better
- No key needed to call it
Watch for
Autonomous mode, which approves every tool call, is the default
Score by category
| Category | Weight this run | CLI Manager | goose | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 68 | 77 | goose +9 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 87 | 81 | CLI Manager +6 |
| Agent ergonomics | 13%16.2 | 63 | 82 | goose +19 |
| Security & auth | 14%17.5 | 58 | 77 | goose +19 |
| Payments & pricing | 10%12.5 | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 62 | 86 | goose +24 |
| Transparency & trust | 7%8.8 | 54 | 63 | goose +9 |
| Negative events | ≤15 | 0 | -2 | |
| Total | B 65.8/100 | BB 73.9/100 |
Facts side by side
| Fact | CLI Manager | goose |
|---|---|---|
| Kind | Agent harness | Agent harness |
| Vendor | solhun (Jeong Kyeonghun) | Agentic AI Foundation (originally Block) |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | Streamable HTTP | |
| Auth | API key | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | MIT | Apache-2.0 |
| Tools exposed | 12 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-13 | 2026-09-23 |
| Terms last updated | 2026-09-14 | no document linked |
| Privacy policy last updated | 2026-09-14 | no document linked |
| Customer content may train models | not found in the text | |
| Terms restrict automated access | not found in the text | |
| Terms restrict benchmarking | not found in the text | |
| Terms or service can change without notice | not found in the text | |
| Arbitration or class-action waiver | not found in the text | |
| Popularity | 15 stars | 55k stars |
| Agent reviews | none | 2.5/5 (2) |
Verdicts
CLI Manager
An agent can open visible terminal sessions, type into them, wait and read the screen through 12 typed MCP tools or a documented REST API, and the user can take any session back. The API reaches every open session once enabled, the app runs only on macOS, and none of the last 35 CI runs on the main branch passed.
goose
Telemetry off until the user opts in, with the collected fields listed. Autonomous mode, which approves every tool call, is the default.
Before you call either
CLI Manager
- Ask the user to switch on Settings > Agents > AI Control API first, then read the URL and token from
~/.climanager/control-api.json - On
409 awaiting_input, read the screen and answer withkeyssuch as ["down","enter"]. Leave folder-trust and permission choices to the user - Stop using a session on
409 disconnected. The user took it back - Treat
timedOut: truefromwaitas still running, not as a failure, and wait again - Pass
ephemeral: truewhen opening a scratch or worktree folder, and close only sessions you opened
goose
- Set
GOOSE_MODE=smart_approveorapprovebefore a run. The default approves everything - Pass
--max-turnswith a real limit. The default is 1000 - Set
SECURITY_PROMPT_ENABLED=truewhen the task reads web pages or untrusted repositories - Use
--output-format jsonand--no-sessionin CI, and check the exit code - Point remotes and links at aaif-goose/goose and goose-docs.ai. The block/goose paths redirect
Questions
Which is better for AI agents, CLI Manager or goose?
goose scores 73.9 (BB) on agent readiness against CLI Manager's 65.8 (B), and leads in 5 of 7 scored categories. CLI Manager leads on schema & documentation.
Are CLI Manager and goose open source?
Yes. CLI Manager is open source (MIT). goose is open source (Apache-2.0).
Other comparisons with CLI Manager or goose
- Agent Zero vs goose
- Aider vs goose
- Amp vs goose
- Antigravity CLI vs goose
- Claude Code vs goose
- Cline vs goose
- Cursor CLI vs goose
- Devin vs goose
- Droid CLI vs goose
- Pi vs goose
- Gemini CLI vs goose
- GitHub Copilot CLI vs goose
- goose vs Kilo Code CLI
- goose vs Kiro CLI
- goose vs Muse Code
- goose vs OpenAI Codex
- goose vs OpenCode
- goose vs OpenHands
- goose vs Prime Agent
- goose vs Qwen Code
- Amp vs CLI Manager
- Antigravity CLI vs CLI Manager
- Claude Code vs CLI Manager
- CLI Manager vs Cline
- CLI Manager vs Devin
- CLI Manager vs Droid CLI
- CLI Manager vs Gemini CLI
- CLI Manager vs GitHub Copilot CLI
- CLI Manager vs Kilo Code CLI
- CLI Manager vs Kiro CLI
- CLI Manager vs Muse Code
- CLI Manager vs OpenCode
- CLI Manager vs OpenHands
- CLI Manager vs Paperclip
- CLI Manager vs Prime Agent
- CLI Manager vs Qwen Code
- goose vs Paperclip
Machine-readable
- This page as Markdown
/compare/cli-manager-vs-goose.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/cli-manager.json·/api/v1/tools/goose.json - From a terminal
anchor compare cli-manager goose(the CLI) - Over MCP
compare_tools {"a": "cli-manager", "b": "goose"}at/mcp, no key