{"version":"2.1.311","anchor":"stopped-turn-now-stops-moved-shells","canonical_anchor":"stopped-turn-now-stops-moved-shells","heading":"Stopping a turn now also stops shells moved to the background","tier":"notice","area":"Bash","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/stopped-turn-now-stops-moved-shells","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Stopping a turn now also stops shells moved to the background\n\nWhen you stop a turn, Claude Code now also stops the shells that had been moved off that turn\n\n**Unclear.** Exactly which background shells count as moved, and are therefore stopped, is not clear.\n\n**What**\n\nA turn is one round of Claude working on your request. When you stop a turn yourself, Claude Code now also stops shells that had been moved off the turn, meaning shell commands that were sent to keep running in the background. Before, ending the turn did not stop them. The record that you stopped the turn is cleared when the turn ends.\n\n**Why**\n\nBackground commands started during a turn may now be ended when you interrupt it, so a long-running command you wanted to keep going may stop.\n\n- Area: Bash\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}