From 8a6d697308162874a236c84aac0b0f8c7ac01f83 Mon Sep 17 00:00:00 2001 From: Ogulcan Celik Date: Tue, 1 Sep 2026 14:48:45 +0300 Subject: refactor: separate website presentation from runtime --- website/src/pages/compare.astro | 265 ---------------------------------------- 1 file changed, 265 deletions(-) delete mode 100644 website/src/pages/compare.astro (limited to 'website/src/pages/compare.astro') diff --git a/website/src/pages/compare.astro b/website/src/pages/compare.astro deleted file mode 100644 index 315d6a1b..00000000 --- a/website/src/pages/compare.astro +++ /dev/null @@ -1,265 +0,0 @@ ---- -import SiteLayout from '../components/SiteLayout.astro'; ---- - - -
-
-
-
compare
-

Apps manage the herd. Herdr runs it.

-

- Most tools Herdr gets compared to are apps: a window you open to - manage coding agents, and a window the work depends on. Herdr is a - different kind of thing: a runtime. A server holds real terminals - open on the machine, the agents live in those, and every UI, ours - included, is just a client that attaches. Keep that split in mind - and the matrix below mostly explains itself. -

-
- -
- -
-
- herdr against the field - scrolls sideways on a phone -
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
capabilityherdrtmux · zellijcmux · warpsoloconductor · emdash · superset
Kind of thingruntime + clientsterminal multiplexerterminal appprocess dashboardmanager app
Work survives its own UI closingyes, the server owns the terminalsyes, detachsession restorewhile the app is openwhile the app is open
Runs inside your existing terminalyesyesreplaces itno, desktop appno, desktop app
Semantic agent stateblocked · working · done · idle—attention cuesprocess statusworkspace status
Detach, reattach, SSH inyes, any ttyyespartial—remote projects
Direct attach to one agentyes————
API agents drive themselvesread · send · wait · split · attachterminal scriptingapp APIsMCP for processesworkflow APIs
Worktree and diff review flowpairs with it—partial—yes, their core
Clients on the same runtimeTUI · CLI · plain SSH, more comingits own clientthe app onlythe app onlythe app only
-
-

- The columns are categories, not enemies: Herdr pairs happily with a - worktree manager and runs fine inside a fancy terminal. - The row that sorts the field is the second one: what happens to - the agents when the thing you're looking at goes away. -

-
- -
-
-
01
-
-

Herdr is the runtime.

-

- A server owns the terminals; every UI is a client of it. The TUI in - the screenshots attaches, detaches and even crashes without the - agents noticing. Same for the CLI, plain SSH, and whatever - attaches next. The TUI is the first client, not the last. -

-
- -
-
-
02
-
-

Multiplexers persist terminals, not agents.

-

- tmux gave humans persistence, and Herdr keeps that whole - inheritance: real PTYs, detach, SSH. What it adds is the part - multiplexers never had: knowing which pane is an agent, whether - it's blocked, and how to wait on it instead of polling it. -

-
- -
-
-
03
-
-

Terminal apps replace your terminal.

-

- cmux and Warp can be genuinely polished, but the deal is that the - work moves into their window, with their renderer, on the machines - they support. Herdr changes nothing about your terminal. It runs - inside it, wherever a terminal and SSH already reach. -

-
- -
-
-
04
-
-

Manager apps are clients without a runtime.

-

- Conductor, Emdash and Superset manage a herd from a window: - worktrees, diffs, review queues. Useful, and Herdr pairs fine with - that flow. But a window that manages agents is not a place agents - live: quit the app and the herd goes with it. -

-
- -
-
-
05
-
-

Dashboards watch processes.

-

- Solo supervises a dev stack: health, restarts, logs. Herdr's job - is different: interactive agent terminals that stay open, hold - scrollback and state, and stay yours whether or not anything is - watching them. -

-
- -
-
- -
-
- one-liners, for deciding fast -
-
-
- herdr vs tmux -

tmux keeps terminals alive; so does Herdr. The difference is Herdr knows which terminals are agents, what state each one is in, and how to wait on them. tmux sees panes.

-
-
- herdr vs zellij -

Zellij is a friendlier workspace for humans in terminals. Herdr is a runtime for agents in terminals: state, waits, direct attach, and an API.

-
-
- herdr vs cmux -

cmux is a Mac terminal app built around agents. Herdr isn't an app: it's the runtime underneath, in whatever terminal you already use, reachable over SSH.

-
-
- herdr vs warp -

Warp wants to be your terminal and your platform. Herdr keeps your terminal and owns what runs inside it.

-
-
- herdr vs opencode web -

opencode's web mode serves one agent over HTTP. Herdr runs the whole herd: any agent CLI, many at once, from any tty.

-
-
- herdr vs solo -

Solo is a dashboard that supervises your dev processes. Herdr holds interactive agent terminals open whether or not anything is watching them.

-
-
- herdr vs conductor, emdash, superset -

Manager apps put worktrees, diffs and review queues in a window. Herdr is the layer under that kind of window: quit their app and the agents stop; detach every Herdr client and they don't.

-
-
-
- -
- -
-

A runtime, not another window.

-

- Install it and nothing about your setup changes: same terminal, same - agent CLIs. They just stop dying when a window does. -

- -
-
-
-
-- cgit v1.2.3