Head to head · Agent harnesses · October 2026 research run
boxes.dev vs Paseo
Paseo scores 65.9 (B) on agent readiness against boxes.dev's 53.2 (D), and leads in 6 of 7 scored categories. boxes.dev leads on security & auth. 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
- 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
Paseo B
Best for Developers who want parallel coding agents on their own machines with no telemetry, reachable from anywhere.
Ahead on
- Reliability, 50 against 32
- Schema & documentation, 65 against 57
- Agent ergonomics, 70 against 60
- Payments & pricing, 90 against 50
- Maintenance & community, 75 against 48
- Transparency & trust, 68 against 60
Also in its favour
- No key needed to call it
- Open source
Watch for
Pre-1.0, at 0.15.3
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 Paseo +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.
Paseo 90
Free self-hosted software with nothing to buy, so 0 for a protocol and 20 each for public pricing, a free tier and onboarding with no sign-up, 60. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.
Maintenance & community Paseo +27
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.
Paseo 75
v0.15.3 and commits on 7 November 2026 (30). More than three releases in 90 days (20). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). Current builds (15). CI on push (10). 30 + 20 + 0 + 15 + 10 = 75.
Reliability Paseo +18
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.
Paseo 50
Local software. Desktop builds, an Android APK, a Docker image and a Nix package (20). ci.yml on the repository; pass state not read (15). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). CHANGELOG.md (15). Version 0.15.3 (0). 20 + 15 + 0 + 15 + 0 = 50.
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.
Paseo 58
Harness reading. The README says no telemetry, tracking or forced log-ins (30 of 30). Worktree per agent, on your own machine (10 of 20). No prompt-injection guidance (5). No audit log (5). SECURITY.md (8). 30 + 10 + 5 + 5 + 8 = 58.
Agent ergonomics Paseo +10
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.
Paseo 70
Harness reading. A self-hosted daemon that agents can use to create worktrees, launch other agents and talk to them, scriptable from the CLI (70).
Schema & documentation Paseo +8
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.
Paseo 65
Harness reading. Public docs, a CLI and plugin examples in the repository (65).
Score by category
| Category | Weight | boxes.dev | Paseo | Edge |
|---|---|---|---|---|
| Reliability | 16% | 32 | 50 | Paseo +18 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 57 | 65 | Paseo +8 |
| Agent ergonomics | 13% | 60 | 70 | Paseo +10 |
| Security & auth | 14% | 69 | 58 | boxes.dev +11 |
| Payments & pricing | 10% | 50 | 90 | Paseo +40 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 48 | 75 | Paseo +27 |
| Transparency & trust | 7% | 60 | 68 | Paseo +8 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 53.2/100 | B 65.9/100 |
Facts side by side
| Fact | boxes.dev | Paseo |
|---|---|---|
| Kind | MCP server | Agent harness |
| Vendor | Boxes, Inc. | Mohamed Boudra |
| Hosted endpoint | https://api.boxes.dev/mcp | no (local only) |
| Transports | Streamable HTTP, HTTP | |
| Auth | OAuth or key | None |
| 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 | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-11-17 | 2026-11-07 |
| Terms last updated | 2026-10-20 | no document linked |
| Privacy policy last updated | 2026-10-21 | no document linked |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
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.
Paseo
A self-hosted, open-source workspace for running many coding agents on your own machines, scriptable from the CLI and reachable from phone, web or desktop, with no telemetry or forced log-in. It's pre-1.0 and run largely by one maintainer.
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
Paseo
- Run the daemon on the machine that has your tools and credentials, and connect from the clients
- Script runs from the CLI for repeatable agent jobs
Questions
Which is better for AI agents, boxes.dev or Paseo?
Paseo scores 65.9 (B) on agent readiness against boxes.dev's 53.2 (D), and leads in 6 of 7 scored categories. boxes.dev leads on security & auth.
Can an agent call boxes.dev and Paseo without installing anything?
boxes.dev has a hosted endpoint at https://api.boxes.dev/mcp. No hosted endpoint is listed for Paseo.
Are boxes.dev and Paseo open source?
No open-source release is listed for boxes.dev. Paseo is open source (Apache-2.0).
Other comparisons with boxes.dev or Paseo
- Agent Zero vs boxes.dev
- Agent Zero vs Paseo
- Aider vs boxes.dev
- Aider vs Paseo
- Amp vs boxes.dev
- Amp vs Paseo
- Antigravity CLI vs boxes.dev
- Antigravity CLI vs Paseo
- Auggie CLI vs boxes.dev
- Auggie CLI vs Paseo
- AXLR vs boxes.dev
- AXLR vs Paseo
- 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 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)
- Claude Code vs Paseo
- Click vs Paseo
- Cline vs Paseo
- Conductor vs Paseo
- Crush vs Paseo
- Cursor CLI vs Paseo
- DeepSeek Harness (dsh) vs Paseo
- dsh-superagent (DeepSeek) vs Paseo
- Devin vs Paseo
- Droid CLI vs Paseo
- Pi vs Paseo
- Emdash vs Paseo
- Gemini CLI vs Paseo
- GitHub Copilot CLI vs Paseo
- goose vs Paseo
- Harness² vs Paseo
- HarnessRouter vs Paseo
- Jules vs Paseo
- Junie CLI vs Paseo
- Kilo Code CLI vs Paseo
- Kimi Code CLI vs Paseo
- Kiro CLI vs Paseo
- Letta vs Paseo
- mini-swe-agent vs Paseo
- MiniMax Code vs Paseo
- Mistral Vibe CLI vs Paseo
- Muse Code vs Paseo
- OpenAI Agents API vs Paseo
- OpenAI Codex vs Paseo
- OpenCode vs Paseo
- OpenHands vs Paseo
- Orca vs Paseo
- Paseo vs Prime Agent
- Paseo vs Qoder CLI
- Paseo vs Qwen Code
- Paseo vs Mirror CLI
- Paseo vs Rovo Dev CLI
- Paseo vs Sculptor
- Paseo vs T3 Code
- Paseo vs Traycer
- Paseo vs Unstoppable
- Paseo vs Verdent
- Paseo vs Vibe-Trading
- Paseo vs Warp (Warp Agent CLI and the Oz Agent API)
- Agent Relay vs boxes.dev
- Agent Relay vs Paseo
- 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 Paseo
- CLI Manager vs Paseo
- Friday vs Paseo
- Harness vs Paseo
- herdr vs Paseo
- OpenMausBot vs Paseo
- Paperclip vs Paseo
- Parallax vs Paseo
Machine-readable
- This page as Markdown
/compare/boxes-dev-vs-paseo.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/boxes-dev.json·/api/v1/tools/paseo.json - From a terminal
anchor compare boxes-dev paseo(the CLI) - Over MCP
compare_tools {"a": "boxes-dev", "b": "paseo"}at/mcp, no key