stuck-process-detection

Stuck-process detection monitors background Bash calls with enforced timeouts and max polling attempts. When 3 consecutive empty responses occur or timeout is reached, it triggers recovery via KillShell, preventing infinite loops in test suites, builds, and dev servers.

Configure max poll limits and explicit timeout constraints on background process monitors. The detector enforces these boundaries and automatically recovers stuck pipelines, stopping endless waiting and enabling safe retry logic.

Yes. The detector integrates with run_in_background setups, applying foreground-first operation with timeout and max polling controls to catch stuck shells and trigger KillShell recovery before hangs cascade.

KillShell provides automatic termination and safe recovery steps when stuck-process detection triggers. It cleans up hung processes and enables retry decisions without manual intervention or pipeline deadlock.

After 3 consecutive empty BashOutput responses, stuck-process detection flags the pipeline and initiates KillShell recovery. Timeouts and max poll limits ensure detection occurs before monitoring loops consume indefinite resources.

Configure explicit timeout limits and max poll attempt counts when launching background processes. The detector enforces these constraints you define, stopping and recovering when either boundary is hit.