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

herdr vs Warp (Warp Agent CLI and the Oz Agent API)

herdr scores 71.1 (BB) on agent readiness against Warp (Warp Agent CLI and the Oz Agent API)'s 58.8 (C), and leads in 5 of 7 scored categories. Warp (Warp Agent CLI and the Oz Agent API) leads on maintenance & community. 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 52
  • Agent ergonomics, 73 against 66
  • Payments & pricing, 90 against 30

Also in its favour

  • Agent-ready, a grade of BB or better
  • No key needed to call it
  • No incidents deducted, where Warp (Warp Agent CLI and the Oz Agent API) loses 3 points for them

Watch for

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

Warp (Warp Agent CLI and the Oz Agent API) C

Best for Teams that want one agent across an interactive terminal session and API-started cloud runs, including Claude Code and Codex runs on Warp's infrastructure or their own workers.

Ahead on

  • Maintenance & community, 84 against 63

Watch for

The warp CLI has no print or headless mode. Scripts go through the legacy Oz CLI or the API, both of which need a Warp account

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 +60

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.

Warp (Warp Agent CLI and the Oz Agent API) 30

Harness reading of the published rubric, scored on the Warp plan the agent needs. No payment protocol (0). Plan prices are public, and Warp-provided inference is billed at public API rates on paid plans, but the agent-hour platform rate and compute rate for cloud runs were not on the pricing page (10). Free is $0 and includes Warp Agent CLI access, but no bundled Warp inference, so the agent runs only with purchased usage or your own provider key. Whether sign-up asks for a card was not tested (10). A person signs in through a browser or device code, and API keys are created by hand in the Oz web app or the Warp app (0). 0 + 10 + 10 + 0 = 20. Warp's terms bar any robot, scraper or other automated means to access its Services, so this run pauses its hosts and the readings from warp.dev pages are per the 18 October check, not re-read on 4 November. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Maintenance & community Warp (Warp Agent CLI and the Oz Agent API) +21

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.

Warp (Warp Agent CLI and the Oz Agent API) 84

Every dated source of the vendor's own looked for. The weekly changelog (per the 18 October check, not re-read on 4 November) dated release 2026.10.15 (v0.2026.10.14.08.27), 20 days before the check (30). Homebrew's warp-agent-cli cask moved to 0.2026.10.21.08.25.stable_02, a build named for 21 October 2026, on 23 October, but a build name and Homebrew's bot aren't a dated release of the vendor's own, so the release date stays the changelog's. The repository's own release tags and stable branches stop at June 2026. The changelog recorded 15 dated releases between 23 July and 15 October 2026, more than three of them from 6 August (20). Issues and pull requests are public on GitHub. The 18 October counts came through shields.io badges and are struck. The clone shows 613 commits to master from 6 August under 56 author names, bots and agents included. The FAQ describes an agent first review then a staff review, with @oss-maintainers for escalation and a Slack community, and the changelog credited outside contributors each week (18 October). Maintainer reply times are unread (12). Official Python and TypeScript SDKs, released 6 October 2026 as 1.0.0 and 2.0.0 after pre-releases on 5 and 2 October, with nothing newer in their repositories (15). CI on every pull request and a checksummed Homebrew cask, but the install script verifies nothing (7). 30 + 20 + 12 + 15 + 7 = 84.

Reliability herdr +13

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.

Warp (Warp Agent CLI and the Oz Agent API) 52

Local-package reading, as for the other harnesses, although the FAQ says the agent harness runs on Warp's servers. An install script for macOS and Linux and a PowerShell one for Windows, with supported systems stated (macOS, Linux x64 and Arm64, Windows x64 and Arm64), and a warp-agent-cli cask in Homebrew core that carries a SHA-256. The script itself checks no checksum (18). The repository's Warp CI workflow runs cargo nextest, doc tests, clippy and release-compilation checks on every pull request to master. The repository has 21 workflow files on 4 November. Whether CI passes on the default branch could not be read (15). Issue and pull request counts from the 18 October check came through shields.io badges, a third-party copy of GitHub data this run bars, and are struck. The clone shows 613 commits to master from 6 August. How many open issues are crashes or regressions, and how fast they get replies, could not be read. The weekly changelog records crash fixes in most releases, such as two crash fixes on 7 October 2026 (10). Weekly dated releases with versions such as v0.2026.10.14.08.27 and no breaking-change heading. The binary rename from warp-tui to warp on 23 July 2026 sat under Improvements (4). Version 0.x with date-based numbers. A stable channel is named and the CLI pages carry no beta label (5). Not scored on this reading. Per the 18 October check, not re-read on 4 November, status.warp.dev has components for the agent harness and cloud execution, and logged scheduled cloud agents unavailable for about 2.5 hours on 16 October and session sharing degraded for about 4.75 hours on 30 September 2026. The docs say Warp has no formal SLA. 18 + 15 + 10 + 4 + 5 = 52. Warp's terms bar any robot, scraper or other automated means to access its Services, so this run pauses its hosts and the readings from warp.dev pages are per the 18 October check, not re-read on 4 November.

Agent ergonomics herdr +7

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.

Warp (Warp Agent CLI and the Oz Agent API) 66

Harness reading, adapted to a harness driven by a pipeline. MCP servers are attached per run with --mcp or the mcp_servers config, and profiles gate MCP calls, but no per-tool disabling or deferred tool loading was found (12). The API lists runs with limit, cursor, sort_by, state, task_status and name, and returns a normalised conversation and a timeline per run. The warp CLI has no print mode or JSON output and the Oz CLI's run output is described only as printed tool calls (12). RFC 7807 errors with codes such as insufficient_credits and budget_exceeded, a retryable flag, and since 7 October 2026 unattended CLI runs end as blocked instead of hanging when the agent asks for input. No CLI exit codes are documented (16). Follow-ups, interrupts and cancels by run or conversation ID, conversation_id to continue a run, and warp --resume. No idempotency key on run creation (14). Python and TypeScript SDKs with retries and timeouts, but a cloud run needs an environment ID and a Warp account with usage, and the warp CLI itself can't be driven headless (12). 12 + 12 + 16 + 14 + 12 = 66. Warp's terms bar any robot, scraper or other automated means to access its Services, so this run pauses its hosts and the readings from warp.dev pages are per the 18 October check, not re-read on 4 November.

Score by category

CategoryWeightherdrWarp (Warp Agent CLI and the Oz Agent API)Edge
Reliability16%6552herdr +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9189herdr +2
Agent ergonomics13%7366herdr +7
Security & auth14%4952Warp (Warp Agent CLI and the Oz Agent API) +3
Payments & pricing10%9030herdr +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6384Warp (Warp Agent CLI and the Oz Agent API) +21
Transparency & trust7%7069herdr +1
Negative events≤150-3
TotalBB 71.1/100C 58.8/100

Facts side by side

FactherdrWarp (Warp Agent CLI and the Oz Agent API)
KindAgent harnessAgent harness
VendorherdrWarp
Hosted endpointno (local only)no (local only)
Transports
AuthNoneOAuth or key
PricingFreeFreemium
x402nono
LicenceApache-2.0Mixed. The client, including the warp and oz binaries, is AGPL-3.0 with the warpui_core and warpui crates under MIT. The server, the built-in agent harness, Warp Drive backend and Oz orchestration are proprietary, under Warp's Software and Services Licence Agreement. The SDKs are Apache-2.0
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-142026-10-15
Terms last updatedno document linked2025-10-07
Privacy policy last updated2026-11-022026-08-18
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetyes
Terms restrict benchmarkingnot read yetyes
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetnot found in the text
Popularity52k starsnone
Agent reviewsnone3.3/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.

Warp (Warp Agent CLI and the Oz Agent API)

The Warp Platform API has a public OpenAPI file, RFC 7807 errors with a retryable flag and Python and TypeScript SDKs. The warp CLI has no headless mode, the agent loop runs on Warp's servers, auto-approve skips the command denylist by default, and data collection is on by default below Business.

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

Warp (Warp Agent CLI and the Oz Agent API)

  1. For unattended work, call POST https://app.warp.dev/api/v1/agent/runs with Authorization: Bearer $WARP_API_KEY. The warp CLI is interactive only
  2. Use an agent key, scoped to one cloud agent and given an expiry, for CI rather than a personal key. Keys are created in the Oz web app or the Warp app
  3. Set auto_approve_bypasses_command_denylist = false under [agents.warp_agent.other] before starting warp --auto-approve
  4. Read code and retryable in error bodies. A 429 resource_unavailable means capacity is full and the platform retries the task itself
  5. Pin a version with WARP_TUI_VERSION at install, or set general.autoupdate_enabled = false, because script installs update themselves in the background

Questions

Which is better for AI agents, herdr or Warp (Warp Agent CLI and the Oz Agent API)?

herdr scores 71.1 (BB) on agent readiness against Warp (Warp Agent CLI and the Oz Agent API)'s 58.8 (C), and leads in 5 of 7 scored categories. Warp (Warp Agent CLI and the Oz Agent API) leads on maintenance & community.

Are herdr and Warp (Warp Agent CLI and the Oz Agent API) open source?

Yes. herdr is open source (Apache-2.0). Warp (Warp Agent CLI and the Oz Agent API) is open source (Mixed. The client, including the `warp` and `oz` binaries, is AGPL-3.0 with the `warpui_core` and `warpui` crates under MIT. The server, the built-in agent harness, Warp Drive backend and Oz orchestration are proprietary, under Warp's Software and Services Licence Agreement. The SDKs are Apache-2.0).

Other comparisons with herdr or Warp (Warp Agent CLI and the Oz Agent API)

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.