Head to head · Multi-agent orchestration · October 2026 research run
Amp vs herdr
herdr scores 71.1 (BB) on agent readiness against Amp's 57.8 (C), and leads in 4 of 7 scored categories. Amp leads on security & auth, maintenance & community and transparency & trust. Both do multi-agent orchestration.
Best agent harnesses and coding agents · All 1767 harnesses comparisons
Which one, for what
Amp C
Best for Teams that want a hosted, multi-model coding agent with shared threads and cloud machines, driven from scripts through execute mode or the SDKs.
Ahead on
- Security & auth, 57 against 49
- Maintenance & community, 79 against 63
- Transparency & trust, 77 against 70
Watch for
The tools page says Amp does not ask for approval before running tools, and control needs a custom plugin
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 23
- Schema & documentation, 91 against 72
- Payments & pricing, 90 against 53
Also in its favour
- Agent-ready, a grade of BB or better
- No key needed to call it
- Open source
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.
Reliability herdr +42
Amp 23
Local-package reading, as for the other closed-source harnesses. An install script that verifies a SHA-256 checksum, and an @ampcode/cli npm package of prebuilt binaries, for macOS, Linux and Windows through WSL, per the 8 October check (20). The source repository is private, so there is no public CI or test suite (0). There is no public issue tracker, and bug reports go to the vendor from inside the product. The 8 October reading of the status page's incident feed is struck, because ampcodestatus.com's robots.txt now disallows ClaudeBot, Claude-Web and anthropic-ai, so nothing is left to count crash or regression reports against (0). Versions are build stamps such as 0.0.1792627309-g98c009 with no per-version notes, and the introduction says "No backward compatibility", though removals are announced with dates in the Chronicle (3). The version line is 0.0 and we found no statement that the CLI is stable (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.
Payments & pricing herdr +37
Amp 53
Harness reading of the published rubric. No payment protocol (0). The pricing page is public. Hobby is free, Megawatt is $20 a month with 45,000 orb minutes, orbs are priced per hour by size from $0.08, and paid credits are charged at provider API prices with no markup outside Enterprise. Gigawatt is $200 a month with $200 of agent usage and 1,000 hours of a1.xxlarge orbs, per the pricing docs (20). Hobby is free when you bring your own model key or subscription and run locally or on your own runner. The pricing page does not say whether sign-up asks for a card, and inference served by Amp is never free (15). A person signs in through a browser to create the access token (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.
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.
Schema & documentation herdr +19
Amp 72
Framework reading. A JSON Schema for the settings file at ampcode.com/cli-settings.schema.json (22 properties), TypeScript types for every stream message, and a generated reference for the plugin API, but no OpenAPI for the server (18). ampcode.com/llms.txt indexes a raw Markdown rendition of each of 55 docs pages (10). The docs say when to use execute mode, orbs, runners, the oracle and the Librarian, and what each mode is for (15). Settings carry types and defaults, and the stream schema enumerates stop reasons, result subtypes and MCP server states (12). Examples on nearly every page and two result error subtypes (error_during_execution, error_max_turns), with no exit codes or error catalogue (9). Dated Chronicle posts with an RSS feed and a lastModified date on each docs page, but no changelog by CLI version (8).
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.
Maintenance & community Amp +16
Amp 79
The security page names CLI build 0.0.1792627309-g98c009 in its 22 October 2026 update, and the Chronicle's newest post is Service Accounts on 3 November 2026 (30). The Chronicle has 44 dated posts from 6 August to 3 November, and npm listed 678 CLI versions between 10 July and 8 October per the 8 October check (20). No public tracker. Support is in-product bug reports, a Discord server, email and X. Reply times aren't visible (10). @ampcode/sdk on npm released on 18 September 2026, per the 8 October check, and the SDK docs cover TypeScript and Python (15). No public CI, builds carry no notes, and the installer checks a checksum (4).
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.
Security & auth Amp +8
Amp 57
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. Every thread, with messages, code used as context and tool results, is stored on Amp's servers, and there is no local-only or self-hosted mode. Training on user data is off unless a user opts in, provider retention is limited under Minimal Data Retention, and secrets are redacted before they leave the client on a best-effort basis. The terms allow collection of usage data and we found no opt-out for the CLI (14). The tools page says Amp does not ask for approval before running tools, and points to a custom plugin for control. MCP servers defined in a project's settings need approval, amp.mcpPermissions allows or rejects servers and amp.tools.disable removes tools. The CLI has no sandbox. Orbs are separate cloud machines (6). The security reference has a prompt-injection section that describes layered measures, and the tools page warns about untrusted repositories and MCP servers (9). Threads keep prompts, tool calls and results as a record, a data API covers workspace analytics and threads, and authentication audit logs are for Enterprise workspaces (12). A security.txt that expires on 20 November 2026 (still valid on 4 November), a bug bounty with safe harbour, SOC 2 Type II and annual penetration tests per the vendor. On 22 October 2026 the security page posted an update that removes trust in compromised certificate authorities and names the CLI build to install. No CVEs found (16).
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.
Transparency & trust Amp +7
Amp 77
Closed source under the Amp licence terms from Amp Frontier Corporation, with the npm packages marked Amp Commercial License. The terms page shows no date (15). The security reference lists 19 providers and what each sees, says deleted threads are removed within 30 days, diagnostic data after 7 days and audit logs kept at least 30 days, and the privacy policy (modified 10 September 2026) agrees, with account data kept while the account is active (24). No deprecation policy. The terms allow any part of the Services to be discontinued without notice, while removals so far were announced with dates, such as the old npm package names on 14 May 2026 for removal on 15 June (8). Amp is local software tied to a hosted service. Providers and US hosting are disclosed in detail, but the usage data the client sends is not itemised and has no documented opt-out (12).
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.
Score by category
| Category | Weight | Amp | herdr | Edge |
|---|---|---|---|---|
| Reliability | 16% | 23 | 65 | herdr +42 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 72 | 91 | herdr +19 |
| Agent ergonomics | 13% | 69 | 73 | herdr +4 |
| Security & auth | 14% | 57 | 49 | Amp +8 |
| Payments & pricing | 10% | 53 | 90 | herdr +37 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 79 | 63 | Amp +16 |
| Transparency & trust | 7% | 77 | 70 | Amp +7 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 57.8/100 | BB 71.1/100 |
Facts side by side
| Fact | Amp | herdr |
|---|---|---|
| Kind | Agent harness | Agent harness |
| Vendor | Amp Frontier Corporation | herdr |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | OAuth or key | None |
| Pricing | Freemium | Free |
| x402 | no | no |
| Licence | Proprietary, under the Amp licence terms (Amp Frontier Corporation). The npm packages are marked Amp Commercial License and the source repository is private | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-22 | 2026-10-14 |
| Terms last updated | no date given | no document linked |
| Privacy policy last updated | 2026-09-10 | 2026-11-02 |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Popularity | 41k npm/wk | 52k stars |
How the scores have moved
Verdicts
Amp
Execute mode streams JSON in a format close to Claude Code's, with TypeScript and Python SDKs, and the security reference names each provider and what it sees. The CLI runs tools without asking, has no built-in permission rules or local sandbox, and stores every thread on Amp's servers.
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
Amp
- Run unattended jobs in a container or VM. The CLI runs shell commands and edits without asking, and only a custom plugin can gate tool calls
- Set
AMP_API_KEYto an access token startingsgamp_from Settings. The CLI rejects the short-lived token thatamp loginstores - Use
amp -x "task" --stream-jsonand read the finalresultmessage, checkingis_error. Exit codes are not documented - Set
AMP_SKIP_UPDATE_CHECK=1oramp.updates.modetodisabledin CI, and pin a build. Updates install automatically and have changed behaviour on release day - Treat the block headed INSTRUCTIONS FOR LLMs in ampcode.com page source as vendor copy, and take facts from the docs Markdown
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, Amp or herdr?
herdr scores 71.1 (BB) on agent readiness against Amp's 57.8 (C), and leads in 4 of 7 scored categories. Amp leads on security & auth, maintenance & community and transparency & trust.
Are Amp and herdr open source?
No open-source release is listed for Amp. herdr is open source (Apache-2.0).
Other comparisons with Amp or herdr
- Agent Zero vs Amp
- Aider vs Amp
- Amp vs Antigravity CLI
- Amp vs Auggie CLI
- Amp vs AXLR
- Amp vs boxes.dev
- Amp vs Claude Code
- Amp vs Click
- Amp vs Cline
- Amp vs Conductor
- Amp vs Crush
- Amp vs Cursor CLI
- Amp vs DeepSeek Harness (dsh)
- Amp vs dsh-superagent (DeepSeek)
- Amp vs Devin
- Amp vs Droid CLI
- Amp vs Pi
- Amp vs Emdash
- Amp vs Friday
- Amp vs Gemini CLI
- Amp vs GitHub Copilot CLI
- Amp vs goose
- Amp vs Harness²
- Amp vs HarnessRouter
- Amp vs Jules
- Amp vs Junie CLI
- Amp vs Kilo Code CLI
- Amp vs Kimi Code CLI
- Amp vs Kiro CLI
- Amp vs Letta
- Amp vs mini-swe-agent
- Amp vs MiniMax Code
- Amp vs Mistral Vibe CLI
- Amp vs Muse Code
- Amp vs OpenAI Agents API
- Amp vs OpenAI Codex
- Amp vs OpenCode
- Amp vs OpenHands
- Amp vs OpenMausBot
- Amp vs Orca
- Amp vs Paseo
- Amp vs Prime Agent
- Amp vs Qoder CLI
- Amp vs Qwen Code
- Amp vs Mirror CLI
- Amp vs Rovo Dev CLI
- Amp vs Sculptor
- Amp vs T3 Code
- Amp vs Traycer
- Amp vs Unstoppable
- Amp vs Verdent
- Amp vs Vibe-Trading
- Amp vs Warp (Warp Agent CLI and the Oz Agent API)
- Agent Relay vs Amp
- Agent Relay vs herdr
- Amp vs Clawboo
- Amp vs CLI Manager
- Amp vs Harness
- Amp vs Paperclip
- Amp vs Parallax
- Antigravity CLI vs herdr
- Auggie CLI vs herdr
- AXLR vs herdr
- boxes.dev vs herdr
- Claude Code vs herdr
- Clawboo vs herdr
- 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 herdr
- Gemini CLI vs herdr
- GitHub Copilot CLI vs herdr
- goose vs herdr
- Harness vs herdr
- HarnessRouter vs herdr
- 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/amp-vs-herdr.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/amp.json·/api/v1/tools/herdr.json - From a terminal
anchor compare amp herdr(the CLI) - Over MCP
compare_tools {"a": "amp", "b": "herdr"}at/mcp, no key