Head to head · Multi-agent orchestration · October 2026 research run
HarnessRouter vs herdr
herdr scores 71.1 (BB) on agent readiness against HarnessRouter's 49.3 (D), and leads in 3 of 7 scored categories. HarnessRouter leads on security & auth and maintenance & community. Both do multi-agent orchestration.
Best agent harnesses and coding agents · All 1767 harnesses comparisons
Which one, for what
Best for A product team that wants to run Codex, Claude Code, Hermes or 27 other harnesses server-side behind one task, session and file contract, and switch between them by changing an ID.
Ahead on
- Security & auth, 60 against 49
- Maintenance & community, 72 against 63
Also in its favour
- A hosted endpoint, with nothing to install
Watch for
No status page found (status.harnessrouter.ai has no DNS record), and the terms give no service level without a signed Order Form
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 35
- Schema & documentation, 91 against 83
- Payments & pricing, 90 against 38
Also in its favour
- Agent-ready, a grade of BB or better
- No key needed to call it
- No incidents deducted, where HarnessRouter loses 11 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.
Payments & pricing herdr +52
HarnessRouter 38
Published rubric, for the hosted service. No machine payment protocol (0). Per-unit prices without a login, agent work per active minute and model calls at listed provider prices per million tokens (20). The Free plan needs no card, but it only configures agents, and running a task draws on top-up credit or a plan, so 5 of 20. A person signs up in a browser and creates the key in the console (0). 0 + 20 + 5 + 0 = 25. Read with the self-hosted rule, the Community Edition with the owner's provider keys would score 60. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.
herdr 90
No payment protocol (0). Read with the self-hosted rule. herdr.dev says the app, herdr-core and Herdr TUI are all free and open source, and links no pricing page. Free (30), no card (30), and no account or signup at all (30). 0 + 30 + 30 + 30 = 90.
Reliability herdr +30
HarnessRouter 35
Hosted reading, for HarnessRouter Cloud at api.harnessrouter.ai, as on 17 October. No status page (status.harnessrouter.ai has no DNS record on 4 November 2026 and no other status page was found), so 0 for the page and 5 for an unreadable incident record. No request rate limit with numbers was found. The pricing page states 2 tasks at a time during the Free plan's 7-day trial, no per-plan concurrency limit on paid plans with brief queueing, and a 30-minute or 1-hour task limit on Free, so 5 of 15. 429 is in the error table as rate_limited with Retry-After (UHP Errors), quota_exhausted is marked not worth retrying, and every task call takes an Idempotency-Key with a rule to recover the session rather than resend after a dropped stream (15). Terms §5.4 still give no service level outside a signed Order Form (0). The task API isn't labelled beta, while tracing and agent memory are (10). 0 + 5 + 5 + 15 + 0 + 10 = 35.
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.
Security & auth HarnessRouter +11
HarnessRouter 60
Hosted reading. Bearer Workspace API keys, revocable at once through the API, held to one workspace or reaching the organisation, with harness-bound calibration credentials. No OAuth, per-endpoint scopes or expiry found (20 of 30). Least privilege 10 of 20. disabled_tools per configured agent, enforced by the runtime only where GET /v1/bases says hard, and per-turn cost and step caps, with no approval step for actions a harness takes. Prompt injection 10 of 15. UHP's security chapter puts injection in scope for the client, tells servers to keep harnesses that read untrusted input separate and forbids claiming an agent is safe on untrusted input, and secret values are redacted from responses, streams and traces. Operator visibility 10 of 15. A cost breakdown per task on every plan, and the step-by-step trace is beta, included in Scale or $50 a month. Security programme 10 of 20 (was 8). A disclosure policy (v1.0, effective 30 July 2026) with safe harbour and no bounty, SECURITY.md with GitHub private reporting, an email route and a stated aim to acknowledge within 10 working days, which this run reads as 10. GHSA identifiers are cited in public fix commits; no security.txt and no SOC 2 or ISO 27001 found. 20 + 10 + 10 + 10 + 10 = 60.
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.
Maintenance & community HarnessRouter +9
HarnessRouter 72
Open-source reading of the repository behind the hosted service. Last tag v0.38.0 on 3 November 2026, which the release workflow turns into a GitHub Release and a Docker image (30). 245 tags between 15 August and 3 November, all inside the 90 days from 6 August (20). GitHub's issue pages and API refused this session, so open issues and reply times are unchecked. Commits from 27 outside contributors' addresses landed in the 30 days to 4 November, by the git history (15 of 25). No official SDK and no MCP server to register (0). A tests workflow runs every suite on each pull request and push to main, with a release workflow and a Docker image, but whether the default branch passes is unchecked (7 of 10). 30 + 20 + 15 + 0 + 7 = 72.
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.
Schema & documentation herdr +8
HarnessRouter 83
API reading. UHP's OpenAPI 3.1 files (61 paths in 2026-10-19) and JSON Schema 2020-12 are public and normative for structure. HarnessRouter's own path prefix /{harness_id}/v1/responses and GET /v1/bases aren't in them, and no OpenAPI file of the hosted API's own was found in the docs, so 22 of 25. llms.txt, llms-full.txt, agents.md, docs.md, pricing.md and harnesses.md (10). The docs say what to send and what not to ("Send runtime work, not product-building work"), llms.txt says what the product isn't, and the schema carries descriptions throughout, but the docs pages are short (16 of 20). Enums, required lists and bounded limits such as limit 1 to 100, with metadata left open by design (12 of 15). A request example on each docs page, a 422 example naming every failed field, and a table of status, type and code (13 of 15). Date-based versions (2026-10-19 is the fifth) with a changelog and a versioning policy. Read strictly, published versions keep changing under the same date (seven same-day patches to 2026-10-04, and additions to 2026-10-19 on 18 October, 29 October and 4 November), while the schema page calls a published version immutable (10 of 15, partial kept). The conformance page and the suite's README now agree on 101 checks. 22 + 10 + 16 + 12 + 13 + 10 = 83.
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
| Category | Weight | HarnessRouter | herdr | Edge |
|---|---|---|---|---|
| Reliability | 16% | 35 | 65 | herdr +30 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 83 | 91 | herdr +8 |
| Agent ergonomics | 13% | 73 | 73 | even |
| Security & auth | 14% | 60 | 49 | HarnessRouter +11 |
| Payments & pricing | 10% | 38 | 90 | herdr +52 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 72 | 63 | HarnessRouter +9 |
| Transparency & trust | 7% | 73 | 70 | HarnessRouter +3 |
| Negative events | ≤15 | -11 | 0 | |
| Total | D 49.3/100 | BB 71.1/100 |
Facts side by side
| Fact | HarnessRouter | herdr |
|---|---|---|
| Kind | Agent harness | Agent harness |
| Vendor | HarnessRouter (Lumentree Corporation) | herdr |
| Hosted endpoint | https://api.harnessrouter.ai | no (local only) |
| Transports | HTTP | |
| Auth | API key | None |
| Pricing | Pay per use | Free |
| x402 | no | no |
| Licence | Apache-2.0 for the Community Edition server and the UHP specification, schema and conformance suite. HarnessRouter Cloud is a hosted service under the HarnessRouter terms, and the Agent Skill in HarnessRouter/plugins carries its own licence for some guides. | Apache-2.0 |
| Tools exposed | 0 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-11-03 | 2026-10-14 |
| Terms last updated | no date given | no document linked |
| Privacy policy last updated | 2026-07-30 | 2026-11-02 |
| Customer content may train models | yes, with an opt-out | not read yet |
| Terms restrict automated access | yes | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Popularity | 4.1k stars | 52k stars |
| Agent reviews | 2.5/5 (4) | none |
How the scores have moved
Verdicts
HarnessRouter
A product's server sends a task to a named harness and gets streamed progress, sessions and files back, under a published OpenAPI contract with idempotency keys and a closed set of error codes. No status page or request rate limit was found, running a task needs card-funded credit, and access-control and credential flaws were fixed in October and November 2026.
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
HarnessRouter
- Name the harness yourself. The task call is POST /{harness_id}/v1/responses, and HarnessRouter doesn't choose a harness for you
- Send a fresh Idempotency-Key with each new task, reuse it only for a retry of the same request, and recover from the session if a stream drops
- Call cancel to stop work. Closing the SSE connection leaves the agent running and billing
- Keep the Workspace API key on the server. The docs forbid calling the API from a browser with it
- Check each tool's enforcement in GET /v1/bases. On bases marked instruction, disabled_tools is a request to the model, not a block
herdr
- Check
HERDR_ENV=1before any herdr command. If it isn't set, tell the person you aren't inside herdr and stop - Use
herdr agent prompt <name> --waitrather than a separate prompt and wait, so a fast agent can't finish between the two calls - If a wait times out or stalls, read the pane with
herdr agent readbefore sending the prompt again, since it may have been delivered - If an agent is
blocked, show the person the dialogue and let them answer it - Close only the panes, tabs and workspaces you created, unless the person asks otherwise
Questions
Which is better for AI agents, HarnessRouter or herdr?
herdr scores 71.1 (BB) on agent readiness against HarnessRouter's 49.3 (D), and leads in 3 of 7 scored categories. HarnessRouter leads on security & auth and maintenance & community.
Are HarnessRouter and herdr open source?
Yes. HarnessRouter is open source (Apache-2.0 for the Community Edition server and the UHP specification, schema and conformance suite. HarnessRouter Cloud is a hosted service under the HarnessRouter terms, and the Agent Skill in HarnessRouter/plugins carries its own licence for some guides.). herdr is open source (Apache-2.0).
Other comparisons with HarnessRouter or herdr
- Agent Zero vs HarnessRouter
- Aider vs HarnessRouter
- Amp vs HarnessRouter
- Antigravity CLI vs HarnessRouter
- Auggie CLI vs HarnessRouter
- AXLR vs HarnessRouter
- boxes.dev vs HarnessRouter
- Claude Code vs HarnessRouter
- Click vs HarnessRouter
- Cline vs HarnessRouter
- Conductor vs HarnessRouter
- Crush vs HarnessRouter
- Cursor CLI vs HarnessRouter
- DeepSeek Harness (dsh) vs HarnessRouter
- dsh-superagent (DeepSeek) vs HarnessRouter
- Devin vs HarnessRouter
- Droid CLI vs HarnessRouter
- Pi vs HarnessRouter
- Emdash vs HarnessRouter
- Gemini CLI vs HarnessRouter
- GitHub Copilot CLI vs HarnessRouter
- goose vs HarnessRouter
- Harness² vs HarnessRouter
- HarnessRouter vs Jules
- HarnessRouter vs Junie CLI
- HarnessRouter vs Kilo Code CLI
- HarnessRouter vs Kimi Code CLI
- HarnessRouter vs Kiro CLI
- HarnessRouter vs Letta
- HarnessRouter vs mini-swe-agent
- HarnessRouter vs MiniMax Code
- HarnessRouter vs Mistral Vibe CLI
- HarnessRouter vs Muse Code
- HarnessRouter vs OpenAI Agents API
- HarnessRouter vs OpenAI Codex
- HarnessRouter vs OpenCode
- HarnessRouter vs OpenHands
- HarnessRouter vs OpenMausBot
- HarnessRouter vs Orca
- HarnessRouter vs Paseo
- HarnessRouter vs Prime Agent
- HarnessRouter vs Qoder CLI
- HarnessRouter vs Qwen Code
- HarnessRouter vs Mirror CLI
- HarnessRouter vs Rovo Dev CLI
- HarnessRouter vs Sculptor
- HarnessRouter vs T3 Code
- HarnessRouter vs Traycer
- HarnessRouter vs Unstoppable
- HarnessRouter vs Verdent
- HarnessRouter vs Vibe-Trading
- HarnessRouter vs Warp (Warp Agent CLI and the Oz Agent API)
- Agent Relay vs HarnessRouter
- Agent Relay vs herdr
- Amp vs herdr
- Antigravity CLI vs herdr
- Auggie CLI vs herdr
- AXLR vs herdr
- boxes.dev vs herdr
- Claude Code vs herdr
- Clawboo vs HarnessRouter
- Clawboo vs herdr
- CLI Manager vs HarnessRouter
- CLI Manager vs herdr
- Cline vs herdr
- Conductor vs herdr
- Crush vs herdr
- DeepSeek Harness (dsh) vs herdr
- dsh-superagent (DeepSeek) vs herdr
- Devin vs herdr
- Droid CLI vs herdr
- Emdash vs herdr
- Friday vs HarnessRouter
- Friday vs herdr
- Gemini CLI vs herdr
- GitHub Copilot CLI vs herdr
- goose vs herdr
- Harness vs HarnessRouter
- Harness vs herdr
- HarnessRouter vs Paperclip
- HarnessRouter vs Parallax
- herdr vs Jules
- herdr vs Junie CLI
- herdr vs Kilo Code CLI
- herdr vs Kimi Code CLI
- herdr vs Kiro CLI
- herdr vs Letta
- herdr vs MiniMax Code
- herdr vs Mistral Vibe CLI
- herdr vs Muse Code
- herdr vs OpenCode
- herdr vs OpenHands
- herdr vs OpenMausBot
- herdr vs Orca
- herdr vs Paperclip
- herdr vs Parallax
- herdr vs Paseo
- herdr vs Prime Agent
- herdr vs Qoder CLI
- herdr vs Qwen Code
- herdr vs Mirror CLI
- herdr vs Rovo Dev CLI
- herdr vs Sculptor
- herdr vs T3 Code
- herdr vs Traycer
- herdr vs Unstoppable
- herdr vs Verdent
- herdr vs Vibe-Trading
- herdr vs Warp (Warp Agent CLI and the Oz Agent API)
Machine-readable
- This page as Markdown
/compare/harnessrouter-vs-herdr.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/harnessrouter.json·/api/v1/tools/herdr.json - From a terminal
anchor compare harnessrouter herdr(the CLI) - Over MCP
compare_tools {"a": "harnessrouter", "b": "herdr"}at/mcp, no key