Repository navigation
hush: bare TUI exits 1 with cryptic crossterm error when no TTY is present #57
Description
Activity
Fixed by merged PR #58 at main commit
0fd0ef1f23840b7278417bbe29adcbb5fca49a05. With a synthetic bws fixture, a fully headless invocation exits 1 with the no-TTY explanation and list/get/exec guidance, with empty stdout. A real PTY starts and exits cleanly with alternate-screen restoration. Fresh Rust tests (19), full repository checks, packaging, extension startup, independent exact-head review, and remote CI passed. CHANGELOG.md records the behavior.
Running bare
hush(interactive TUI) from a non-interactive context (agent harness, script, pipe) fails with:exit code 1. The message gives no hint about why or what to use instead.
hush list,hush get, andhush execall work fine in the same context, so this is only the TUI entry path.Fix: gate
tui::run()on TTY availability up front and return an actionable error pointing at the script-friendly subcommands.