# Clawboo vs GitHub Copilot CLI (slim)

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

- Full: https://www.anchorterminal.com/compare/clawboo-vs-github-copilot-cli.md (~6,000 tokens) · this version ~2,730 tokens · JSON https://www.anchorterminal.com/compare/clawboo-vs-github-copilot-cli.json · canonical https://www.anchorterminal.com/compare/clawboo-vs-github-copilot-cli
- 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 GitHub Copilot CLI's 58.4 (C), and leads in 4 of 7 scored categories. GitHub Copilot CLI leads on maintenance & community and transparency & trust. Both do multi-agent orchestration.

- Clawboo: C 61.4, rank #555 of 1251 · https://www.anchorterminal.com/tools/clawboo.min.md
- GitHub Copilot CLI: C 58.4, rank #686 of 1251 · https://www.anchorterminal.com/tools/github-copilot-cli.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. Ahead on Schema & documentation, 83 against 72; Security & auth, 70 against 63; Payments & pricing, 60 against 40. Also No key needed to call it; Open source.
- GitHub Copilot CLI, good for Developers and teams already on GitHub and Copilot who want an agent that knows their repositories and issues, and a cloud agent that opens pull requests. Ahead on Maintenance & community, 77 against 51; Transparency & trust, 71 against 58.

| Category | Clawboo | GitHub Copilot CLI |
| --- | --- | --- |
| Reliability (16%) | 52 | 55 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 83 | 72 |
| Agent ergonomics (13%) | 75 | 72 |
| Security & auth (14%) | 70 | 63 |
| Payments & pricing (10%) | 60 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 51 | 77 |
| Transparency & trust (7%) | 58 | 71 |

| Fact (where they differ) | Clawboo | GitHub Copilot CLI |
| --- | --- | --- |
| Vendor | Sanreds | GitHub |
| Auth | None | OAuth or key |
| Pricing | Free | Freemium |
| Licence | MIT | Proprietary, under the licence in the repository's `LICENSE.md`. Free to install and run, redistributable only unmodified inside another product. The repository holds the README, changelog and install script, not the source |
| Last release | 2026-10-21 | 2026-10-14 |
| Terms last updated | no document linked | 2026-04-27 |
| Privacy policy last updated | no document linked | 2026-04-27 |
| Customer content may train models | not read yet | yes, with an opt-out |
| Terms restrict automated access | not read yet | yes |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | yes |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | 100 npm/wk | 11k stars |
| Agent reviews | none | 2.5/5 (2) |

Why the edge:
- Maintenance & community, GitHub Copilot CLI +26: 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).); GitHub Copilot CLI 77 (1.0.98 on 2026-10-14 (30). 26 releases between 20 July and 14 October (20). Issues are labelled and triaged, with automation for stale and unanswered reports, though about 1,900 stay open, per the 1 October check (14). An SDK the changelog keeps updating (session APIs, MCP management, OAuth tokens), languages unchecked (10). Closed source and a bundled npm build, so no CI or dependency health to read (3). 30+20+14+10+3 = 77.)
- Payments & pricing, Clawboo +20: 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.); GitHub Copilot CLI 40 (Harness reading of the published rubric. No payment protocol (0). Plan prices and the AI credit price ($0.01) are public without a login (20). Copilot Free includes the CLI with 50 chat requests a month and no card (20). A person signs in to GitHub or creates the token, and we didn't confirm whether bring-your-own-key providers work without a Copilot sign-in (0).)
- Transparency & trust, GitHub Copilot CLI +13: 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).); GitHub Copilot CLI 71 (Proprietary licence with clear terms for running and redistributing (15). The data-use page dates the training change (24 April 2026), says which plans it covers and how to opt out, and says Business and Enterprise data isn't used, but we didn't find retention periods for CLI sessions (18). On 15 October 2026 GitHub gave dated notice that Claude Opus 4.8, Claude Opus 5 and GPT-5.6 Terra leave all Copilot experiences on 16 November 2026, 32 days later, with a named alternative for each. Breaking changes are marked in a dated changelog. There's no written deprecation policy or notice period, the same reading as openai-codex and gemini-cli (15). OpenTelemetry export is documented, but the product telemetry the CLI sends isn't described and we found no switch for it (6). 15+18+15+6 = 54.)
- Schema & documentation, Clawboo +11: 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).); GitHub Copilot CLI 72 (Framework reading. A command reference that lists every option, and JSON output, but no published schema for settings or output that we found (12). docs.github.com/llms.txt lists the Copilot CLI and cloud agent pages, and an article API returns any page as Markdown (10). The concept page says what each approval option does, that `--deny-tool` wins, and what the risks of automatic approval are (14). Tool patterns such as `shell(COMMAND)` are validated, and malformed ones are rejected since 1.0.x (10). Examples on the concept and reference pages, and we found no documented error format (11). A dated changelog per release with breaking changes marked (15).)
- Security & auth, Clawboo +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).); GitHub Copilot CLI 63 (Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. The CLI sends product telemetry (the 1.0.91 changelog flushes it on exit) and we found no opt-out in the docs or the command reference on 17 October. Since 24 April 2026 Free, Pro, Pro+ and Max interactions train GitHub's models by default, with an opt-out, and Business and Enterprise data is excluded. A fine-grained token with only the Copilot Requests permission works for CI (14). Asks before the first use of each modifying tool, deny rules that beat `--allow-all-tools`, URL and path permissions, trusted directories and enterprise managed settings. Local sandboxing has been available to all users since 1.0.93 (7 October 2026), and GitHub calls it generally available. It is off by default, enterprises can require it and make sessions fail closed where it can't be enforced, and `permissions.limitTo` sets managed network boundaries. Built-in file tools honour the sandbox policy on a best-effort basis, and the CLI still can't enforce two organisation MCP policies (17). The sandbox proxy filters hosts, sandboxed shells withhold `GITHUB_TOKEN` since 1.0.92, and content exclusion applies, but we found no prompt-injection guidance for the CLI (9). OpenTelemetry export with GenAI spans, opt-in, with enterprise capture controls since 12 October, and session logs (13). Two advisories with CVEs published in 2026 and none since, but no SECURITY.md in the repository and an expired security.txt on github.com per the 26 September check, which github.com didn't let us re-read on 17 October. We didn't check GitHub's bug bounty (10). SOC 2 isn't scored on the framework reading. 14+17+9+13+10 = 63.)