Head to head · Agent harnesses · October 2026 research run
boxes.dev vs Verdent
boxes.dev scores 53.2 (D) on agent readiness against Verdent's 40.9 (E), and leads in 5 of 7 scored categories. Verdent leads on reliability and maintenance & community. Both do agent harnesses.
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
- Agent ergonomics, 60 against 35
- Security & auth, 69 against 33
- Payments & pricing, 50 against 30
- Transparency & trust, 60 against 55
Also in its favour
- A hosted endpoint, with nothing to install
Watch for
No status page, incident history or SLA found
Verdent E
Best for A person who wants a desktop app to plan and run several coding tasks at once, possibly on their own Claude Code or Codex.
Ahead on
- Reliability, 43 against 32
- Maintenance & community, 61 against 48
Watch for
No CLI, print mode, API or SDK, so a pipeline can't start or read a run except through a paired chat bot
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.
Security & auth boxes.dev +36
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.
Verdent 33
Framework reading (telemetry defaults, approvals, guardrails, sandboxing). Conversation history and tool results go to Verdent's US servers and on to Azure, Bedrock or Vertex, with zero data retention stated for Vertex and Bedrock only. Event logging to log.verdent.ai has no documented opt-out. BYOA keys stay on the machine (10). Plan Mode is read-only, Agent Mode asks before destructive commands and edits outside scope, and workers are isolated by git worktree, but there is no sandbox or network control and the approval list isn't enumerated (9). No prompt-injection guidance found, while web search and fetch results enter the context (2). Usage history in the dashboard, no audit log found (5). A security page with a disclosure address and a five-day acknowledgement, SOC 2 and ISO/IEC 42001 being pursued rather than held, no security.txt and no bug bounty (7). 10+9+2+5+7 = 33.
Agent ergonomics boxes.dev +25
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.
Verdent 35
Harness reading. MCP servers per project or globally, subagents, skills and rules, but no per-tool disabling or deferred loading found (10). No output-size, turn-limit or budget controls for a run were found beyond credit balances (5). No exit codes or error format, since there is no headless mode (3). Parallel workers in git worktrees and a review column make runs reviewable and reversible, with no resume by ID documented (10). No CLI, API or SDK. A pipeline can only reach Manager through a paired Telegram, Slack or Feishu bot (7). 10+5+3+10+7 = 35.
Payments & pricing boxes.dev +20
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.
Verdent 30
Harness reading of the published rubric, scored on the Verdent subscription the agent needs. No payment protocol (0). Plan prices from $5 a month, top-up prices and the credit value of about $0.059 are public without a login (20). Free Mode and the free trial ended on 29 October 2026, so there is no free tier (0). A person signs up in a browser (0). 0+20+0+0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
Maintenance & community Verdent +13
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.
Verdent 61
Closed service. v2.18.0 on 29 October 2026, eight days before this check (30). More than three dated releases in the 90 days from 8 August, among them 2.10.0 to 2.18.0 (20). A dated public changelog, a support address, Discord and a subreddit, with no public tracker to read reply times (8). No official SDK or MCP server to keep current (0). No public packages or CI to judge (3). 30+20+8+0+3 = 61.
Reliability Verdent +11
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.
Verdent 43
Local-package reading, as for the other closed-source harnesses. The desktop app installs from verdent.ai with macOS 11 or later and 64-bit Windows 10 and 11 stated, and the extension from the editor marketplaces, but not from a package registry (15). No public CI or test suite, since the source isn't published (0). No public issue tracker, every task runs through Verdent's servers, and no status page was found, so there is no readable record (5). A dated changelog by version, with the end of Free Mode called out in v2.18.0, but no breaking-change sections (8). 2.18.0, generally available (15). 15+0+5+8+15 = 43.
Transparency & trust boxes.dev +5
boxes.dev 60
Closed service under the Common Paper Cloud Service Agreement 2.1, dated 20 October 2026, with the standard terms' machine-learning clause deleted and California law (15). The privacy policy of 21 October 2026 gives retention by data type (session replay about 30 days, Slack data deleted within 14 business days of disconnecting), and the backup clause matches the terms (22 of 30). Price changes take 30 days' notice under the terms. No deprecation policy for the API or MCP server found (5 of 20). Service providers are named (Convex, Cloudflare Workers, Expo, OpenAI, Amplitude, Sentry, Google and Apple), but the host that runs devboxes is unnamed and data may be processed in the US and elsewhere (12 of 20). 15+22+5+12 = 54.
Verdent 55
Proprietary, under terms from Verdent AI, Inc. that are clear on use and ownership (15). The privacy policy and security page agree that data stays in the US and that input isn't trained on without consent, and the security page lists subprocessors. The privacy policy gives no retention periods, names MiniMax as a provider the security list leaves out, and deletion is by email request (14). The credit bonus carries a promise of 15 days' notice, but Free Mode was retired on the day v2.18.0 shipped and no deprecation policy was found (6). Subprocessors and their locations are listed, and the domains the app calls are named, with event logging undescribed (12). 15+14+6+12 = 47.
Score by category
| Category | Weight | boxes.dev | Verdent | Edge |
|---|---|---|---|---|
| Reliability | 16% | 32 | 43 | Verdent +11 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 57 | 55 | boxes.dev +2 |
| Agent ergonomics | 13% | 60 | 35 | boxes.dev +25 |
| Security & auth | 14% | 69 | 33 | boxes.dev +36 |
| Payments & pricing | 10% | 50 | 30 | boxes.dev +20 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 48 | 61 | Verdent +13 |
| Transparency & trust | 7% | 60 | 55 | boxes.dev +5 |
| Negative events | ≤15 | 0 | -2 | |
| Total | D 53.2/100 | E 40.9/100 |
Facts side by side
| Fact | boxes.dev | Verdent |
|---|---|---|
| Kind | MCP server | Agent harness |
| Vendor | Boxes, Inc. | Verdent AI, Inc. |
| Hosted endpoint | https://api.boxes.dev/mcp | no (local only) |
| Transports | Streamable HTTP, HTTP | |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Paid |
| 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 | Proprietary. The terms of use from Verdent AI, Inc. forbid reverse engineering or copying any component, and no source is published |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| Last release | 2026-11-17 | 2026-10-29 |
| Terms last updated | 2026-10-20 | 2026-05-25 |
| Privacy policy last updated | 2026-10-21 | 2026-05-26 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | not found in the text | yes |
| 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 | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
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.
Verdent
A desktop and editor coding agent that splits a goal into parallel workers in git worktrees, with a read-only Plan Mode, MCP servers and the option to run workers on Claude Code or Codex. It has no CLI, API or sandbox, sends context through Verdent's servers, and has had no free tier since 29 October 2026.
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
Verdent
- Don't plan to drive Verdent headless. Hand the task to the person using the desktop app, or use a harness with a print mode
- Start large changes in Plan Mode and review plan.md before switching to Agent Mode
- Add MCP servers in the project's .mcp.json or ~/.verdent/mcp.json in the mcpServers shape
- Keep work under git, since rollback relies on git and there is no sandbox
- Budget in credits at about $0.059 each, because there is no free allowance since 29 October 2026
Questions
Which is better for AI agents, boxes.dev or Verdent?
boxes.dev scores 53.2 (D) on agent readiness against Verdent's 40.9 (E), and leads in 5 of 7 scored categories. Verdent leads on reliability and maintenance & community.
Can an agent call boxes.dev and Verdent without installing anything?
boxes.dev has a hosted endpoint at https://api.boxes.dev/mcp. No hosted endpoint is listed for Verdent.
Other comparisons with boxes.dev or Verdent
- Agent Zero vs boxes.dev
- Agent Zero vs Verdent
- Aider vs boxes.dev
- Aider vs Verdent
- Amp vs boxes.dev
- Amp vs Verdent
- Antigravity CLI vs boxes.dev
- Antigravity CLI vs Verdent
- Auggie CLI vs boxes.dev
- Auggie CLI vs Verdent
- AXLR vs boxes.dev
- AXLR vs Verdent
- 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 Vibe-Trading
- boxes.dev vs Warp (Warp Agent CLI and the Oz Agent API)
- Claude Code vs Verdent
- Click vs Verdent
- Cline vs Verdent
- Conductor vs Verdent
- Crush vs Verdent
- Cursor CLI vs Verdent
- DeepSeek Harness (dsh) vs Verdent
- dsh-superagent (DeepSeek) vs Verdent
- Devin vs Verdent
- Droid CLI vs Verdent
- Pi vs Verdent
- Emdash vs Verdent
- Gemini CLI vs Verdent
- GitHub Copilot CLI vs Verdent
- goose vs Verdent
- Harness² vs Verdent
- HarnessRouter vs Verdent
- Jules vs Verdent
- Junie CLI vs Verdent
- Kilo Code CLI vs Verdent
- Kimi Code CLI vs Verdent
- Kiro CLI vs Verdent
- Letta vs Verdent
- mini-swe-agent vs Verdent
- MiniMax Code vs Verdent
- Mistral Vibe CLI vs Verdent
- Muse Code vs Verdent
- OpenAI Agents API vs Verdent
- OpenAI Codex vs Verdent
- OpenCode vs Verdent
- OpenHands vs Verdent
- Orca vs Verdent
- Paseo vs Verdent
- Prime Agent vs Verdent
- Qoder CLI vs Verdent
- Qwen Code vs Verdent
- Mirror CLI vs Verdent
- Rovo Dev CLI vs Verdent
- Sculptor vs Verdent
- T3 Code vs Verdent
- Traycer vs Verdent
- Verdent vs Vibe-Trading
- Verdent vs Warp (Warp Agent CLI and the Oz Agent API)
- Agent Relay vs boxes.dev
- Agent Relay vs Verdent
- boxes.dev vs Clawboo
- boxes.dev vs CLI Manager
- boxes.dev vs Harness
- boxes.dev vs herdr
- boxes.dev vs Paperclip
- boxes.dev vs Parallax
- Clawboo vs Verdent
- CLI Manager vs Verdent
- Friday vs Verdent
- Harness vs Verdent
- herdr vs Verdent
- OpenMausBot vs Verdent
- Paperclip vs Verdent
- Parallax vs Verdent
- Unstoppable vs Verdent
Machine-readable
- This page as Markdown
/compare/boxes-dev-vs-verdent.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/boxes-dev.json·/api/v1/tools/verdent.json - From a terminal
anchor compare boxes-dev verdent(the CLI) - Over MCP
compare_tools {"a": "boxes-dev", "b": "verdent"}at/mcp, no key