{"version":"2.1.290","anchor":"background-shell-kill-is-now-tracked","canonical_anchor":"background-shell-kill-is-now-tracked","heading":"Stopping a remotely served background command no longer waits for it to end","tier":"notice","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/background-shell-kill-is-now-tracked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Stopping a remotely served background command no longer waits for it to end\n\nA remotely served background command still counts as running while it is being stopped, and the stop result returns without waiting\n\n**Unclear.** What difference this makes to someone using Claude Code is not clear.\n\n**What**\n\nA background command is a shell command left running while Claude carries on. For background commands served remotely, one that is being stopped now still counts as running until it ends. The result of the stop request also comes back without waiting for the command to finish shutting down.\n\n**Why**\n\nThe count of running background commands is more accurate.\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"}