The stack: each layer exposes its state to the one above
The tempting way to pick a terminal for agent work is comparing feature lists. This setup rejects that framing. It is four small layers, and the selection rule is visible in the configs: each layer exposes its state to the layer above.
Ghostty only draws pixels and forwards keys. Herdr (0.7.3, "terminal workspace manager for AI coding agents") runs as a client/server pair over a unix socket and surfaces the whole workspace โ tab โ pane model as CLI subcommands: workspace, tab, pane, agent, wait. The server keeps every pane alive with no window attached โ quit Ghostty entirely and herdr reattaches to everything. Pi (0.80.10) is the agent inside the panes; herdr's integration installs a pi extension that reports the agent's state โ idle, working, blocked โ back over the socket, so a workspace listing truthfully says which agents are busy because the agents report it themselves. Karabiner turns all of it into single keystrokes.
The test for your own setup: ask what your terminal will tell a script about its panes. If the answer is "nothing," everything below is out of reach regardless of features.
Two configs shake hands: keyboard to focused pane
Karabiner knows the keyboard but not which pane is focused. Herdr knows the focused pane but not global hotkeys. The handshake: Karabiner emits internal Ctrl+Alt+โฆ chords only while Ghostty is frontmost, and herdr's [[keys.command]] bindings translate each chord into a command that receives the focused pane's context. The herdr config states the design in a comment: "Karabiner emits these internal chords only while Ghostty is frontmost; Herdr supplies the exact focused inner pane."
Holding Esc turns the home row into a herdr command deck:
One layer up, a comma simlayer jumps between projects: , plus a letter focuses a workspace by label, falls back to matching panes by cwd, and creates the workspace if neither exists.
The three chords worth stealing (complete config)
Wire three chords, not thirty: open-cwd-in-editor, open-repo, and search-all-panes-to-focus. Three files. The helper script is a minimal, self-contained stand-in for the presenter's personal 1,200-line helper (see appendix) โ it needs herdr, jq, and per verb zed, gh, or fzf.
#!/bin/sh
# Focus-aware chord actions for a herdr session. chmod +x this file.
# Herdr injects HERDR_ACTIVE_PANE_ID when a [[keys.command]] binding fires.
set -eu
pane="${HERDR_ACTIVE_PANE_ID:-${HERDR_PANE_ID:?run from a herdr binding or pane}}"
cwd="$(herdr pane get "$pane" | jq -r '.result.pane.foreground_cwd')"
case "${1:-}" in
zed) zed "$cwd" ;;
repo) cd "$cwd" && gh repo view --web ;;
pane-search)
herdr pane list | jq -r '.result.panes[].pane_id' | while read -r p; do
herdr pane read "$p" --source recent-unwrapped --lines 200 2>/dev/null \
| grep -v '^[[:space:]]*$' | sed "s|^|$p |"
done | fzf --no-sort --tac | awk '{print $1}' | xargs -r -n1 herdr agent focus ;;
*) echo "usage: herdr-chords zed|repo|pane-search" >&2; exit 2 ;;
esac
# Karabiner emits these internal chords only while Ghostty is frontmost;
# Herdr supplies the exact focused inner pane.
[[keys.command]] # Esc+Z -> open focused pane's cwd in Zed
key = "ctrl+alt+z"
type = "shell"
command = "$HOME/.local/bin/herdr-chords zed"
[[keys.command]] # Esc+R -> open focused pane's GitHub repo
key = "ctrl+alt+r"
type = "shell"
command = "$HOME/.local/bin/herdr-chords repo"
[[keys.command]] # Esc+Space -> search every pane, jump to the hit
key = "ctrl+alt+shift+l"
type = "pane" # runs in a temporary pane; it closes after you pick
command = "$HOME/.local/bin/herdr-chords pane-search"
;; Goku / Karabiner-Elements. Tap Esc = normal Esc.
;; Hold Esc + key = chord, only while Ghostty is frontmost.
;; under :applications
:ghostty ["com.mitchellh.ghostty"]
;; under :layers โ hold-Esc layer; tap still sends Esc
:escape-mode {:key :escape
:params {:basic.to_if_alone_timeout_milliseconds 200
:basic.to_if_held_down_threshold_milliseconds 200}
:alone [{:key :escape}]}
;; under :main โ the three chords
{:des "Ghostty: Escape Mode Herdr actions"
:rules [[:condi :ghostty :escape-mode]
[:-z {:key :z :modi [:left_control :left_option]}] ; Esc+Z
[:-r {:key :r :modi [:left_control :left_option]}] ; Esc+R
[:spacebar {:key :l :modi [:left_control :left_option :left_shift]}]]} ; Esc+Space
The keeper: one agent babysits the rest
"Have pi keep other panes alive" is two mechanisms. Herdr keeps the panes alive structurally โ the server outlives every window. Pi keeps the agents in those panes alive operationally: because herdr injects the socket path and pane id into every pane, a pi session can supervise its siblings with ordinary shell commands โ read what a sibling printed, answer its stuck confirmation prompt, restart its crashed command, and block on herdr wait agent-status instead of burning tokens polling. That is the keeper prompt above, and its two hard rules โ never close panes, never start new work โ exist because a shepherd with worker instincts destroys the flock.
This is not hypothetical self-inspection. On July 16, 2026, a pi session used pane capture to check glyph rendering in its own herdr pane โ and in doing so surfaced a real bug in herdr pane run. The success check above is that same move, packaged.
The signal the keeper is working: interventions get rarer over a session. A keeper that intervenes constantly is masking a bad task split โ fix the plan, not the babysitter.
Swarms: plan until independent, then fan out
The agenda bullet carries its own warning label: "lots of planning with a smart model first!" The swarm is the cheap part; the plan is the whole game. Run the decomposition prompt above with your strongest model, and argue with the output โ if two workers would touch the same file, you are not done planning. Then fan out each brief into a visible pane as a direct process:
herdr agent start learners --cwd ~/dev/proj/sites/learners --split right \
-- bash -lc 'pi -p "$(cat briefs/learners.md)"'
The argv launch matters: no shell, no typed command, no startup race โ "the launch race cannot happen, by construction" (the pi-herdr-subagents README, a herdr-native descendant of HazAT's pi-interactive-subagents). Death is observable too: herdr emits pane.exited socket events within milliseconds, so a dead worker is an event, not a screen that stopped changing. Captured from the running server the day before the workshop:
workspace "pushing-boundaries" โ herdr pane list, 2026-07-16 (abridged)
wS:p1 pi (orchestrator) ~/dev/pushing-boundaries
wS:pE kimi learners ~/โฆ/sites/learners
wS:pD kimi execs ~/โฆ/sites/execs
wS:pC kimi designers ~/โฆ/sites/designers
One pi orchestrator, three workers, each confined to its own directory โ exactly the shape the planning prompt demands. Every worker is watchable (glance at its pane), interruptible (click in and type), and composable with the keeper: one pane's pi can babysit the whole swarm.