const DEFAULT_IDLE_KILL_TIMEOUT: Duration;Expand description
If a wrapped command’s PTY produces zero bytes of output for this long,
assume it’s blocked waiting for interactive input that will never come
(e.g. less/more invoked as a pager, since the PTY deliberately makes
the child see isatty(stdout) == true and this wrapper never writes to
the PTY again after the startup DSR response) and forcibly kill it
rather than leak this whole process forever. See
docs/retro/RETRO_BASHWRAP_PAGER_HANG_LEAK_2026_07_14.md.
This is an IDLE timeout, not a total-runtime timeout: a command that’s
silent for under this long but runs far longer overall (e.g. a build
with continuous compiler output over several minutes) is unaffected —
only a command producing literally zero bytes for the full window trips
it. Overridable via AGENTMUX_BASHWRAP_IDLE_TIMEOUT_SECS.