Write a review

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

CLI Manager vs Kilo Code CLI

Kilo Code CLI scores 75.4 (BB) on agent readiness against CLI Manager's 65.8 (B), and leads in 6 of 7 scored categories. CLI Manager leads on payments & pricing. 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 Kilo Code CLIKilo Code Inc. · Agent harness BB75.4/100#51 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

  • Payments & pricing, 60 against 50

Watch for

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

Kilo Code CLI BB

Best for Developers who want an open-source terminal agent with per-tool permission rules, an optional sandbox and a choice of provider, and the same engine in VS Code and JetBrains.

Ahead on

  • Reliability, 85 against 68
  • Agent ergonomics, 72 against 63
  • Security & auth, 66 against 58
  • Maintenance & community, 87 against 62
  • Transparency & trust, 76 against 54

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

Telemetry to PostHog is on by default, and the privacy policy and PRIVACY.md don't mention it

Score by category

CategoryWeight this runCLI ManagerKilo Code CLIEdge
Reliability16%206885Kilo Code CLI +17
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28790Kilo Code CLI +3
Agent ergonomics13%16.26372Kilo Code CLI +9
Security & auth14%17.55866Kilo Code CLI +8
Payments & pricing10%12.56050CLI Manager +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86287Kilo Code CLI +25
Transparency & trust7%8.85476Kilo Code CLI +22
Negative events≤1500
TotalB 65.8/100BB 75.4/100

Facts side by side

FactCLI ManagerKilo Code CLI
KindAgent harnessAgent harness
Vendorsolhun (Jeong Kyeonghun)Kilo Code Inc.
Hosted endpointno (local only)no (local only)
TransportsStreamable HTTP
AuthAPI keyOAuth or key
PricingFreeFreemium
x402nono
LicenceMITMIT
Tools exposed12none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-132026-10-07
Terms last updated2026-09-142026-09-30
Privacy policy last updated2026-09-142026-05-29
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularity15 stars28k stars, 33k 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.

Kilo Code CLI

Shell commands ask before running by default, and an optional operating-system sandbox blocks writes outside the workspace and outbound network. Telemetry to PostHog is on by default and the sandbox is off, so an unattended kilo run --auto approves everything not denied unless both are configured first.

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

Kilo Code CLI

  1. Set sandbox.enabled to true in the global kilo.jsonc before kilo run --auto. --auto approves every permission request not explicitly denied
  2. Set experimental.openTelemetry to false, or KILO_TELEMETRY_LEVEL to a value other than all, to stop telemetry
  3. Add needed hosts to sandbox.allowed_hosts in global config. MCP tool calls are unavailable while network restriction is on
  4. Without --auto a non-interactive run rejects every permission prompt and exits 1
  5. Put provider keys in global config or the environment. {env:VAR} in a project kilo.json is ignored

Questions

Which is better for AI agents, CLI Manager or Kilo Code CLI?

Kilo Code CLI scores 75.4 (BB) on agent readiness against CLI Manager's 65.8 (B), and leads in 6 of 7 scored categories. CLI Manager leads on payments & pricing.

Are CLI Manager and Kilo Code CLI open source?

Yes. CLI Manager is open source (MIT). Kilo Code CLI is open source (MIT).

Other comparisons with CLI Manager or Kilo Code 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