Write a review

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

CLI Manager vs Droid CLI

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

Best agent harnesses and coding agents · All 243 harnesses comparisons

CLI Managersolhun (Jeong Kyeonghun) · Agent harness B65.8/100#329 of 1084 Droid CLIFactory · Agent harness C59.1/100#593 of 1084

Which one, for what

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 49
  • Schema & documentation, 87 against 79
  • Payments & pricing, 60 against 10

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

Droid CLI C

Best for Teams that want a terminal coding agent with tiered autonomy, command rules and an optional sandbox, and that will pay for a Factory plan.

Ahead on

  • Agent ergonomics, 72 against 63
  • Security & auth, 63 against 58
  • Maintenance & community, 79 against 62
  • Transparency & trust, 64 against 54

Watch for

No free tier or trial was found. Plans start at $20 a month and included usage is stated only as rolling rate limits without numbers

Score by category

CategoryWeight this runCLI ManagerDroid CLIEdge
Reliability16%206849CLI Manager +19
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28779CLI Manager +8
Agent ergonomics13%16.26372Droid CLI +9
Security & auth14%17.55863Droid CLI +5
Payments & pricing10%12.56010CLI Manager +50
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86279Droid CLI +17
Transparency & trust7%8.85464Droid CLI +10
Negative events≤1500
TotalB 65.8/100C 59.1/100

Facts side by side

FactCLI ManagerDroid CLI
KindAgent harnessAgent harness
Vendorsolhun (Jeong Kyeonghun)Factory
Hosted endpointno (local only)no (local only)
TransportsStreamable HTTP
AuthAPI keyOAuth or key
PricingFreePaid
x402nono
LicenceMITProprietary, under Factory's Terms and Conditions. The droid npm package is marked UNLICENSED and the public repository holds documentation only. The Python SDK is Apache-2.0
Tools exposed12none
Read-only variant documentednoyes
llms.txtyesyes
Last release2026-10-132026-10-08
Terms last updated2026-09-142026-07-14
Privacy policy last updated2026-09-142026-08-20
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 textyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity15 stars49 stars, 7.8k npm/wk

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.

Droid CLI

droid exec is read-only unless --auto raises the autonomy level, with command rules, an optional kernel-enforced sandbox, JSON output and documented exit codes. No free tier, status page or security.txt was found, the source is closed, and usage metrics go to Factory by default.

Before you call either

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

Droid CLI

  1. Set FACTORY_API_KEY (starts fk-) from the API keys page in Factory settings for headless runs. Interactive use signs in through a browser
  2. Start with droid exec and no flags for analysis. Add --auto low for edits and --auto medium for installs, tests and local commits
  3. Use --output-format json and read is_error, num_turns and session_id. Treat a non-zero exit code as failure
  4. Set sandbox.enabled to true before running on untrusted code. In droid exec a sandbox violation is denied without a prompt
  5. Pin the version in CI with npm install -g droid@<version>, or set FACTORY_DROID_AUTO_UPDATE_ENABLED=false on standalone installs, which update themselves

Questions

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

CLI Manager scores 65.8 (B) on agent readiness against Droid CLI's 59.1 (C), and leads in 3 of 7 scored categories. Droid CLI leads on agent ergonomics, security & auth, maintenance & community and transparency & trust.

Are CLI Manager and Droid CLI open source?

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

Other comparisons with CLI Manager or Droid CLI

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