herdr Orchestration

The top-level agent is the controller (Codex, Claude, Fable, or another); it delegates to worker TUIs that gather evidence, draft bounded patches, run tests, and report. The controller owns assignment, state, conflict control, verification, integration, and the final user-facing answer. herdr is the substrate: panes host the worker TUIs, and the socket CLI (herdr …) gives the controller placement, input, screen reads, and native agent-status waits.

Workers are TUIs — no headless runners

A worker is an interactive TUI — claude or codex — launched in a herdr pane with herdr agent start. The whole orchestration loop hangs on this: herdr's agent-state integrations hook the interactive TUIs, so wait agent-status, agent list, and blocked/done detection exist only while a real TUI is on screen.