Head to head · Multi-agent orchestration · October 2026 research run

Clawboo vs herdr

herdr scores 71.1 (BB) on agent readiness against Clawboo's 65.1 (B), and leads in 4 of 7 scored categories. Clawboo leads on security & auth. Both do multi-agent orchestration.

Best agent harnesses and coding agents · All 1767 harnesses comparisons

Which one, for what

Clawboo B

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

  • Security & auth, 70 against 49

Also in its favour

  • Free to start without a card

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

herdr BB

Best for A developer who runs several coding agents in terminals, locally or over SSH, and wants one agent to start, prompt and wait on others.

Ahead on

  • Reliability, 65 against 52
  • Schema & documentation, 91 against 83
  • Maintenance & community, 63 against 51
  • Transparency & trust, 70 against 58

Also in its favour

  • Agent-ready, a grade of BB or better
  • No incidents deducted, where Clawboo loses 4 points for them

Watch for

Version 0.9.5, not yet 1.0, and the last tagged release is 14 October 2026

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.

Security & auth Clawboo +21

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).

herdr 49

Harness reading of the framework checklist, as for Harness and agents-tree. 30 for what leaves the machine and credentials, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. No account, no telemetry found in the source, and a socket file set to 0600. Version and manifest checks reach herdr.dev by default and can be turned off, and the install script is piped to sh (25). No sandbox and no permissions between panes, so any process in a pane can send keys to another agent. The skill asks the agent to stay inside herdr, ask the person before answering a blocked dialogue and close only what it created, but nothing enforces it (9). Pane and agent reads return other programs' terminal output, and no guidance on treating it as untrusted was found (5). A server log, but no per-call audit log found (5). No SECURITY.md or disclosure policy in the repository, and herdr.dev serves no security.txt. CI pins actions to commit SHAs and Dependabot is on (5). 25 + 9 + 5 + 5 + 5 = 49.

Reliability herdr +13

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).

herdr 65

Read as local software, as for agents-tree and Harness. Official release binaries for Linux, macOS and Windows x86_64 with an install script, and Homebrew and mise in the README. The Homebrew formula wasn't read (20). .github/workflows/ci.yml runs checks and tests on ubuntu, macOS and Windows for every push and pull request, but run results couldn't be read from this session, so 15, the value this run gives public CI with unread results. 495 issues were open on 18 November 2026. The 25 newest, opened 15 to 18 November, all carry a triaged label and a priority (p1 or p2), several of them bugs, so reports are sorted within a day but many stay open (15). Semver tags and a Keep a Changelog file with Breaking Changes and Removed sections (15). Version 0.9.5, not 1.0, and not declared stable (0). 20 + 15 + 15 + 15 + 0 = 65.

Maintenance & community herdr +12

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).

herdr 63

v0.9.5 on 14 October 2026, 35 days before the check, and the last commit on master on 29 October (20). Six releases from 7 September to 14 October 2026 (20). 495 open issues and 26 open pull requests. The 25 newest issues were labelled triaged with a priority within a day of opening. Unsolicited pull requests are closed automatically and a monthly workflow closes stale issues (15). Not an MCP server and no official SDK (0). Cargo.lock, Dependabot and CI on three systems, run results unread (8). 20 + 20 + 15 + 0 + 8 = 63.

Transparency & trust herdr +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).

herdr 70

Apache-2.0 (30). herdr.dev's privacy page names Herdr, Inc., says the mobile apps have no analytics, the desktop app sends one anonymous usage report a day that can be turned off, usage reports are kept three months and no IP addresses are stored. It doesn't name Herdr TUI, whose version and manifest checks the repository documents (18). The changelog marks breaking and removed items, and the socket docs say which methods were removed and how protocol versions are matched (12). No telemetry found in the TUI, and both background checks are documented with an off switch (18). 30 + 18 + 12 + 18 = 78.

Schema & documentation herdr +8

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).

herdr 91

Read as a CLI and socket API. herdr api schema --json prints a JSON Schema for requests, responses, errors and events, also at docs/next/api/herdr-api.schema.json (25). Markdown for agents, with skills/herdr/SKILL.md and distribution/agent-guide.md. https://herdr.dev/llms.txt indexes the 0.9.5 docs as raw source files for agents (10). The skill says when to use herdr and when not to, and the socket docs say which layer to use for which job, but the schema itself carries few descriptions (15). The schema has 49 enums and agent names are constrained by a pattern, while some inputs are free strings (12). Many CLI and JSON examples, a documented error shape with codes such as not_found, agent_blocked and events_lost (14). Versioned docs per release and a changelog (15). 25 + 10 + 15 + 12 + 14 + 15 = 91.

Score by category

CategoryWeightClawbooherdrEdge
Reliability16%5265herdr +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8391herdr +8
Agent ergonomics13%7573Clawboo +2
Security & auth14%7049Clawboo +21
Payments & pricing10%9090even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5163herdr +12
Transparency & trust7%5870herdr +12
Negative events≤15-40
TotalB 65.1/100BB 71.1/100

Facts side by side

FactClawbooherdr
KindAgent harnessAgent harness
VendorSanredsherdr
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMITApache-2.0
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-212026-10-14
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linked2026-11-02
Popularity100 npm/wk52k stars

How the scores have moved

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.

herdr

Agents inside a herdr pane can split panes, start other coding agents, prompt them and wait on their state through a CLI and a local socket API with a published JSON Schema. It is pre-1.0 local software with no sandbox, and any process in a pane can type into another agent's terminal.

Before you call either

Clawboo

  1. Run npx clawboo@latest, not a bare npx clawboo, which can reuse an older cached build. Node.js 22.12 or newer is required
  2. On 0.5.0 behind nginx, Caddy or a Cloudflare Tunnel, deny /api/mcp/ at the proxy and set STUDIO_ACCESS_TOKEN from openssl rand -hex 24
  3. Give Claude Code, Codex and Hermes teammates only work you would let run unattended, or run Clawboo under a separate user account or VM
  4. Create a hard-cap budget in Settings > Insights > Governance before long runs. A fresh install has no budget and new budgets only warn
  5. Install @anthropic-ai/claude-agent-sdk globally beside Clawboo for Claude Code teammates. A one-off npx run cannot load it

herdr

  1. Check HERDR_ENV=1 before any herdr command. If it isn't set, tell the person you aren't inside herdr and stop
  2. Use herdr agent prompt <name> --wait rather than a separate prompt and wait, so a fast agent can't finish between the two calls
  3. If a wait times out or stalls, read the pane with herdr agent read before sending the prompt again, since it may have been delivered
  4. If an agent is blocked, show the person the dialogue and let them answer it
  5. Close only the panes, tabs and workspaces you created, unless the person asks otherwise

Questions

Which is better for AI agents, Clawboo or herdr?

herdr scores 71.1 (BB) on agent readiness against Clawboo's 65.1 (B), and leads in 4 of 7 scored categories. Clawboo leads on security & auth.

Are Clawboo and herdr open source?

Yes. Clawboo is open source (MIT). herdr is open source (Apache-2.0).

Other comparisons with Clawboo or herdr

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.