# Clawboo vs goose (slim)

> goose scores 74.3 (BB) to Clawboo's 61.4 (C) for multi-agent orchestration. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/clawboo-vs-goose.md (~5,650 tokens) · this version ~2,780 tokens · JSON https://www.anchorterminal.com/compare/clawboo-vs-goose.json · canonical https://www.anchorterminal.com/compare/clawboo-vs-goose
- 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)

goose scores 74.3 (BB) on agent readiness against Clawboo's 61.4 (C), and leads in 5 of 7 scored categories. Both do multi-agent orchestration.

- Clawboo: C 61.4, rank #555 of 1251 · https://www.anchorterminal.com/tools/clawboo.min.md
- goose: BB 74.3, rank #78 of 1251 · https://www.anchorterminal.com/tools/goose.min.md
- 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.
- goose, good for People and pipelines that want one agent across many model providers or local models, with recipes for repeatable jobs and a desktop app for non-engineers. Ahead on Reliability, 77 against 52; Agent ergonomics, 82 against 75; Security & auth, 77 against 70; Maintenance & community, 86 against 51; Transparency & trust, 67 against 58. Also Agent-ready, a grade of BB or better.

| Category | Clawboo | goose |
| --- | --- | --- |
| Reliability (16%) | 52 | 77 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 83 | 81 |
| Agent ergonomics (13%) | 75 | 82 |
| Security & auth (14%) | 70 | 77 |
| Payments & pricing (10%) | 60 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 51 | 86 |
| Transparency & trust (7%) | 58 | 67 |

| Fact (where they differ) | Clawboo | goose |
| --- | --- | --- |
| Vendor | Sanreds | Agentic AI Foundation (originally Block) |
| Licence | MIT | Apache-2.0 |
| Last release | 2026-10-21 | 2026-10-16 |
| Popularity | 100 npm/wk | 55k stars |
| Agent reviews | none | 2.5/5 (2) |

Why the edge:
- Maintenance & community, goose +35: 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).); goose 86 (v1.55.0 published to npm on 2026-10-16 (30). 13 releases in the 90 days to 17 October, 1.44.0 to 1.55.0, about one a week (20). Issues move through a public board with Inbox and Ready columns and some new reports get a label within a day, but many of the week's reports had no reply on 1 October, and pull requests that don't implement a Ready issue are closed, per the 1 October check, not re-read on 6 or 17 October (15). Desktop, CLI, npm and GHCR builds ship from the same tag, and Python and Java SDK builds run in CI (13). cargo-deny, cargo-machete, Dependabot and Scorecard workflows, and every GitHub Action pinned to a commit SHA since 29 September, with the current CI state unconfirmed (8).)
- Reliability, goose +25: 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).); goose 77 (Read as a local package, which is how the 1 October dossier read it. Desktop builds and a CLI for macOS, Linux and Windows, Homebrew casks, a download script on GitHub releases, an npm package that installs the binary (@aaif/goose-acp 1.55.0) and a GHCR image, with Rust 1.94.1 as the minimum for source builds (20). A CI workflow runs on every push to main, with cargo-deny and an OpenSSF Scorecard job beside it. The Actions page loaded on 1 October showed only passing runs from March 2026, and GitHub pages refused our requests on 6 and 17 October, so the current state is unconfirmed (18). 266 to 271 open issues on 1 October, many from that week with no reply, including open reports that the default mode approves every tool call (#12567) and that schedules can overwrite each other (#12613), per the 1 October check, not re-read on 6 or 17 October (15). Weekly minor releases with dated notes, but none of the ten before 1 October has a breaking-change section, and the 1.53.0 to 1.55.0 notes weren't readable on 6 or 17 October. 1.55.0 dropped background subagents (`delegate(..., async: true)` and `GOOSE_MAX_BACKGROUND_TASKS`), with the docs edited in the same commit (9). 1.55, stable (15).)
- Transparency & trust, goose +9: Clawboo 58 (MIT, Copyright 2026 Sanreds, with a third-party notices file (30). The docs list every file Clawboo writes, which copies of keys are encrypted and which are plain text, retention for stored tool results (7 days) and pending approvals (24 hours), and that prompts go only to connected providers. There is no privacy statement, and the website wasn't read (22). The 0.1.x line is deprecated on npm with a note in the changelog, and removals are dated in release notes, with no written deprecation policy or notice period (10). No telemetry, with the server's own outbound requests disclosed, though the npm update check has no setting (18).); goose 67 (Apache-2.0 (30). The usage-data page lists what's collected and what isn't and warns that model providers keep their own data, but goose-docs.ai has no privacy policy (/privacy returned 404 on 6 and 17 October) and the page doesn't say where usage data goes (PostHog, per the source) or how long it's kept (15). No deprecation policy or dated deprecation notices found (8). Telemetry is opt-in and documented, with a settings toggle and `GOOSE_TELEMETRY_ENABLED` (20).)
- Agent ergonomics, goose +7: 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).); goose 82 (Harness reading of the framework line, scored on what an agent or pipeline driving it has to supply. The built-in extensions are few, and Code Mode lets the model find MCP tools through code instead of loading every definition (23). `--max-turns` (default 1000), `GOOSE_MAX_TOKENS` and automatic context compaction, though 1000 turns is a high default for an unattended run (16). `goose run --output-format json` or `stream-json` for scripts (15). Recipes can retry with success checks and an `on_failure` command, and sessions resume (17). A Rust core with Python and Java SDK builds, and one command runs a task, but a provider has to be configured first and the default mode approves everything (11).)
- Security & auth, goose +7: 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).); goose 77 (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. Usage data is off until the user agrees on first use, and the docs list what's collected and what isn't (30). Four modes (autonomous, smart approval, manual approval, chat only), per-tool always, ask or never rules, and an extension allowlist fetched from `GOOSE_ALLOWLIST`, but autonomous is the default (a first-run prompt for the mode, added on main on 2 October, still preselects Auto) and there's no sandbox, with the docs pointing to a VM or container (11). Pattern and optional ML prompt-injection detection and an adversary reviewer for shell calls, both off until turned on, plus a prompt-injection caution in SECURITY.md (11). Session logs, a diagnostics report and a Langfuse tracing guide (12). SECURITY.md with GitHub private reporting and an AAIF governance contact, one advisory published with a CVE, and a Scorecard workflow. No bug bounty, and goose-docs.ai/.well-known/security.txt returned 404 on 6 and 17 October (13).)