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

herdr vs Kimi Code CLI

herdr scores 71.1 (BB) on agent readiness against Kimi Code CLI's 61.8 (C), and leads in 4 of 7 scored categories. Kimi Code CLI 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

  • Schema & documentation, 91 against 85
  • Transparency & trust, 70 against 62

Also in its favour

  • Agent-ready, a grade of BB or better
  • No key needed to call it
  • No incidents deducted, where Kimi Code CLI loses 8 points for them

Watch for

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

Kimi Code CLI C

Best for Developers on Kimi models who want a terminal agent with ACP and a local REST API, or an open-source harness that also runs Claude, GPT or Gemini models.

Ahead on

  • Maintenance & community, 72 against 63

Also in its favour

  • Free to start without a card

Watch for

Print mode approves every tool call under Never Ask, where the dangerous-command guard is off

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.

Maintenance & community Kimi Code CLI +9

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.

Kimi Code CLI 72

2.4.1 on 30 October 2026 (30). 30 stable tags from 0.32.0 on 4 August to 2.4.1 on 30 October, plus canary builds since 29 October (20). The 18 October counts from shields.io badges are struck. The clone shows the pace directly, 95 commits from 13 authors between 18 October and 2 November and pull requests numbered past #4600, with the changelog crediting outside contributors in each release. Issue reply times couldn't be read (11). No published SDK. A TypeScript SDK sits in the repository (@moonshot-ai/kimi-code-sdk 0.22.0) marked private, the ACP server and REST API ship inside the CLI, and Homebrew core is current at 2.4.1 (5). CI with a frozen lockfile, lint and a dependency check (sherif), canary and release workflows, no Dependabot or Renovate file, and the pass state unchecked (6). 30 + 20 + 11 + 5 + 6 = 72.

Transparency & trust herdr +8

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.

Kimi Code CLI 62

MIT (30). The docs have no privacy page for the CLI. The Kimi terms (effective 13 August 2026, NOVASCENT PRIVATE LIMITED, Singapore) let Moonshot use content to train its services unless the user opts out by email, prospectively only, and the Kimi privacy policy says content is used for training. The Kimi Platform privacy policy keeps inputs while the account is active. Neither says which applies to CLI sessions (12). The kimi server tree prints a deprecation notice until the next major version, a table names each deprecated config key and the version that replaced it, and the Python Kimi CLI was archived with a migration guide, though its notice gives no date for when old installations stop working (13). Telemetry is documented as on, with a config key and an environment variable to turn it off, but what it collects isn't listed, and print mode ignored the opt-out until 0.41.0 (9).

Schema & documentation herdr +6

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.

Kimi Code CLI 85

Framework reading. The kimi web server serves /openapi.json and /asyncapi.json, generated from its runtime validation schemas, but only from a running server behind auth, and the API is marked experimental. The ACP server's methods and capabilities are tabled (20). llms.txt indexes every page and each page is served as Markdown (10). The permission-mode, goal-mode and MCP pages say when to use each mode and what to avoid (16). The config reference gives type and default for each key, with enums for permission modes, output formats and rule decisions (13). Many examples, the server's error-code bands and ACP error codes are documented, but print-mode exit codes are documented only for goal runs (11). A dated changelog in the docs plus the technical changelog in the repository (15). Unchanged on 2 November; llms.txt now indexes 60 pages in two languages.

Score by category

CategoryWeightherdrKimi Code CLIEdge
Reliability16%6568Kimi Code CLI +3
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9185herdr +6
Agent ergonomics13%7371herdr +2
Security & auth14%4945herdr +4
Payments & pricing10%9090even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6372Kimi Code CLI +9
Transparency & trust7%7062herdr +8
Negative events≤150-8
TotalBB 71.1/100C 61.8/100

Facts side by side

FactherdrKimi Code CLI
KindAgent harnessAgent harness
VendorherdrMoonshot AI
Hosted endpointno (local only)no (local only)
Transports
AuthNoneOAuth or key
PricingFreeFree
x402nono
LicenceApache-2.0MIT
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-142026-10-30
Terms last updatedno document linked2026-08-13
Privacy policy last updated2026-11-022026-08-13
Customer content may train modelsnot read yetyes, with an opt-out
Terms restrict automated accessnot read yetyes
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 stars37k npm/wk
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.

Kimi Code CLI

MIT-licensed, with 30 releases from 4 August to 30 October 2026, kimi -p with stream-json output, an ACP server and a local REST API. Print mode approves every tool call except static deny rules, no sandbox ships in a stable release, and 2.x minor releases changed behaviour without notice.

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

Kimi Code CLI

  1. kimi -p approves every tool call. Add [[permission.rules]] deny entries and run it in a container, since no sandbox ships
  2. Set KIMI_LOOP_MAX_STEPS_PER_TURN for unattended runs. Steps per turn are unlimited by default
  3. Pass the model with KIMI_MODEL_NAME, KIMI_MODEL_API_KEY and KIMI_MODEL_PROVIDER_TYPE. OPENAI_API_KEY or ANTHROPIC_API_KEY in the shell is ignored otherwise
  4. Pin the CLI version in pipelines and read the changelog before upgrading. Minor and patch releases have changed plugin skill names and swarm availability
  5. Set KIMI_DISABLE_TELEMETRY=1 and use 0.41.0 or later, since earlier print-mode runs ignored it

Questions

Which is better for AI agents, herdr or Kimi Code CLI?

herdr scores 71.1 (BB) on agent readiness against Kimi Code CLI's 61.8 (C), and leads in 4 of 7 scored categories. Kimi Code CLI leads on maintenance & community.

Are herdr and Kimi Code CLI open source?

Yes. herdr is open source (Apache-2.0). Kimi Code CLI is open source (MIT).

Other comparisons with herdr or Kimi Code 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.