Quick start
Install hooks first so sessions publish lifecycle metadata, then inspect HUD-backed rows from the same socket state.
forktty hooks setup --dry-runforktty agents --workspace-name main --jsonforktty agent-health --workspace-name main --jsonforktty wait agent-status --status needs_input --timeout-ms 30000Lifecycle without scrollback archaeology
Managed hooks publish provider-neutral status rows for supported agents. ForkTTY groups rows into scan-friendly states such as Working, Needs input, Done, and Idle while keeping diagnostic source and age metadata visible.
Actionable controls
HUD actions can focus a pane, resume a ready persisted session, or forget stale state. The UI highlights current panes and risky permission modes instead of burying them in terminal text.
Loop and team context
When a visible agent surface is bound to workflow loop state, compact chips show iteration and gate status. Team summaries and final states help leaders decide whether a worker is still active, stale, closed, or waiting.
Questions
Which agents appear in the Agent HUD?
Is HUD status proof that an agent is live right now?
Can the HUD resume sessions?
Explore related ForkTTY pages
Get the alpha build
AppImage and .deb packages are published on GitHub Releases for Linux x86_64.
View releases