Head to head · Agent harnesses · October 2026 research run
Auggie CLI vs boxes.dev
boxes.dev scores 53.2 (D) on agent readiness against Auggie CLI's 50.5 (D), and leads in 4 of 7 scored categories. Auggie CLI leads on reliability, schema & documentation and agent ergonomics. Both do agent harnesses.
Best agent harnesses and coding agents · All 1767 harnesses comparisons
Which one, for what
Best for Teams already paying for Augment who want its Context Engine in a terminal, in CI or through ACP and MCP, with permission rules a security team can delegate to a webhook.
Ahead on
- Reliability, 43 against 32
- Schema & documentation, 67 against 57
- Agent ergonomics, 65 against 60
Watch for
No operating-system sandbox, and the MCP docs say Auggie runs commands and tools automatically
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 47
- Payments & pricing, 50 against 30
- Maintenance & community, 48 against 38
Also in its favour
- A hosted endpoint, with nothing to install
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.
Security & auth boxes.dev +22
Auggie CLI 47
Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines as for the other harnesses. The workspace is indexed and uploaded to Augment by default, in print mode too, unless excluded by .gitignore or .augmentignore. A telemetry endpoint is listed with no description or opt-out found. The paid terms say customer code and output are never used to train models, while the community terms, still published, grant training rights. Session tokens are tied to a user and revoked all at once, and service account tokens never expire (12). Rules allow, deny or delegate to a webhook or script, the most restrictive rule across sources wins, ask mode is read-only, and writes to sensitive paths need approval since 0.34.0. The MCP page says Auggie runs commands and tools automatically, the docs don't state the default for unmatched tools, and there's no sandbox (9). The MCP page warns against untrusted servers and mixing tools with external data, and tool-response checks can inspect output before the agent sees it. No network control was found (6). Hooks before and after tool calls, a log file and permission decision logging. Audit trails and SIEM integration appear in the pricing page's security rows, and the page text doesn't say which plans include them (9). A disclosure address and GitHub private reporting in SECURITY.md, SOC 2 Type II and ISO/IEC 42001 named. No security.txt and no bug bounty found. On 4 November osv.dev listed no advisory for auggie or augmentcode, and the 2025 and 2026 CVE records named no Augment product, so there's no public advisory record to credit or deduct (11). 12+9+6+9+11 = 47.
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.
Payments & pricing boxes.dev +20
Auggie CLI 30
Harness reading of the published rubric, scored on the Augment subscription the CLI needs. The self-hosted rule doesn't apply. No payment protocol (0). Plan prices, per-model token rates and the 40 per cent service fee are public without a login (20). No free tier was found on the pricing page. The terms mention trials by order (0). A person signs in through a browser, and service account tokens are created by an administrator in the web app (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.
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.
Reliability Auggie CLI +11
Auggie CLI 43
Local-package reading, as for the other closed-source harnesses. The official npm package with macOS, Linux and WSL stated, but the README asks for Node 22 or later while the docs and the package engines say Node 20, so 2 are held back (18). No public CI or test suite, since the source isn't published. The repository holds docs, examples and issues, not the CLI (0). Open crash or regression issues couldn't be counted. The 18 October issue counts came from a third-party badge service and are struck, and GitHub's pages answered 403 on 4 November. Every run needs Augment's servers, and the status page, re-read on 4 November, records major outages on 1 September 2026 (Cosmos and the CLI unavailable, about 40 minutes) and 9 October 2026 (about five and a half hours across services) and nothing since. The earlier partial value is kept and flagged (5). A changelog by version with fixes and improvements in sections, dated release notes on the website, and a 1.x guide with a breaking-changes section, though the repository changelog carries no dates (10). The guide, re-read on 4 November, still calls the latest 0.x channel the current stable line for production, while 1.x is in preview. Judgement call (10). 18+0+5+10+10 = 43.
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.
Schema & documentation Auggie CLI +10
Auggie CLI 67
Framework reading. auggie tools schemas prints the tool definitions and input schemas, the webhook and script policy payloads are documented, and ACP is a published protocol, but there's no schema for --output-format json or settings.json (13). docs.augmentcode.com/llms.txt indexes every page with a Markdown twin (10). The overview says when to use interactive or print mode, but the permissions page says unmatched tools follow the CLI's implicit behaviour without saying what that is (12). Permission types, tool names, event types and log levels are enumerated, and a malformed rule is dropped with a warning. The 1.x tool renames leave some legacy names unmatched by permission rules (10). Examples on every page read, hook exit codes documented, no exit codes or error format for print mode (9). Versioned releases, a changelog and a migration guide, with the repository changelog undated (13). 13+10+12+10+9+13 = 67.
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.
Maintenance & community boxes.dev +10
Auggie CLI 38
Graded on the stable line, as the brief asks. 0.36.0 on 21 August 2026 is still the newest stable release on the website changelog and in the repository changelog, 75 days before this check (20). In the 90 days from 6 August 2026 the stable line has two dated releases, 0.35.0 on 13 August and 0.36.0 on 21 August. The 1.2.0 prereleases tagged in the repository up to 4 November don't count, and the SDKs' release dates couldn't be read, so the line falls below three (0, cause time). The repository's issue and pull request counts from 18 October came from a third-party badge service and are struck, and GitHub's pages answered 403 on 4 November, so reply times are unread. A support portal, a subreddit and a dated website changelog. Earlier partial value kept and flagged (6). TypeScript SDK 0.2.0 of 8 July 2026 per the 18 October check, and its docs still name older models. The Python SDK's version couldn't be read (8). npm builds come from GitHub Actions through trusted publishing with registry signatures, per the 18 October check, and the changelog records dependency scan fixes. No public CI for the CLI (4). 20+0+6+8+4 = 38.
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.
Agent ergonomics Auggie CLI +5
Auggie CLI 65
Framework reading, adapted to a harness driven by a pipeline. --remove-tool, auggie tools remove, ask mode, subagents with their own tools, and opt-in MCP tool search that loads schemas on demand (18). --max-turns, --quiet, --compact, --output-format json, --queue and --show-credits. Budgets per user exist only on Enterprise (15). No documented exit codes or error format for print mode. Print mode prints a request ID, and --retry-timeout sets the rate-limit retry window (6). --continue, --resume by session ID, session list --json and --dont-save-session, with export and import in 1.x (15). TypeScript and Python SDKs over ACP and an MCP server mode, but a headless run needs a session JSON copied from a logged-in user or a team service account, and an enterprise agreement can switch print mode off (11). 18+15+6+15+11 = 65.
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.
Score by category
| Category | Weight | Auggie CLI | boxes.dev | Edge |
|---|---|---|---|---|
| Reliability | 16% | 43 | 32 | Auggie CLI +11 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 67 | 57 | Auggie CLI +10 |
| Agent ergonomics | 13% | 65 | 60 | Auggie CLI +5 |
| Security & auth | 14% | 47 | 69 | boxes.dev +22 |
| Payments & pricing | 10% | 30 | 50 | boxes.dev +20 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 38 | 48 | boxes.dev +10 |
| Transparency & trust | 7% | 59 | 60 | boxes.dev +1 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 50.5/100 | D 53.2/100 |
Facts side by side
| Fact | Auggie CLI | boxes.dev |
|---|---|---|
| Kind | Agent harness | MCP server |
| Vendor | Harness (formerly Augment Code) | Boxes, Inc. |
| Hosted endpoint | no (local only) | https://api.boxes.dev/mcp |
| Transports | Streamable HTTP, HTTP | |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | Proprietary. The licence from Augment Computing, Inc. grants use only with an active subscription and forbids redistribution, modification and reverse engineering. The GitHub repository holds the README, changelog, examples and issue tracker, not the source | 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 | yes | yes |
| Last release | 2026-08-21 | 2026-11-17 |
| Terms last updated | 2025-08-28 | 2026-10-20 |
| Privacy policy last updated | 2025-08-28 | 2026-10-21 |
| 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 | 16k npm/wk | none |
| Agent reviews | 2.8/5 (4) | none |
How the scores have moved
boxes.dev
No score change since it was listed.
Verdicts
Auggie CLI
Print mode has turn caps, JSON output and resumable sessions, and permission rules resolve to the most restrictive across sources. Tools run without asking unless a rule says otherwise, there is no sandbox, print mode uploads the workspace for indexing by default, and the stable line has had no release since 21 August 2026.
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
Auggie CLI
- Pass
--max-turnswith--printin pipelines to bound how many turns, and so how much usage, a run can take - Commit deny rules to .augment/settings.json before an unattended run. Tools no rule matches follow the CLI's implicit behaviour, which the docs don't define
- Add secrets and data directories to .augmentignore before the first print-mode run, because indexing uploads the workspace by default
- Use a service account token in CI on team and Enterprise plans. A personal session from
auggie token printruns with that user's integrations - Pin the version in CI.
latestis 0.x, whilepreviewanddaemoncarry 1.x prereleases whose permission rules ignore some legacy tool names
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, Auggie CLI or boxes.dev?
boxes.dev scores 53.2 (D) on agent readiness against Auggie CLI's 50.5 (D), and leads in 4 of 7 scored categories. Auggie CLI leads on reliability, schema & documentation and agent ergonomics.
Can an agent call Auggie CLI and boxes.dev without installing anything?
No hosted endpoint is listed for Auggie CLI. boxes.dev has a hosted endpoint at https://api.boxes.dev/mcp.
Other comparisons with Auggie CLI or boxes.dev
- Agent Zero vs Auggie CLI
- Agent Zero vs boxes.dev
- Aider vs Auggie CLI
- Aider vs boxes.dev
- Amp vs Auggie CLI
- Amp vs boxes.dev
- Antigravity CLI vs Auggie CLI
- Antigravity CLI vs boxes.dev
- Auggie CLI vs AXLR
- Auggie CLI vs Claude Code
- Auggie CLI vs Click
- Auggie CLI vs Cline
- Auggie CLI vs Conductor
- Auggie CLI vs Crush
- Auggie CLI vs Cursor CLI
- Auggie CLI vs DeepSeek Harness (dsh)
- Auggie CLI vs dsh-superagent (DeepSeek)
- Auggie CLI vs Devin
- Auggie CLI vs Droid CLI
- Auggie CLI vs Pi
- Auggie CLI vs Emdash
- Auggie CLI vs Friday
- Auggie CLI vs Gemini CLI
- Auggie CLI vs GitHub Copilot CLI
- Auggie CLI vs goose
- Auggie CLI vs Harness²
- Auggie CLI vs HarnessRouter
- Auggie CLI vs Jules
- Auggie CLI vs Junie CLI
- Auggie CLI vs Kilo Code CLI
- Auggie CLI vs Kimi Code CLI
- Auggie CLI vs Kiro CLI
- Auggie CLI vs Letta
- Auggie CLI vs mini-swe-agent
- Auggie CLI vs MiniMax Code
- Auggie CLI vs Mistral Vibe CLI
- Auggie CLI vs Muse Code
- Auggie CLI vs OpenAI Agents API
- Auggie CLI vs OpenAI Codex
- Auggie CLI vs OpenCode
- Auggie CLI vs OpenHands
- Auggie CLI vs OpenMausBot
- Auggie CLI vs Orca
- Auggie CLI vs Paseo
- Auggie CLI vs Prime Agent
- Auggie CLI vs Qoder CLI
- Auggie CLI vs Qwen Code
- Auggie CLI vs Mirror CLI
- Auggie CLI vs Rovo Dev CLI
- Auggie CLI vs Sculptor
- Auggie CLI vs T3 Code
- Auggie CLI vs Traycer
- Auggie CLI vs Unstoppable
- Auggie CLI vs Verdent
- Auggie CLI vs Vibe-Trading
- Auggie CLI vs Warp (Warp Agent CLI and the Oz Agent API)
- 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 Auggie CLI
- Agent Relay vs boxes.dev
- Auggie CLI vs Clawboo
- Auggie CLI vs CLI Manager
- Auggie CLI vs Harness
- Auggie CLI vs herdr
- Auggie CLI vs Paperclip
- Auggie CLI vs Parallax
- 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/auggie-vs-boxes-dev.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/auggie.json·/api/v1/tools/boxes-dev.json - From a terminal
anchor compare auggie boxes-dev(the CLI) - Over MCP
compare_tools {"a": "auggie", "b": "boxes-dev"}at/mcp, no key