phux

Drive persistent, interactive terminal sessions via the phux CLI instead of one-off shells. Use when work needs session state across steps (a long-lived shell, a REPL, an activated venv, a running dev server), an interactive/TUI program (installer prompts, gdb, vim, ssh password), or watching a long-running process — i.e. anything a stateless one-shot `bash` call handles badly.

Wrap the phux CLI as a programmable terminal-control surface for an agent — enumerate sessions, read panes, send input, and run commands using the stable --json contracts and exit-code mirroring. Use when you are scripting phux from another program/agent and need machine-parseable I/O and a read+act+wait loop, rather than the prose "when to use phux" guidance.