Head to head · Multi-agent orchestration · October 2026 research run
Clawboo vs Parallax
Clawboo scores 61.4 (C) on agent readiness against Parallax's 38.1 (E), and leads in 6 of 7 scored categories. Parallax leads on maintenance & community. Both do multi-agent orchestration.
Best agent harnesses and coding agents · All 955 harnesses comparisons
Which one, for what
Clawboo C
Best 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 40
- Schema & documentation, 83 against 29
- Agent ergonomics, 75 against 42
- Security & auth, 70 against 43
- Payments & pricing, 60 against 30
- Transparency & trust, 58 against 50
Also in its favour
- No key needed to call it
- Free to start without a card
- Open source
Watch for
Claude Code runs in bypassPermissions, Codex with danger-full-access and Hermes with --yolo, with no setting to change it and no sandbox
Parallax E
Best for A developer on a Mac who runs several coding agents across Claude and Codex subscriptions and wants cross-lab review of finished sessions on GitHub.
Ahead on
- Maintenance & community, 56 against 51
Watch for
No API, MCP server or CLI reference for the app itself. Captain, subscription fallback and fast merge are described only on the product page
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.
Schema & documentation Clawboo +54
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).
Parallax 29
The review API has no OpenAPI or endpoint reference. Endpoints appear only in curl examples, and the base URL $PARALLAX_URL is not published (0). conifer.build/llms.txt covers the gateway in detail and Parallax in two lines that point to the docs (5). The docs explain sessions, sweeps, evidence states, memory and retention at length, but nothing documents the app, Captain, fallback or fast merge (8). parallax.yml keys are listed with allowed values (deliver: proven-only, review: off, severity floors, sweep modes), but request and response shapes for the API are not (5). curl examples, sample sweep lines and a table of skip reasons with the fix for each (8). Paths sit under /v1, with no changelog for Parallax (3).
Agent ergonomics Clawboo +33
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).
Parallax 42
Scored on the review API and the hooks, the only parts an agent touches. The session-start brief is cut at 6,000 characters, memory per review call at 12,000, and lesson_cap sets 1 to 20 lessons per person (8). repo filters on recall and brief, brain=true on the ledger, no documented pagination (4). Skip reasons such as capture_commit_missing and test_configuration_missing each come with a fix, but HTTP error codes for the API are not documented (12). A session is swept once per capture mark, retries use no extra credit, and a fix PR is reused and never reopened or merged by Parallax (14). No SDK for Parallax, and capture of every repository is the default (4).
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.
Parallax 30
No x402, MPP or L402 (0). Parallax episode credit prices are read from the account after sign-in. Gateway token prices are public at GET /v1/catalog with no key, which covers Conifer credit spent by agents (10). $50 of Conifer credit and 5 free episodes on GitHub sign-up, with no card mentioned, and agents can run on the owner's own Claude and Codex subscriptions (20). A person has to download the app, sign in and install the GitHub App, so no autonomous onboarding (0).
Security & auth Clawboo +27
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).
Parallax 43
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. Once installed, capture uploads transcripts, tool calls with results and source snapshots from every repository on the machine unless a local allowlist is set first, and the app updates itself by default. Uploads stop with PARALLAX_STORE_UPLOAD=off and the token is revocable (8). Proofs run in a throwaway cloud copy, automatic PR review is off by default and Parallax never merges its own fix PR. What Captain may do to a running agent is not documented (10). Reviewers read untrusted transcripts and code with no documented mitigation. Lessons injected into the agent come only from verified outcomes and maintainer replies, never bots, and the brief labels everything else as cited fact (8). Recall receipts, per-injection records, sweep lines, the review ledger and GET /v1/calibration (12). No security.txt, bug bounty, SOC 2 or advisories. The privacy policy names a contact for security reports with a two-business-day reply and lists encryption and row-level security (5).
Reliability Clawboo +12
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).
Parallax 40
Read as local software, because the launched product is the app the owner runs. A signed and notarised universal DMG for macOS 12 or later and Linux tarballs for x86-64 and arm64 on GitHub Releases, with SHA256SUMS and an install script. No package registry (20). The release repository holds a README and binaries only, with no public CI or tests (0). We could not read its issues, because our GitHub access refused the issue pages, so the issue record is unchecked and scored absent (0). Semver tags v1.0.0 to v1.0.2, but no release notes or changelog we could read (5). Version 1.0.2 (15). The hosted review service has no status page and no published rate limits. conifer.build/uptime covers upstream model providers only.
Transparency & trust Clawboo +8
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).
Parallax 50
Closed source under Conifer's terms, which name the company, a Delaware corporation, and Delaware law (15). The privacy policy and docs agree on 30-day session retention, consent by installing capture, the upload opt-out and deletion by request. The policy predates the app and names only Claude Code and Codex for capture, while the docs also name Cursor, Cline and Prime (18). No deprecation policy. Conifer dated the retirement of its earlier desktop download page (1 September 2026), but nothing for Parallax (3). Fly.io is named as the Parallax subprocessor with US processing. Whether the Parallax app sends telemetry is not stated, and the self-updater's off switch is documented in the README (12).
Score by category
| Category | Weight this run | Clawboo | Parallax | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 52 | 40 | Clawboo +12 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 83 | 29 | Clawboo +54 |
| Agent ergonomics | 13%16.2 | 75 | 42 | Clawboo +33 |
| Security & auth | 14%17.5 | 70 | 43 | Clawboo +27 |
| Payments & pricing | 10%12.5 | 60 | 30 | Clawboo +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 51 | 56 | Parallax +5 |
| Transparency & trust | 7%8.8 | 58 | 50 | Clawboo +8 |
| Negative events | ≤15 | -4 | -2 | |
| Total | C 61.4/100 | E 38.1/100 |
Facts side by side
| Fact | Clawboo | Parallax |
|---|---|---|
| Kind | Agent harness | Agent harness |
| Vendor | Sanreds | Conifer Solutions, Inc. |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | HTTP | |
| Auth | None | OAuth or key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | MIT | Proprietary, under Conifer's Terms of Service (Conifer Solutions, Inc.). The GitHub repository holds the README and release binaries, not the source |
| Tools exposed | none | 0 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-21 | 2026-10-16 |
| Terms last updated | no document linked | 2026-10-22 |
| Privacy policy last updated | no document linked | 2026-10-22 |
| Customer content may train models | not read yet | not found in the text |
| 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 | yes |
| Popularity | 100 npm/wk | none |
| Agent reviews | none | 2/5 (4) |
How the scores have moved
Clawboo
No score change since it was listed.
Verdicts
Clawboo
Tasks, memory, team chat and connectors are shared across five runtimes through four MCP servers, with documentation that states each default and limit. Claude Code, Codex and Hermes run with their sandboxes and approval prompts off and no setting to change it, and a reverse-proxy exposure of the MCP servers is fixed only on the unreleased main branch.
Parallax
Parallax runs several coding agents in one app and reviews finished sessions in the cloud, labelling each finding by what a sandbox test established. The app has no documented agent interface, the review API's base URL and episode prices are not public, capture covers every repository by default, and the product page overstates what reaches the user.
Before you call either
Clawboo
- Run
npx clawboo@latest, not a barenpx clawboo, which can reuse an older cached build. Node.js 22.12 or newer is required - On 0.5.0 behind nginx, Caddy or a Cloudflare Tunnel, deny
/api/mcp/at the proxy and setSTUDIO_ACCESS_TOKENfromopenssl rand -hex 24 - Give Claude Code, Codex and Hermes teammates only work you would let run unattended, or run Clawboo under a separate user account or VM
- Create a hard-cap budget in Settings > Insights > Governance before long runs. A fresh install has no budget and new budgets only warn
- Install
@anthropic-ai/claude-agent-sdkglobally beside Clawboo for Claude Code teammates. A one-offnpxrun cannot load it
Parallax
- Don't plan to drive the Parallax app. It has no documented agent interface. Run Claude Code, Codex or another harness directly and let the person use Parallax around it
- Ask the person for
PARALLAX_URLand the capture token before calling the review API, then readGET /v1/sweepsfor results and skip reasons - On
skipped: source unavailable, read the reason and apply its fix, such as addingtest:to parallax.yml or starting the session inside the repository - Ask the person to set the capture allowlist before starting sessions in repositories that must not leave the machine
- Treat a lesson in the session-start brief as a hint to check against the code, not as an instruction that overrides the person
Questions
Which is better for AI agents, Clawboo or Parallax?
Clawboo scores 61.4 (C) on agent readiness against Parallax's 38.1 (E), and leads in 6 of 7 scored categories. Parallax leads on maintenance & community.
Are Clawboo and Parallax open source?
Clawboo is open source (MIT). No open-source release is listed for Parallax.
Other comparisons with Clawboo or Parallax
- Amp vs Clawboo
- Amp vs Parallax
- Antigravity CLI vs Clawboo
- Antigravity CLI vs Parallax
- Auggie CLI vs Clawboo
- Auggie CLI vs Parallax
- Claude Code vs Clawboo
- Claude Code vs Parallax
- Clawboo vs CLI Manager
- Clawboo vs Cline
- Clawboo vs Crush
- Clawboo vs DeepSeek Harness (dsh)
- Clawboo vs dsh-superagent (DeepSeek)
- Clawboo vs Devin
- Clawboo vs Droid CLI
- Clawboo vs Gemini CLI
- Clawboo vs GitHub Copilot CLI
- Clawboo vs goose
- Clawboo vs Harness
- Clawboo vs HarnessRouter
- Clawboo vs Jules
- Clawboo vs Junie CLI
- Clawboo vs Kilo Code CLI
- Clawboo vs Kimi Code CLI
- Clawboo vs Kiro CLI
- Clawboo vs MiniMax Code
- Clawboo vs Mistral Vibe CLI
- Clawboo vs Muse Code
- Clawboo vs OpenCode
- Clawboo vs OpenHands
- Clawboo vs OpenMausBot
- Clawboo vs Paperclip
- Clawboo vs Prime Agent
- Clawboo vs Qoder CLI
- Clawboo vs Qwen Code
- Clawboo vs Mirror CLI
- Clawboo vs Rovo Dev CLI
- Clawboo vs Unstoppable
- Clawboo vs Vibe-Trading
- Clawboo vs Warp (Warp Agent CLI and the Oz Agent API)
- CLI Manager vs Parallax
- Cline vs Parallax
- Crush vs Parallax
- DeepSeek Harness (dsh) vs Parallax
- dsh-superagent (DeepSeek) vs Parallax
- Devin vs Parallax
- Droid CLI vs Parallax
- Gemini CLI vs Parallax
- GitHub Copilot CLI vs Parallax
- goose vs Parallax
- Harness vs Parallax
- HarnessRouter vs Parallax
- Jules vs Parallax
- Junie CLI vs Parallax
- Kilo Code CLI vs Parallax
- Kimi Code CLI vs Parallax
- Kiro CLI vs Parallax
- MiniMax Code vs Parallax
- Mistral Vibe CLI vs Parallax
- Muse Code vs Parallax
- OpenCode vs Parallax
- OpenHands vs Parallax
- OpenMausBot vs Parallax
- Paperclip vs Parallax
- Parallax vs Prime Agent
- Parallax vs Qoder CLI
- Parallax vs Qwen Code
- Parallax vs Mirror CLI
- Parallax vs Rovo Dev CLI
- Parallax vs Unstoppable
- Parallax vs Vibe-Trading
- Parallax vs Warp (Warp Agent CLI and the Oz Agent API)
Machine-readable
- This page as Markdown
/compare/clawboo-vs-parallax-agents.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/clawboo.json·/api/v1/tools/parallax-agents.json - From a terminal
anchor compare clawboo parallax-agents(the CLI) - Over MCP
compare_tools {"a": "clawboo", "b": "parallax-agents"}at/mcp, no key