Tool roles, alternatives, selection tradeoffs, and compatibility caveats.
Terminal emulators
John uses: Ghostty (58.3k, MIT) — fast, GPU-accelerated, platform-native. In the stack it's deliberately just the pixel layer; Karabiner scopes its Esc-hold chord layer to the Ghostty app, and Herdr runs inside it.
| Alternative | What it is | How it differs | License |
|---|---|---|---|
| WezTerm | GPU-accelerated cross-platform terminal emulator AND multiplexer in Rust, Lua-configurable | Built-in multiplexing could replace part of the herdr layer too; deep Lua scripting | NOASSERTION (MIT per repo) |
| kitty | Fast, feature-rich GPU-based terminal with 'kittens' extensions and remote control protocol | Scriptable remote-control protocol (kitty @) is a viable pane-automation substrate | GPL-3.0 |
| Alacritty | Minimal, very fast OpenGL terminal emulator | No tabs/splits by design — pair with tmux/zellij/herdr | Apache-2.0 |
| iTerm2 | The long-standing macOS power-user terminal (Python scripting API, triggers, tmux integration) | macOS-only; slower rendering than the GPU generation but deepest macOS integration | GPL-2.0 |
Pick this if…
- WezTerm — you want emulator + multiplexer in one binary (can absorb part of the herdr layer).
- kitty — you want a scriptable terminal (
kitty @remote control is a pane-automation substrate). - Alacritty — you want maximum speed and will pair it with tmux/zellij/herdr anyway.
- iTerm2 — you want the deepest macOS integration and don't care about raw render speed.