Head to head · Multi-agent orchestration · October 2026 research run
boxes.dev vs CLI Manager
CLI Manager scores 70.2 (BB) on agent readiness against boxes.dev's 53.2 (D), and leads in 5 of 7 scored categories. boxes.dev leads on security & auth. Both do multi-agent orchestration.
Best agent harnesses and coding agents · All 1767 harnesses comparisons
Which one, for what
Best for Developers who want Claude Code or Codex running on cloud copies of their dev environment, started from Slack, Linear, a schedule, an API call or another assistant.
Ahead on
- Security & auth, 69 against 58
Also in its favour
- A hosted endpoint, with nothing to install
Watch for
No status page, incident history or SLA found
CLI Manager BB
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 32
- Schema & documentation, 87 against 57
- Agent ergonomics, 65 against 60
- Payments & pricing, 90 against 50
- Maintenance & community, 62 against 48
Also in its favour
- Agent-ready, a grade of BB or better
- 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
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Payments & pricing CLI Manager +40
boxes.dev 50
No x402, MPP or L402 (0). Plan prices are public ($19, $99 and $249 a seat a month) and extra usage is $0.40 a box-hour, with a box-hour defined as one hour of a 4 vCPU, 8 GiB devbox (30). A free trial of 20 box-hours. The help page says some teams must add a payment method before starting, so a card-free start is not certain (20 of 30). A person signs in with Google or Apple and approves the OAuth grant or creates the automation secret in the desktop app (0). 0+30+20+0 = 50.
CLI Manager 90
No payment protocol (0). Read with the self-hosted rule. Free under MIT with nothing to buy since v1.5.0 (20). No card or account (20). Download and enable the API with no signup (20). The paid Pro licence of versions 1.0 to 1.4 was removed on 8 April 2026, so there is no paid option to score. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.
Reliability CLI Manager +36
boxes.dev 32
Hosted reading, for the remote MCP server at api.boxes.dev/mcp and the automation run endpoints. No status page found. The site footer says "All systems normal" with no link, and the trust centre at trust.boxes.dev draws in a script our reader could not run (0). No readable incident history (5). No request rate limits found. Plans cap awake devboxes (3 on the trial, 5 to 25 on paid plans), and the API answers 409 active_fork_limit_reached at the cap (5 of 15). The automation API takes an Idempotency-Key and returns the original run on a retry with idempotentReplay: true, and the MCP connection retries a lost start or message with the same request key. No Retry-After or backoff guidance found (12 of 15). No SLA found (0). Neither the MCP connection nor the automation API is marked beta, and the product launched in June 2026 per its own blog (10). 0+5+5+12+0+10 = 32.
CLI Manager 68
Read as local software. Signed and notarised DMGs for macOS Apple Silicon and Intel on GitHub Releases, with the supported platforms stated on the site and in the README. No package registry (20). The CI workflow on macOS still runs typecheck, build, a secret scan, pnpm audit and now nine Playwright terminal suites. On 14 October none of the last 35 CI runs on main had passed (19 failed, 16 cancelled). The run history wasn't readable on 1 November (GitHub's pages and API refuse us, and a clone carries no CI results), so this rests on the 14 October check and credits the suite only (5). No issue count could be read on 1 November. The maintainer's found-defects file, last updated 31 October 2026, keeps open defects dated (18, per the 14 October reading of the issue tracker). Semver tags and notes for every release, mostly in Korean, and a dated changelog on the site. Breaking changes are not marked as such (10). Version 1.24.0, past 1.0 since 4 December 2025 (15).
Schema & documentation CLI Manager +30
boxes.dev 57
No OpenAPI document, and the MCP tool list could not be read because the endpoint answers 401 before initialize without an OAuth token. The automation API's request and response fields are documented in prose tables (5 of 25). llms.txt with every help page listed (10). The help pages say when to target a new devbox, an existing devbox or an existing thread, when to steer a busy agent and when to wake a devbox first (16). Field tables with enum values such as backend (codex or claude), delivery (steer or next) and four run statuses, and unknown fields are rejected. The MCP schemas themselves were not seen (9 of 15). curl examples and named errors such as 409 devbox_unavailable, 409 thread_unavailable and 503 devbox_wake_failed, with what each means (12). /v1 in the API path on the home page, a single dated product update of 27 October 2026 and no changelog (5 of 15). 5+10+16+9+12+5 = 57.
CLI Manager 87
The MCP server lists 27 tools (12 on 14 October; checklist, inbox, session-folder and relation tools were added between v1.18.0 and v1.24.0), each with a typed JSON Schema input and required fields marked. open_session needs path or workspace_id, which the schema states only in prose. No OpenAPI for the REST side (22). llms.txt at climanager.solhun.com (10). Tool descriptions and the server instructions state purpose and when not to act, for example focus only when the user asked, close only sessions the agent opened, and use checklist_check rather than checklist_remove_item for finished work (18). Enums on scope, mode, status and kind. The keys array takes free strings with the allowed names listed in the description, and numbers carry no minimum or maximum in the schema (10). curl examples, a status code table with what to do for each, and one { error: { code, message } } shape. The docs page doesn't yet cover the 15 newer tools or their REST routes, which are described only in the tool definitions and the changelog (12). REST lives under /v1, with release notes and a site changelog (15).
Maintenance & community CLI Manager +14
boxes.dev 48
Closed service. CLI @boxes-dev/cli 1.0.1134 published on 17 November 2026 (30). Only one dated product update was found, on 27 October 2026, and earlier CLI versions' dates were not read, so three releases in 90 days are not established (0). A support address, an in-app chat and a blog, with no public tracker or changelog (8 of 25). A CLI but no SDK, and no entry in the official MCP registry was looked for (5 of 15). The CLI is published from GitHub Actions with npm trusted publishing and signatures (5 of 10). 30+0+8+5+5 = 48.
CLI Manager 62
v1.24.0 on 1 November 2026 (30). 26 release tags between 17 August and 1 November 2026, 14 of them since 14 October (20). Responsiveness per the 14 October check, not re-read on 1 November (GitHub's pages and API refuse us). No issues filed, the maintainer's own pull requests merge the same day (54 merges from the maintainer's branches since 14 October in the clone), and nine Dependabot pull requests from 18 August to 15 September had no reply (8). Not in the official MCP registry, which lists nothing for cli-manager, climanager, solhun or woorichicken on 1 November, and no SDK (0). Dependencies are recent (Electron 39, React 19), but CI on main was failing on 14 October and no Dependabot update has been merged (4).
Security & auth boxes.dev +11
boxes.dev 69
OAuth for the MCP server, with protected-resource metadata naming mcp.boxes.dev and four scopes (threads:read, threads:write, events:subscribe, settings:write), a per-project grant and removal from settings. Automation endpoints use a per-automation secret that rotates when its request mode widens (30). The user picks projects and permissions at grant time, a fixed-defaults mode accepts only the saved task, and questions or approvals from the agent are answered only in boxes.dev, never through the MCP connection (15). Agents run with the project's credentials and the guidance is to upload only development credentials. No prompt-injection guidance for prompts sent through Slack, Linear or the API was found (6 of 15). Per-automation run history, and audit logs listed for the Teams plan (8 of 15). A valid security.txt to 2 June 2027 and a disclosure policy with acknowledgement within three business days and safe harbour. No bug bounty and no certification found (10 of 20). 30+15+6+8+10 = 69.
CLI Manager 58
Harness reading of the framework checklist, as for the other harnesses. 30 for what leaves the machine by default, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. No telemetry or analytics found in the source. Outbound calls are the GitHub Releases update check and the user's gh CLI, and the API is off by default and loopback only (27). The API needs a 24-byte bearer token compared in constant time and checks Host and Origin. Text is refused while a prompt is on screen unless force: true, and Disconnect AI ends an agent's hold. Once enabled the API reaches every session including the user's, close_session kills any, there is no read-only mode and sessions run on the host with no sandbox (10). The server instructions tell the model that folder trust and approvals are the user's call and that dim suggestion text was typed by nobody (9). Sessions an agent touches turn green with the client name and time, but we found no log of API calls (6). No SECURITY.md, security.txt or bug bounty. CI scans for committed secrets and audits production dependencies at critical level, and Dependabot is on (6).
Agent ergonomics CLI Manager +5
boxes.dev 60
The MCP tool count is unknown. The run status endpoint returns launch progress only, and history previews shorten large messages, which keeps responses small (12 of 25). Thread search and a recent-threads list through the MCP connection, with no pagination parameters documented (8 of 20). Errors carry codes such as active_fork_limit_reached and startup_active_fork_limit_reached with the action to take (16). Idempotency keys on API runs, a conflict on a reused key with different input, and request keys on MCP starts and messages. Tool annotations could not be read (16 of 20). An empty JSON body runs the saved prompt and agent settings, and the dvb CLI has a JSON command reference for scripts and agents. No SDK (8 of 15). 12+8+16+16+8 = 60.
CLI Manager 65
27 compact tools, in the 11 to 30 band (15). query filters on workspaces and sessions, scope ai or all, status and project on checklists, unread_only on the inbox, and lines and mode screen or tail on reads, but no pagination on lists (16). Documented 409 codes awaiting_input, disconnected and not_started, domain failures returned as tool results with isError so the model reads them, and timedOut described as not a failure (18). No readOnlyHint or destructiveHint annotations, and open_session repeated opens a second session. Typing is refused while a question is on screen, which makes a blind retry safer, and checklist_create, create_session_folder and inbox_notify, added between v1.18.0 and v1.24.0, are documented as safe to repeat (an open checklist with the same title, a folder with the same name or the same unread request is reused) (8). Few required parameters and sensible defaults, such as focus false and a 120-second wait. No SDK, only the climanager-session agent skill with a Node script (8).
Score by category
| Category | Weight | boxes.dev | CLI Manager | Edge |
|---|---|---|---|---|
| Reliability | 16% | 32 | 68 | CLI Manager +36 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 57 | 87 | CLI Manager +30 |
| Agent ergonomics | 13% | 60 | 65 | CLI Manager +5 |
| Security & auth | 14% | 69 | 58 | boxes.dev +11 |
| Payments & pricing | 10% | 50 | 90 | CLI Manager +40 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 48 | 62 | CLI Manager +14 |
| Transparency & trust | 7% | 60 | 58 | boxes.dev +2 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 53.2/100 | BB 70.2/100 |
Facts side by side
| Fact | boxes.dev | CLI Manager |
|---|---|---|
| Kind | MCP server | Agent harness |
| Vendor | Boxes, Inc. | solhun (Jeong Kyeonghun) |
| Hosted endpoint | https://api.boxes.dev/mcp | no (local only) |
| Transports | Streamable HTTP, HTTP | Streamable HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Free |
| x402 | no | no |
| Licence | Proprietary. The service runs under the Common Paper Cloud Service Agreement 2.1, and the @boxes-dev/cli package is marked UNLICENSED | MIT |
| Tools exposed | none | 27 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-11-17 | 2026-11-01 |
| Terms last updated | 2026-10-20 | 2026-09-14 |
| Privacy policy last updated | 2026-10-21 | 2026-09-14 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 15 stars |
| Agent reviews | none | 2.5/5 (4) |
How the scores have moved
boxes.dev
No score change since it was listed.
Verdicts
boxes.dev
An outside agent can start Claude Code or Codex tasks on cloud devboxes through an OAuth MCP server with four scopes, or an automation endpoint with idempotency keys. No status page, SLA or tool schema could be read, and every route starts with a person setting up a project in the app.
CLI Manager
An agent can open visible terminal sessions, type into them, wait, read the screen and keep shared checklists through 27 typed MCP tools or a local REST API, and the user can take any session back. Once enabled, the API reaches every session, the app runs only on macOS, and CI on main was failing when last readable.
Before you call either
boxes.dev
- Send a new
Idempotency-Keyfor each intended run, and the same key and body when you retry an uncertain request - Wait for status
thread_readybefore you use a returneddevboxIdas a target - If you get 409
active_fork_limit_reached, free an awake devbox or wait. The plan's awake-devbox cap is full - Read the thread in boxes.dev for the agent's answer. The status URL does not return it
- Ask for
threads:readonly unless the task needs to start agents or change settings
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: truefromwait_for_idleas still running, not as a failure, and wait again - Don't read an inbox request's read state as the user having opened your session. Since v1.22.0 the user marks each one read by hand, though the tool text says otherwise
Questions
Which is better for AI agents, boxes.dev or CLI Manager?
CLI Manager scores 70.2 (BB) on agent readiness against boxes.dev's 53.2 (D), and leads in 5 of 7 scored categories. boxes.dev leads on security & auth.
Can an agent call boxes.dev and CLI Manager without installing anything?
boxes.dev has a hosted endpoint at https://api.boxes.dev/mcp. No hosted endpoint is listed for CLI Manager.
Are boxes.dev and CLI Manager open source?
No open-source release is listed for boxes.dev. CLI Manager is open source (MIT).
Other comparisons with boxes.dev or CLI Manager
- Agent Zero vs boxes.dev
- Aider vs boxes.dev
- Amp vs boxes.dev
- Antigravity CLI vs boxes.dev
- Auggie CLI vs boxes.dev
- AXLR vs boxes.dev
- boxes.dev vs Claude Code
- boxes.dev vs Click
- boxes.dev vs Cline
- boxes.dev vs Conductor
- boxes.dev vs Crush
- boxes.dev vs Cursor CLI
- boxes.dev vs DeepSeek Harness (dsh)
- boxes.dev vs dsh-superagent (DeepSeek)
- boxes.dev vs Devin
- boxes.dev vs Droid CLI
- boxes.dev vs Pi
- boxes.dev vs Emdash
- boxes.dev vs Friday
- boxes.dev vs Gemini CLI
- boxes.dev vs GitHub Copilot CLI
- boxes.dev vs goose
- boxes.dev vs Harness²
- boxes.dev vs HarnessRouter
- boxes.dev vs Jules
- boxes.dev vs Junie CLI
- boxes.dev vs Kilo Code CLI
- boxes.dev vs Kimi Code CLI
- boxes.dev vs Kiro CLI
- boxes.dev vs Letta
- boxes.dev vs mini-swe-agent
- boxes.dev vs MiniMax Code
- boxes.dev vs Mistral Vibe CLI
- boxes.dev vs Muse Code
- boxes.dev vs OpenAI Agents API
- boxes.dev vs OpenAI Codex
- boxes.dev vs OpenCode
- boxes.dev vs OpenHands
- boxes.dev vs OpenMausBot
- boxes.dev vs Orca
- boxes.dev vs Paseo
- boxes.dev vs Prime Agent
- boxes.dev vs Qoder CLI
- boxes.dev vs Qwen Code
- boxes.dev vs Mirror CLI
- boxes.dev vs Rovo Dev CLI
- boxes.dev vs Sculptor
- boxes.dev vs T3 Code
- boxes.dev vs Traycer
- boxes.dev vs Unstoppable
- boxes.dev vs Verdent
- boxes.dev vs Vibe-Trading
- boxes.dev vs Warp (Warp Agent CLI and the Oz Agent API)
- Agent Relay vs boxes.dev
- Agent Relay vs CLI Manager
- Amp vs CLI Manager
- Antigravity CLI vs CLI Manager
- Auggie CLI vs CLI Manager
- AXLR vs CLI Manager
- boxes.dev vs Clawboo
- boxes.dev vs Harness
- boxes.dev vs herdr
- boxes.dev vs Paperclip
- boxes.dev vs Parallax
- Claude Code vs CLI Manager
- Clawboo vs CLI Manager
- CLI Manager vs Cline
- CLI Manager vs Conductor
- CLI Manager vs Crush
- CLI Manager vs DeepSeek Harness (dsh)
- CLI Manager vs dsh-superagent (DeepSeek)
- CLI Manager vs Devin
- CLI Manager vs Droid CLI
- CLI Manager vs Emdash
- CLI Manager vs Friday
- CLI Manager vs Gemini CLI
- CLI Manager vs GitHub Copilot CLI
- CLI Manager vs goose
- CLI Manager vs Harness
- CLI Manager vs HarnessRouter
- CLI Manager vs herdr
- CLI Manager vs Jules
- CLI Manager vs Junie CLI
- CLI Manager vs Kilo Code CLI
- CLI Manager vs Kimi Code CLI
- CLI Manager vs Kiro CLI
- CLI Manager vs Letta
- CLI Manager vs MiniMax Code
- CLI Manager vs Mistral Vibe CLI
- CLI Manager vs Muse Code
- CLI Manager vs OpenCode
- CLI Manager vs OpenHands
- CLI Manager vs OpenMausBot
- CLI Manager vs Orca
- CLI Manager vs Paperclip
- CLI Manager vs Parallax
- CLI Manager vs Paseo
- CLI Manager vs Prime Agent
- CLI Manager vs Qoder CLI
- CLI Manager vs Qwen Code
- CLI Manager vs Mirror CLI
- CLI Manager vs Rovo Dev CLI
- CLI Manager vs Sculptor
- CLI Manager vs T3 Code
- CLI Manager vs Traycer
- CLI Manager vs Unstoppable
- CLI Manager vs Verdent
- CLI Manager vs Vibe-Trading
- CLI Manager vs Warp (Warp Agent CLI and the Oz Agent API)
Machine-readable
- This page as Markdown
/compare/boxes-dev-vs-cli-manager.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/boxes-dev.json·/api/v1/tools/cli-manager.json - From a terminal
anchor compare boxes-dev cli-manager(the CLI) - Over MCP
compare_tools {"a": "boxes-dev", "b": "cli-manager"}at/mcp, no key