herdr Deep Research: The Terminal Runtime Where Coding Agents Manage Themselves
> "The runtime your coding agents live on" — an in-depth study of herdrdev/herdr (local clone at c:/github/herdr), verified 2026-08-13 against the repo, official site, GitHub API, and independent media.
Key points
- What it is: A single-binary Rust terminal runtime (ratatui + crossterm + patched portable-pty, ~224k lines) that hosts coding agents. It runs *inside* your existing terminal (WezTerm/iTerm2/Kitty/Windows Terminal); a background server owns the PTYs, pane state, layouts, and agent identities, while any TUI client is just a detachable visitor.
- Five-state semantics:
blocked(needs your approval),working,done(unseen output),idle,unknown. Detection uses lifecycle hooks for first-party integrations (Pi, OMP, Kimi, OpenCode, Kilo, MastraCode) and screen manifests (bottom-buffer snapshots + TOML rules) for Claude Code, Codex, Cursor Agent CLI, Copilot, Devin, Grok, Qwen Code, and others — 20 agents covered. One status authority per pane; blocked detection is deliberately conservative, and misclassification never triggers input. - Agent-to-agent orchestration: A socket API (Unix socket / Windows named pipe, JSON Schema exportable) plus a bundled agent skill. Agents receive
HERDR_WORKSPACE_ID/TAB_ID/PANE_IDand can split panes, start sibling agents, prompt, wait, and read output — with a stalled-prompt guard (agent_prompt_stalledafter 5s without lifecycle change). - Performance: v0.8.0 removed spinner animations, renders for hidden panes, and redraws on mouse movement — 89–95% total CPU reduction (e.g., 10 panes × 3 clients: 13.014% → 0.617%; silent working pane: 1.467% → 0.133%). The blog admits the limit: 50 busy panes improve only 23.6%, since the bottleneck is PTY reads and terminal parsing itself.
- Persistence tiers: detach/reattach preserves everything; server restarts keep layout and rely on native resume (17 agents supported, e.g., Claude
--resume, Codexresume); an experimentalupdate --handoffattempts full continuity. Pane history replay is off by default because terminal output may contain secrets. - Local-first: no accounts, no telemetry, no cloud sync; sessions stored as JSON in
~/.config/herdr. Only network contact is an optional (disable-able) manifest hot-update check. - License & funding: Relicensed from AGPL-3.0 to Apache-2.0 on 2026-07-22 (commit
cd5ea1be), *before* announcing YC F26 on 2026-08-06, with a public promise that the runtime stays free and open source. Commercialization targets multi-machine sync and extra clients built *on top of* the runtime. - Traction & contributors: First release 2026-03-27; by 2026-08-13 — 28,337 stars, 2,009 forks, 380,624 downloads across 79 releases, 500+ marketplace plugins (Raycast extension, Stream Deck panel, community iOS client). Still essentially a one-person project (Ogulcan/Can Celik: 1,179 + 73 commits), with DHH contributing 9 commits since 2026-08-09.
- Primary: local repo
c:/github/herdr(HEAD952729ee) — README, CHANGELOG (v0.1.0–0.8.0), AGENTS.md,src/detect/manifests/claude.toml, skills/herdr/SKILL.md, docs, git history - GitHub API: api.github.com/repos/herdrdev/herdr (stars/forks/releases)
- Official blog: herdr.dev (YC announcement 2026-08-06; "Ten agents, three clients, 95% less CPU" 2026-08-03; "Coding agents are becoming runtimes" 2026-06-10)
- Independent: byteiota.com, runtimewire.com, dev.to review, chaseai.io
Herd metaphors and how it compares
The README's metaphor: shepherding ten agents across ten terminals means personally checking each one; herdr is the shepherd living at the center of the pastures. Against competitors: tmux/zellij persist terminals but don't understand agent state; cmux/Warp/Solo/Conductor are management apps that die with their windows; herdr is a *runtime* whose server holds real terminals, exposing both mouse and prefix-key interaction as first-class citizens.
Honest limitations
1. Screen-manifest detection is a cat-and-mouse chase (e.g., a patch for Claude Code's spinner changing from Braille dots to a half-circle in 2.1.228); unfamiliar UIs may be misread as idle — display-only, never destructive.
2. Remote manifest delivery is a trust surface (disable via [update] manifest_check = false; local overrides win; SHA-256 verification in unreleased builds).
3. Windows remains beta (bundled ConPTY).
4. Multi-machine orchestration (laptop + VPS + sandbox) is still a vision; today it's SSH, single machine.
5. Plugins run unsandboxed with your user privileges; pane history replay is off by default.
6. Single-founder-to-startup transition risk, though the Apache-2.0 commitment is the current insurance.
Conclusion
herdr fills a real gap in the multi-agent era: agents proliferated, but nobody built the tools to supervise them. Its answer is classical — don't build an agent, build the pen and the shepherd. Strict architecture rules (state/runtime separation, pure-function rendering, evidence-based detection), a performance blog that candidly admits where it fails, and licensing integrity ahead of YC funding make it worth a try — especially if you juggle three or more coding agents daily.