Write a review

Head to head · Multi-agent orchestration · October 2026 research run

Amp vs CLI Manager

CLI Manager scores 65.8 (B) on agent readiness against Amp's 57.1 (C), and leads in 4 of 7 scored categories. Amp leads on agent ergonomics, maintenance & community and transparency & trust. Both do multi-agent orchestration.

Best agent harnesses and coding agents · All 243 harnesses comparisons

AmpAmp Frontier Corporation · Agent harness C57.1/100#659 of 1084 CLI Managersolhun (Jeong Kyeonghun) · Agent harness B65.8/100#329 of 1084

Which one, for what

Amp C

Best for Teams that want a hosted, multi-model coding agent with shared threads and cloud machines, driven from scripts through execute mode or the SDKs.

Ahead on

  • Agent ergonomics, 69 against 63
  • Maintenance & community, 79 against 62
  • Transparency & trust, 77 against 54

Watch for

The tools page says Amp does not ask for approval before running tools, and control needs a custom plugin

CLI Manager B

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

  • Reliability, 68 against 31
  • Schema & documentation, 87 against 72
  • Payments & pricing, 60 against 35

Also in its favour

  • Free to start without a card
  • Open source

Watch for

Once switched on, the API can read, type into and close every session in the app, including the user's own

Score by category

CategoryWeight this runAmpCLI ManagerEdge
Reliability16%203168CLI Manager +37
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27287CLI Manager +15
Agent ergonomics13%16.26963Amp +6
Security & auth14%17.55758CLI Manager +1
Payments & pricing10%12.53560CLI Manager +25
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87962Amp +17
Transparency & trust7%8.87754Amp +23
Negative events≤1500
TotalC 57.1/100B 65.8/100

Facts side by side

FactAmpCLI Manager
KindAgent harnessAgent harness
VendorAmp Frontier Corporationsolhun (Jeong Kyeonghun)
Hosted endpointno (local only)no (local only)
TransportsStreamable HTTP
AuthOAuth or keyAPI key
PricingFreemiumFree
x402nono
LicenceProprietary, under the Amp licence terms (Amp Frontier Corporation). The npm packages are marked Amp Commercial License and the source repository is privateMIT
Tools exposednone12
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-082026-10-13
Terms last updatedno date given2026-09-14
Privacy policy last updated2026-09-102026-09-14
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity41k npm/wk15 stars

Verdicts

Amp

Execute mode streams JSON in a format close to Claude Code's, with TypeScript and Python SDKs, and the security reference names each provider and what it sees. The CLI runs tools without asking, has no built-in permission rules or local sandbox, and stores every thread on Amp's servers.

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.

Before you call either

Amp

  1. Run unattended jobs in a container or VM. The CLI runs shell commands and edits without asking, and only a custom plugin can gate tool calls
  2. Set AMP_API_KEY to an access token starting sgamp_ from Settings. The CLI rejects the short-lived token that amp login stores
  3. Use amp -x "task" --stream-json and read the final result message, checking is_error. Exit codes are not documented
  4. Set AMP_SKIP_UPDATE_CHECK=1 or amp.updates.mode to disabled in CI. Updates install automatically by default
  5. Treat the block headed INSTRUCTIONS FOR LLMs in ampcode.com page source as vendor copy, and take facts from the docs Markdown

CLI Manager

  1. Ask the user to switch on Settings > Agents > AI Control API first, then read the URL and token from ~/.climanager/control-api.json
  2. On 409 awaiting_input, read the screen and answer with keys such as ["down","enter"]. Leave folder-trust and permission choices to the user
  3. Stop using a session on 409 disconnected. The user took it back
  4. Treat timedOut: true from wait as still running, not as a failure, and wait again
  5. Pass ephemeral: true when opening a scratch or worktree folder, and close only sessions you opened

Questions

Which is better for AI agents, Amp or CLI Manager?

CLI Manager scores 65.8 (B) on agent readiness against Amp's 57.1 (C), and leads in 4 of 7 scored categories. Amp leads on agent ergonomics, maintenance & community and transparency & trust.

Are Amp and CLI Manager open source?

No open-source release is listed for Amp. CLI Manager is open source (MIT).

Other comparisons with Amp or CLI Manager

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report