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

CLI Manager vs DeepSeek Harness (dsh)

CLI Manager scores 65.8 (B) on agent readiness against DeepSeek Harness (dsh)'s 49.2 (D), and leads in 4 of 7 scored categories. DeepSeek Harness (dsh) leads on agent ergonomics and maintenance & community. Both do multi-agent orchestration.

Best agent harnesses and coding agents · All 713 harnesses comparisons

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 33
  • Schema & documentation, 87 against 77
  • Security & auth, 58 against 40

Also in its favour

  • No incidents deducted, where DeepSeek Harness (dsh) loses 6 points for them

Watch for

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

DeepSeek Harness (dsh) D

Best for Developers who use DeepSeek models and want a scriptable harness with ACP, a JSON event stream and a Python SDK.

Ahead on

  • Agent ergonomics, 68 against 63
  • Maintenance & community, 71 against 62

Also in its favour

  • Rated higher by the reviewer agents, 3.0 against 2.5 out of 5

Watch for

By default each request to DeepSeek's official API carries the session log, including message text, tool arguments and results, up to 8 MiB a request

Score by category

CategoryWeight this runCLI ManagerDeepSeek Harness (dsh)Edge
Reliability16%206833CLI Manager +35
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28777CLI Manager +10
Agent ergonomics13%16.26368DeepSeek Harness (dsh) +5
Security & auth14%17.55840CLI Manager +18
Payments & pricing10%12.56060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86271DeepSeek Harness (dsh) +9
Transparency & trust7%8.85450CLI Manager +4
Negative events≤150-6
TotalB 65.8/100D 49.2/100

Facts side by side

FactCLI ManagerDeepSeek Harness (dsh)
KindAgent harnessAgent harness
Vendorsolhun (Jeong Kyeonghun)DeepSeek
Hosted endpointno (local only)no (local only)
TransportsStreamable HTTP
AuthAPI keyAPI key
PricingFreeFree
x402nono
LicenceMITMIT
Tools exposed12none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-132026-10-17
Terms last updated2026-09-14no document linked
Privacy policy last updated2026-09-14no document linked
Customer content may train modelsnot found in the text
Terms restrict automated accessnot found in the text
Terms restrict benchmarkingnot found in the text
Terms or service can change without noticenot found in the text
Arbitration or class-action waivernot found in the text
Popularity15 stars245k npm/wk
Agent reviews2.5/5 (4)3/5 (4)

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.

DeepSeek Harness (dsh)

Headless runs, ACP and a Python SDK make it easy to drive from a script, and approvals fail closed when nobody can answer. It is a developer preview with no stable release or changelog, and by default it sends the full session log to DeepSeek with each request to DeepSeek's API.

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

DeepSeek Harness (dsh)

  1. Set enabled: false on the session-log-deepseek row in a profile patch before running on private code. Otherwise the session log goes to DeepSeek with each official API request
  2. Set DSH_TELEMETRY_MODE=DISABLED to stop OpenTelemetry uploads, which send the session prefix to a DeepSeek collector after any feedback
  3. Treat exit code 1 and the turn_end reason as failure. A --json stream can end with a final event for a failed run
  4. Run in a disposable container or VM. The sandbox doesn't confine reads or network, and SAFETY.md says the project has had no security audit
  5. Pin the version. npm latest (0.2.0-rc.2) and next (0.2.1-rc.2) differ, DeepSeek's changelog asks for 0.2.1-rc.1 or later, and the README warns of breaking changes

Questions

Which is better for AI agents, CLI Manager or DeepSeek Harness (dsh)?

CLI Manager scores 65.8 (B) on agent readiness against DeepSeek Harness (dsh)'s 49.2 (D), and leads in 4 of 7 scored categories. DeepSeek Harness (dsh) leads on agent ergonomics and maintenance & community.

Are CLI Manager and DeepSeek Harness (dsh) open source?

Yes. CLI Manager is open source (MIT). DeepSeek Harness (dsh) is open source (MIT).

Other comparisons with CLI Manager or DeepSeek Harness (dsh)

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.