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

herdr vs Mirror CLI

herdr scores 71.1 (BB) on agent readiness against Mirror CLI's 60.9 (C), and leads in 5 of 7 scored categories. Mirror CLI leads on security & auth. Both do multi-agent orchestration.

Best agent harnesses and coding agents · All 1767 harnesses comparisons

Which one, for what

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 40
  • Schema & documentation, 91 against 75
  • Agent ergonomics, 73 against 58
  • Maintenance & community, 63 against 47

Also in its favour

  • Agent-ready, a grade of BB or better
  • No key needed to call it

Watch for

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

Mirror CLI C

Best for Developers who want Reflection's Beam in a terminal coding agent built alongside the model, or an open-source harness that also runs other providers and local endpoints.

Ahead on

  • Security & auth, 58 against 49

Also in its favour

  • Free to start without a card

Watch for

Version 0.1.x, labelled early beta, with an undated changelog and no CLI release tags

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.

Reliability herdr +25

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.

Mirror CLI 40

Local-package reading. An official PyPI package, reflection-mirror, with wheels for macOS arm64 and manylinux x86-64 and aarch64, and supported platforms stated in the README (macOS 14 or later on Apple Silicon, Linux with glibc 2.28 or later, Python 3.12 or later) (20). A public CI workflow runs the Python package tests (ci.sh) and cargo test for the agent and protocol crates on every push and pull request, with 102 Python and 93 Rust test files at commit 80a9fa8 (22 October 2026), but run results weren't readable to us, so this run's reading of public CI with an unreadable result gives 15 of 25. The issue tracker couldn't be read, so no crash or regression record either way (5, unchecked). A CHANGELOG.md now lists 0.1.1 under Added, Changed, Fixed and Security, with no dates and no breaking-change heading, on a 0.x version (0, flagged). 0.1.x, labelled early beta in the docs (0).

Schema & documentation herdr +16

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.

Mirror CLI 75

Framework reading. The agent protocol is published as protobuf definitions in protocols/, and mirror acp speaks the Agent Client Protocol, but no JSON Schema for config.json or the MCP definition files was found (15 of 25). llms.txt with a Markdown copy of every page (10). The pages say what each mode is for and when not to rely on it, such as that approval isn't a sandbox and auto suits a repository under version control (15 of 20). Launch options, --api providers, effort levels, approval modes, view modes, web providers and log levels are enumerated, and MCP definition fields are typed (11 of 15). Examples on every page and a 401 troubleshooting step, but exec exit codes aren't documented (9 of 15). Versions with a stated tag scheme (reflection-mirror-vX.Y.Z for the CLI, mirror-agent-vX.Y.Z for the agent) and a public CHANGELOG.md in the repository since 22 October 2026 (15).

Maintenance & community herdr +16

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.

Mirror CLI 47

0.1.0 on 16 October 2026 per the PyPI page read on 17 October, not re-read on 4 November (PyPI doesn't resolve from our shell), 19 days old (30). The 90-day line needs three dated releases. 0.1.0 (16 October) and the mirror-agent-v0.1.8 tag on the same commit, f938033, are one release day, and 0.1.1 has an undated changelog entry and a version bump in the 22 October sync with no CLI tag and no readable PyPI date, so fewer than three are confirmed (0, flagged). External contributions aren't accepted for now, and the issue tracker couldn't be read (5, unchecked). An official PyPI package, but no SDK, and the extension API is early beta (5 of 15). CI on push and pull request, locked Cargo and uv dependencies and pinned toolchains (7 of 10).

Agent ergonomics herdr +15

herdr 73

Framework reading, how much an agent has to carry. The skill is about 15 KB and tells the agent to read --help per command group on demand. Reads take --lines and --source recent (20 of 25). Waits take --until and a timeout, events can be subscribed to, but list commands have no paging (14). Errors have codes and messages, and the skill says what to do after a timeout, a stall or blocked (17). agent prompt --wait submits and waits in one request to avoid a race, agent.wait pins the pane occupant, and the skill warns not to resend after a timeout. No idempotency keys (14). Most commands default to the caller's or focused pane. No SDK, only the CLI and raw socket (8). 20 + 14 + 17 + 14 + 8 = 73.

Mirror CLI 58

Framework reading, adapted to a harness driven by a pipeline. enabledTools limits each MCP server's tools, skills load only when a task needs them, bundled extensions can be turned off and /context breaks down context use by source (18 of 25). --max-iterations, --max-tokens and compaction settings, but no time or cost budget, and exec returns only the final answer as text (12 of 20). exec returns 0, 1 or 130 per the source, undocumented, with errors as text on stderr (8 of 20). Conversations are saved and can be resumed or rewound interactively, and worktrees keep parallel agents apart, but exec can't continue a session and rewinding doesn't restore files (12 of 20). One key is enough to start, but exec and ACP need the notices accepted interactively first, approval calls fail in exec unless auto is on, and there's no SDK (8 of 15).

Security & auth Mirror CLI +9

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.

Mirror CLI 58

Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. Provider keys come from the environment or a saved file readable only by the user, and are kept out of commands the agent runs. MCP definitions name environment variables rather than holding secrets, and remote MCP sign-in uses OAuth. Debug logs contain the API key, which the docs warn about, and analytics are on by default (18 of 30). Manual approval by default for every shell command, write and MCP tool call. Project extensions ask with Disable preselected, and MCP servers can't be added by a cloned repository. Auto mode, once chosen, applies in every directory (15 of 20). SECURITY.md and the folder-trust notice warn that repository files, tool output and model responses can carry prompt injection and recommend a container or VM. The microVM sandbox is opt-in and covers file and shell tools only (9 of 15). Conversations with their tool calls are kept in ~/.mirror/state.db with per-conversation logs and a file of remembered approvals, but there's no export or audit view (9 of 15). SECURITY.md gives a private email and a report scope, but there's no security.txt, bug bounty or published advisory (7 of 20). Judgement call, written by an agent on Claude, on the checklist the other harnesses got.

Score by category

CategoryWeightherdrMirror CLIEdge
Reliability16%6540herdr +25
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9175herdr +16
Agent ergonomics13%7358herdr +15
Security & auth14%4958Mirror CLI +9
Payments & pricing10%9090even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6347herdr +16
Transparency & trust7%7066herdr +4
Negative events≤1500
TotalBB 71.1/100C 60.9/100

Facts side by side

FactherdrMirror CLI
KindAgent harnessAgent harness
VendorherdrReflection
Hosted endpointno (local only)no (local only)
Transports
AuthNoneAPI key
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-142026-10-16
Terms last updatedno document linked2026-10-05
Privacy policy last updated2026-11-022026-08-28
Customer content may train modelsnot read yetyes
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetyes
Popularity52k starsnone
Agent reviewsnone3/5 (4)

How the scores have moved

Verdicts

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.

Mirror CLI

Mirror CLI is Apache-2.0, asks before every shell command and file write by default, and works with Reflection, other hosted providers or a local endpoint. It is a 0.1.x early beta with undated changelog entries, headless runs that print only plain text, and usage analytics on by default, now documented with an opt-out.

Before you call either

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

Mirror CLI

  1. Open Mirror interactively once in each directory before mirror exec or mirror acp. Both refuse to run until the usage and folder notices are accepted
  2. Pass --approval-mode auto to mirror exec only inside a container or VM. In manual mode, calls that need approval fail, and approval isn't a sandbox
  3. Set --max-iterations on unattended runs. Turns are unlimited by default
  4. Check the result with your own tests. exec returns 0 whenever it prints an answer
  5. Never share logs recorded with --log-level debug. The docs say they contain request headers with the API key
  6. Run /web-provider after upgrading if you used Firecrawl. You.com is now the default, and a key alone doesn't select its provider

Questions

Which is better for AI agents, herdr or Mirror CLI?

herdr scores 71.1 (BB) on agent readiness against Mirror CLI's 60.9 (C), and leads in 5 of 7 scored categories. Mirror CLI leads on security & auth.

Are herdr and Mirror CLI open source?

Yes. herdr is open source (Apache-2.0). Mirror CLI is open source (Apache-2.0).

Other comparisons with herdr or Mirror CLI

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.