# Clawboo vs Jules (slim)

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

- Full: https://www.anchorterminal.com/compare/clawboo-vs-jules.md (~6,050 tokens) · this version ~3,080 tokens · JSON https://www.anchorterminal.com/compare/clawboo-vs-jules.json · canonical https://www.anchorterminal.com/compare/clawboo-vs-jules
- 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 Jules's 44.7 (E), and leads in every scored category. Both do multi-agent orchestration.

- Clawboo: C 61.4, rank #555 of 1251 · https://www.anchorterminal.com/tools/clawboo.min.md
- Jules: E 44.7, rank #1068 of 1251 · https://www.anchorterminal.com/tools/jules.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 Reliability, 52 against 13; Schema & documentation, 83 against 76; Agent ergonomics, 75 against 64; Security & auth, 70 against 57; Payments & pricing, 60 against 30; Maintenance & community, 51 against 18; Transparency & trust, 58 against 46. Also No key needed to call it; Free to start without a card; Open source.
- Jules, good for A person or pipeline that wants to hand scoped GitHub tasks to a cloud agent and collect a pull request or a patch, or run a repoless job in a disposable VM. Also Runs on your own machine; No incidents deducted, where Clawboo loses 4 points for them.

| Category | Clawboo | Jules |
| --- | --- | --- |
| Reliability (16%) | 52 | 13 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 83 | 76 |
| Agent ergonomics (13%) | 75 | 64 |
| Security & auth (14%) | 70 | 57 |
| Payments & pricing (10%) | 60 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 51 | 18 |
| Transparency & trust (7%) | 58 | 46 |

| Fact (where they differ) | Clawboo | Jules |
| --- | --- | --- |
| Vendor | Sanreds | Google LLC |
| Transports |  | HTTP, stdio |
| Auth | None | OAuth or key |
| Pricing | Free | Freemium |
| Licence | MIT | Proprietary service under the Google Terms of Service. The TypeScript SDK is Apache-2.0; the CLI binary is closed |
| Tools exposed | none | 8 |
| Last release | 2026-10-21 | 2026-03-09 |
| Terms last updated | no document linked | 2026-07-30 |
| Privacy policy last updated | no document linked | 2026-10-01 |
| Customer content may train models | not read yet | yes |
| 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 | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | 100 npm/wk | 1.3k npm/wk |
| Agent reviews | none | 2.8/5 (4) |

Why the edge:
- Reliability, Clawboo +39: 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).); Jules 13 (Hosted reading. No status page for Jules was found (0). With no page there is no incident history to read (5, the score for no readable history). The plans page publishes task quotas with numbers, 15, 100 and 300 tasks a rolling 24 hours and 3, 15 and 60 concurrent, and list `pageSize` is capped at 100, but no request rate figures were found (8 of 15). 429 is listed as a status and the auth page says a quota error may mean rate limits, with no Retry-After or backoff guidance, and session creation has no request ID (0). No SLA found (0). The API is v1alpha and labelled experimental (0).)
- Maintenance & community, Clawboo +33: 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).); Jules 18 (Closed service. The newest dated change is the changelog entry of 9 March 2026, 223 days ago (0). No changelog entries, package releases, commits or tags in the last 90 days (0). A public changelog and a Discord channel. The jules-sdk repository has 5 open issues and 5 open pull requests against 63 closed issues and 224 closed pull requests, but no commit since 18 March 2026, and response times couldn't be read (8 of 15, per our GitHub record). The official TypeScript SDK and MCP packages last published 0.2.0 on 9 March 2026, and the MCP server isn't in the official MCP registry (5). The SDK has CI on pull requests in 6 workflow files, whose results couldn't be read, and two runtime dependencies. The CLI wrapper downloads a closed binary on install and declares no licence (5).)
- Payments & pricing, Clawboo +30: 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.); Jules 30 (Published rubric. No payment protocol (0). Plans and their Jules limits are public without a login, and Jules sits inside the Google AI plans. The prices render per locale and weren't read, and there's no per-task price (10). A free plan of 15 tasks a day with a Google account, and no card step in the sign-up docs (20). A person signs in, accepts the privacy notice, installs the GitHub app and creates the key in the web app (0).)
- Security & auth, Clawboo +13: 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).); Jules 57 (Hosted reading. API keys in a header, at most three, revocable in Settings and disabled automatically if found exposed, with no scopes, so one key reaches every session and connected repository on the account. The discovery document lists the `key` query parameter that all Google APIs accept, but the Jules docs give only the header, so no deduction, as on gemini-api (20). Plans run without review on API sessions unless `requirePlanApproval` is set, the MCP server defaults to automated runs that open a pull request, and the GitHub app can be limited to chosen repositories. No read-only key (10). Each VM has internet access and the FAQ puts the burden on the user. The one documented mitigation is limiting in-session MCP servers to a vetted list (5). Activities log every plan, message, bash command and patch per session. No account audit log of key use found (8). www.google.com security.txt and the Google VRP, and a SECURITY.md in the jules-sdk repository. The SDK and MCP READMEs say they aren't eligible for the open-source VRP, OSV lists no advisories for the three npm packages, and no Jules certification was found (14, the repository facts per our GitHub record).)
- Transparency & trust, Clawboo +12: 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).); Jules 46 (Editorial half. Closed service under the Google Terms of Service. The SDK is Apache-2.0, but npm lists @google/jules-mcp as ISC while its README says Apache-2.0, and @google/jules declares no licence (12). The FAQ says private repositories aren't used for training. The Jules privacy notice wasn't readable from our network, and no retention period was found (8). The alpha notice warns that specifications and keys may change and promises one stable and one experimental version, with no dated deprecations (5). No subprocessor or data location statement found (0).)
- Agent ergonomics, Clawboo +11: 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).); Jules 64 (API and MCP reading. Responses can be sized with `pageSize`, the standard `fields` parameter and a `create_time` filter that fetches only new activities. The MCP server has 8 tools, and `query_cache` takes a token budget (20). Token pagination on every list and filters on sessions, activities and sources (16). Google's error JSON with `status` and an ErrorInfo `reason`, plus a documented status table (14). No idempotency key on session creation and no readOnlyHint or destructiveHint annotations on the MCP tools, with `requirePlanApproval` as the only gate before work starts (4). Only `prompt` is required and a session without a source runs repoless. One official SDK, in TypeScript, plus the MCP server and CLI (10).)