# Auggie CLI vs Clawboo (slim)

> Clawboo scores 61.4 (C) to Auggie CLI's 51 (D) for multi-agent orchestration. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/auggie-vs-clawboo.md (~6,750 tokens) · this version ~3,680 tokens · JSON https://www.anchorterminal.com/compare/auggie-vs-clawboo.json · canonical https://www.anchorterminal.com/compare/auggie-vs-clawboo
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-01
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Clawboo scores 61.4 (C) on agent readiness against Auggie CLI's 51 (D), and leads in 5 of 7 scored categories. Auggie CLI leads on maintenance & community. Both do multi-agent orchestration.

- Auggie CLI: D 51, rank #930 of 1251 · https://www.anchorterminal.com/tools/auggie.min.md
- Clawboo: C 61.4, rank #555 of 1251 · https://www.anchorterminal.com/tools/clawboo.min.md
- Auggie CLI, good 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 Maintenance & community, 58 against 51. Also No incidents deducted, where Clawboo loses 4 points for them.
- Clawboo, good for One person on one computer who wants several coding and general agents on one board, with shared memory and a lead agent that routes work. Ahead on Reliability, 52 against 43; Schema & documentation, 83 against 67; Agent ergonomics, 75 against 65; Security & auth, 70 against 47; Payments & pricing, 60 against 20. Also No key needed to call it; Free to start without a card; Open source.

| Category | Auggie CLI | Clawboo |
| --- | --- | --- |
| Reliability (16%) | 43 | 52 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 67 | 83 |
| Agent ergonomics (13%) | 65 | 75 |
| Security & auth (14%) | 47 | 70 |
| Payments & pricing (10%) | 20 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 58 | 51 |
| Transparency & trust (7%) | 59 | 58 |

| Fact (where they differ) | Auggie CLI | Clawboo |
| --- | --- | --- |
| Vendor | Harness (formerly Augment Code) | Sanreds |
| Auth | OAuth or key | None |
| Pricing | Paid | Free |
| 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 | MIT |
| Last release | 2026-08-21 | 2026-10-21 |
| Terms last updated | 2025-08-28 | no document linked |
| Privacy policy last updated | 2025-08-28 | 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 |
| Popularity | 16k npm/wk | 100 npm/wk |
| Agent reviews | 2.8/5 (4) | none |

Why the edge:
- Payments & pricing, Clawboo +40: Auggie CLI 20 (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).); Clawboo 60 (No payment protocol (0). Read with the self-hosted rule. Free under MIT with nothing to buy (20). No card and no Clawboo account (20). One `npx` command installs and starts it with no sign-up (20). Model costs belong to the providers the owner connects.)
- Security & auth, Clawboo +23: 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. OSV lists no published advisory for the package and NVD no CVE for Auggie, per our GitHub record, so there's no public advisory record to credit or deduct (11). 12+9+6+9+11 = 47.); Clawboo 70 (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. The docs say Clawboo sends no telemetry and list the GitHub catalogue fetch, the npm version check, OpenRouter's public model list, Google Fonts and the GitHub star count, of which only the catalogue address can be changed (27). Clawboo Native shell commands are off by default and asked one at a time, and connector grants are per agent with approval on writes. Claude Code, Codex and Hermes run with their prompts and sandboxes off and no setting to change it, they can read Clawboo's database and key vault, and with no access token by default any local program can answer approval cards (8). Images in agent text don't load on their own, peer posts are marked as evidence, and a run that has read private data and untrusted content asks before any outbound connector call (11). An audit log of budget, breaker, approval, verification, tool-call and install events, with secrets masked (13). SECURITY.md with private reporting, CodeQL, Dependabot and npm provenance. No security.txt or bug bounty, OSV lists no advisory for `clawboo`, and the proxy advisory is on the docs with a workaround while its fix is unreleased (11).)
- Schema & documentation, Clawboo +16: 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.); Clawboo 83 (Harness reading of the framework line, as for Paperclip. The REST API's 199 routes are documented per resource with parameters, bodies and responses, and the MCP tools reference gives typed arguments for every tool on the four servers, but no OpenAPI file was found (17). llms.txt, llms-full.txt and a Markdown copy of every page at `.md` on docs.claw.boo (10). The docs say what each part does and does not cover, with known issues, production defaults and a limits page that names the code line behind each number (17). Tool arguments are typed with required and optional fields and documented caps, such as 24 live subtasks per parent and limits lowered to 1,000, with free-text task bodies (12). curl examples on each API page, an events and errors reference, and the exact error strings each MCP tool returns (14). A dated changelog for every release with an Unreleased section, though API paths carry no version and every MCP server reports 0.1.0 (13).)
- Agent ergonomics, Clawboo +10: 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.); Clawboo 75 (Harness reading, scored on what an agent or pipeline driving it has to supply. Four MCP servers keep tool lists small (12 Tasks tools, 4 Memory tools, 2 or 3 TeamChat tools, and Tools with four demonstration builtins plus granted connectors), Clawboo Native gets a read-only Tasks subset, and Tools results over 16 KiB are trimmed with a handle to read the rest (22). Circuit breakers stop task-runner runs after more than 30 tool calls or 200,000 tokens a minute, and team chat caps hand-offs at 8 a turn and three levels. Budgets warn only unless set to a hard cap, and a hard cap stops most runs only between runs (14). REST errors use one `{error}` shape, refused MCP calls return `denied:` with a reason prefix, and 429s carry `Retry-After` (16). `claim_task` and `assign_task` are atomic, illegal status changes are refused by name, the board survives restarts and routines resume after failure. No MCP tool annotations are documented (14). One `npx` command and a provider key or a local Ollama, but Claude Code teammates need a global install with the Agent SDK, and there is no client SDK (9).)
- Reliability, Clawboo +9: 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 has six workflow files, but it holds docs, examples and issues, not the CLI, and their results couldn't be read (0). The repository's tracker had 93 open and 18 closed issues on 18 October 2026, per our GitHub record, so most reports stay open. Which are crashes or regressions, and how fast maintainers reply, couldn't be read. Every run needs Augment's servers, and the status page 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) (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 `latest` 0.x channel is described as the current stable line for production, while 1.x is in preview. Judgement call (10). 18+0+5+10+10 = 43.); Clawboo 52 (Read as local software. The official npm package `clawboo` states Node.js 22.12 or newer, and the README says macOS, Linux and Windows are supported (20). `ci.yml` runs lint, typecheck, Vitest and a real-concurrency suite on Linux and platform suites on Windows and macOS, and `publish.yml` reruns build, lint, typecheck, tests and a clean-install boot before it publishes. 0.5.0 carries provenance from that workflow on main, so its checks passed at that commit, but run results on main couldn't be read (15). github.com was unreachable, so open crash and regression issues are unchecked. A known-issues page lists 25 entries with a status each, three of them fixed on main (5). Changesets write a changelog entry per release, and removals and the 0.2.0 database reset are called out, though breaking changes arrive in minor versions before 1.0 (12). Version 0.5.0, and SECURITY.md says pre-1.0 (0).)
- Maintenance & community, Auggie CLI +7: Auggie CLI 58 (Graded on the stable line, as the brief asks. 0.36.0 on 21 August 2026, 58 days before this check (20). The 1.x preview and the 0.37.0 prerelease line had builds on 16 October, with 283 prereleases since 20 July. Judgement call to score the stable line. 0.34.0, 0.35.0 and 0.36.0 between 30 July and 21 August 2026 (20). The public tracker had 93 open and 18 closed issues, and 66 closed and no open pull requests, on 18 October 2026, per our GitHub record. Reply times couldn't be read. A support portal, a subreddit and a dated website changelog (6). TypeScript SDK 0.2.0 of 8 July 2026, and its docs still name older models. The Python SDK's PyPI page answered with a bot check (8). npm builds come from GitHub Actions through trusted publishing with registry signatures, and the changelog records dependency scan fixes. No public CI for the CLI. The repository's six workflow files don't build it, and their results couldn't be read. Its newest GitHub release is v0.28.0 from May 2026, while tags follow npm builds up to 16 October (4). 20+20+6+8+4 = 58.); Clawboo 51 (0.5.0 was published to npm on 21 October 2026 (30). Two releases in the 90 days to 1 November 2026, 0.4.0 on 28 September and 0.5.0, below the three the line asks for (0). github.com was unreachable, so replies to issues, pull requests and Discussions are unchecked. The CI file cites issue #140 as fixed (3). One public npm package, current, with no entry in the official MCP registry for its four servers (10). CI, CodeQL, weekly Dependabot and SLSA provenance on 0.4.0 and 0.5.0, with `@composio/client` pinned to an alpha (8).)