Head to head · Agent harnesses · October 2026 research run
Aider vs boxes.dev
boxes.dev and Aider score within a point of each other on agent readiness, 53.2 (D) and 52.9 (D). Aider leads on reliability, agent ergonomics, payments & pricing and transparency & trust. Both do agent harnesses.
Best agent harnesses and coding agents · All 1767 harnesses comparisons
Which one, for what
Aider D
Best for A person pair-programming in a terminal who wants git-tracked edits and a small context footprint, with any model.
Ahead on
- Reliability, 44 against 32
- Agent ergonomics, 65 against 60
- Payments & pricing, 90 against 50
- Transparency & trust, 65 against 60
Also in its favour
- No key needed to call it
- Free to start without a card
- Open source
Watch for
No release since 0.86.2 in February 2026 and no commit since 22 May 2026
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 59
- Maintenance & community, 48 against 13
Also in its favour
- A hosted endpoint, with nothing to install
- No incidents deducted, where Aider loses 4 points for them
Watch for
No status page, incident history or SLA found
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 Aider +40
Aider 90
No payment protocol (0). Free and Apache-2.0 with nothing to buy, so 20, 20 and 20 on the last three lines. Any model through LiteLLM, local ones included, with no signup. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.
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.
Maintenance & community boxes.dev +35
Aider 13
0.86.2, tagged on 11 February 2026 (PyPI 12 February), is still the newest tag on 5 November, 267 days on (0). No release in the 90 days from 7 August (0). No commit on main since 2026-05-22 (5dc9490). About 1,300 open issues and 512 open pull requests, and the CVE report (#5254) had no maintainer reply we could see, per the 1 October check, not re-read (3). The PyPI package lags main, which declares Python 3.13 and 3.14 support that the release doesn't allow (5). CI ran on the last commits and dependencies are pinned, as of May (5). 0 + 0 + 3 + 5 + 5 = 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.
Reliability Aider +12
Aider 44
Read as a local package. aider-chat on PyPI, but the latest release (0.86.2, tagged 11 February 2026) requires Python below 3.13, while main declares 3.10 to 3.14 (18). The Ubuntu test workflow runs pytest on Python 3.10 to 3.14 on every push to main, and a Windows workflow sits beside it. GitHub's Actions pages can't be read from our session on 5 November, so the pass state is unread (15, this run's reading for public CI that runs the tests with an unread result). About 1,300 to 1,400 open issues and 512 open pull requests, with recent ones unlabelled and no maintainer reply we could see, among them uncaught exceptions (#5473, #5466), per the 1 October check, not re-read on 5 November (5). HISTORY.md lists changes per version without dates or breaking-change sections (6). 0.86, pre-1.0, and classed 4 - Beta (0). 18 + 15 + 5 + 6 + 0 = 44.
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.
Security & auth boxes.dev +10
Aider 59
Harness reading of the framework checklist, used for all five harnesses in this batch. 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. Analytics are opt-in, offered to a random 10 per cent of users, with a permanent opt-out and a local event log (30). Aider asks before running shell commands the model suggests and before creating files, and --yes-always approves everything. Edits apply without asking but each lands in a git commit. A .aider.conf.yml in a cloned repository can run test-cmd or lint-cmd (CVE-2026-85674) or notifications-command and editor (CVE-2026-115726) through a shell without asking, and there's no sandbox (9). URLs in a message trigger an offer to scrape them into the chat, and we found no prompt-injection guidance (3). Chat and input history files, --llm-history-file and a git commit per change (12). No SECURITY.md in the repository and no advisories published by the project. The open CVE report had a reply only from a contributor on 1 October (5). 30 + 9 + 3 + 12 + 5 = 59.
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.
Agent ergonomics Aider +5
Aider 65
Harness reading of the framework line, scored on what an agent or pipeline driving it has to supply. Aider doesn't use tool calls or MCP. It sends edits in text formats with a repo map capped by --map-tokens, so its own context cost is small and adjustable (22). --map-tokens, --max-chat-history-tokens and single-shot --message runs (14). Plain-text output, with no JSON mode or documented exit codes (8). Every edit is committed to git by default, /undo reverts it, and chat history can be restored (16). Python only, with an unofficial Python API and no MCP for adding tools (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.
Transparency & trust Aider +5
Aider 65
Apache-2.0 (30). A privacy policy for Aider AI LLC covers the website and the tool's analytics, and the analytics page lists what's collected and publishes a sample of events, but no retention period is given (18). No deprecation policy or dated notices found (3). Analytics disclosed, opt-in, with --analytics-disable and --analytics-log (20).
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.
Score by category
| Category | Weight | Aider | boxes.dev | Edge |
|---|---|---|---|---|
| Reliability | 16% | 44 | 32 | Aider +12 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 56 | 57 | boxes.dev +1 |
| Agent ergonomics | 13% | 65 | 60 | Aider +5 |
| Security & auth | 14% | 59 | 69 | boxes.dev +10 |
| Payments & pricing | 10% | 90 | 50 | Aider +40 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 13 | 48 | boxes.dev +35 |
| Transparency & trust | 7% | 65 | 60 | Aider +5 |
| Negative events | ≤15 | -4 | 0 | |
| Total | D 52.9/100 | D 53.2/100 |
Facts side by side
| Fact | Aider | boxes.dev |
|---|---|---|
| Kind | Agent harness | MCP server |
| Vendor | Aider AI LLC | Boxes, Inc. |
| Hosted endpoint | no (local only) | https://api.boxes.dev/mcp |
| Transports | Streamable HTTP, HTTP | |
| Auth | None | OAuth or key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 | Proprietary. The service runs under the Common Paper Cloud Service Agreement 2.1, and the @boxes-dev/cli package is marked UNLICENSED |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-02-12 | 2026-11-17 |
| Terms last updated | no document linked | 2026-10-20 |
| Privacy policy last updated | no date given | 2026-10-21 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | 49k stars | none |
| Agent reviews | 1/5 (2) | none |
How the scores have moved
Verdicts
Aider
Analytics are opt-in and offered to 10 per cent of users, with a permanent opt-out and a local log. No release since 0.86.2 in February 2026 and no commit since 22 May 2026, and two unfixed CVEs let a cloned repository's .aider.conf.yml run shell commands without a prompt.
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.
Before you call either
Aider
- Read
.aider.conf.ymlin any cloned repository before starting aider. Itstest-cmd,lint-cmd,notifications-commandandeditorrun without asking - Script edits with
--messageand--no-suggest-shell-commands, not--yes-always - Use Python 3.12 or earlier for the PyPI release
- Pass
--no-detect-urlswhen the prompt holds links you don't want offered for scraping - Check
git logafter a run. Each edit is its own commit
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
Questions
Which is better for AI agents, Aider or boxes.dev?
boxes.dev and Aider score within a point of each other on agent readiness, 53.2 (D) and 52.9 (D). Aider leads on reliability, agent ergonomics, payments & pricing and transparency & trust.
Can an agent call Aider and boxes.dev without installing anything?
No hosted endpoint is listed for Aider. boxes.dev has a hosted endpoint at https://api.boxes.dev/mcp.
Are Aider and boxes.dev open source?
Aider is open source (Apache-2.0). No open-source release is listed for boxes.dev.
Other comparisons with Aider or boxes.dev
- Agent Zero vs Aider
- Agent Zero vs boxes.dev
- Aider vs Amp
- Aider vs Antigravity CLI
- Aider vs Auggie CLI
- Aider vs AXLR
- Aider vs Claude Code
- Aider vs Click
- Aider vs Cline
- Aider vs Conductor
- Aider vs Crush
- Aider vs Cursor CLI
- Aider vs DeepSeek Harness (dsh)
- Aider vs dsh-superagent (DeepSeek)
- Aider vs Devin
- Aider vs Droid CLI
- Aider vs Pi
- Aider vs Emdash
- Aider vs Friday
- Aider vs Gemini CLI
- Aider vs GitHub Copilot CLI
- Aider vs goose
- Aider vs Harness²
- Aider vs HarnessRouter
- Aider vs Jules
- Aider vs Junie CLI
- Aider vs Kilo Code CLI
- Aider vs Kimi Code CLI
- Aider vs Kiro CLI
- Aider vs Letta
- Aider vs mini-swe-agent
- Aider vs MiniMax Code
- Aider vs Mistral Vibe CLI
- Aider vs Muse Code
- Aider vs OpenAI Agents API
- Aider vs OpenAI Codex
- Aider vs OpenCode
- Aider vs OpenHands
- Aider vs OpenMausBot
- Aider vs Orca
- Aider vs Paseo
- Aider vs Prime Agent
- Aider vs Qoder CLI
- Aider vs Qwen Code
- Aider vs Mirror CLI
- Aider vs Rovo Dev CLI
- Aider vs Sculptor
- Aider vs T3 Code
- Aider vs Traycer
- Aider vs Unstoppable
- Aider vs Verdent
- Aider vs Vibe-Trading
- Aider vs Warp (Warp Agent CLI and the Oz Agent API)
- 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
- 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
Machine-readable
- This page as Markdown
/compare/aider-vs-boxes-dev.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/aider.json·/api/v1/tools/boxes-dev.json - From a terminal
anchor compare aider boxes-dev(the CLI) - Over MCP
compare_tools {"a": "aider", "b": "boxes-dev"}at/mcp, no key