{"version":"2.1.314","anchor":"bash-stall-detection-replaced-by-shared-helper","canonical_anchor":"bash-stall-detection-replaced-by-shared-helper","heading":"Stuck background shell commands are detected in a new way","tier":"notice","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/bash-stall-detection-replaced-by-shared-helper","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Stuck background shell commands are detected in a new way\n\nClaude Code now uses a shared watcher to notice background shell commands that are waiting for input, in place of a separate check per command\n\n**What**\n\nA background shell command is a command Claude starts that keeps running while the conversation continues. Sometimes such a command stops and waits for someone to type an answer. Before, Claude Code checked each of these commands on a timer, watching whether its output kept growing and looking for a prompt asking for input. It then reported that the command appeared to be waiting for interactive input.\n\nThat per-command check is gone. A shared watcher now raises the same notice, and its message is built in a different way.\n\n**Why**\n\nThis may change when you are told that a background command is stuck.\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}