{"version":"2.1.315","anchor":"background-task-kill-on-exit-option-and-text-rhythm-telemetr","canonical_anchor":"background-task-kill-on-exit-option-and-text-rhythm-telemetr","heading":"Commands moved to the background are now marked to be stopped when Claude Code exits","tier":"notice","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/background-task-kill-on-exit-option-and-text-rhythm-telemetr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Commands moved to the background are now marked to be stopped when Claude Code exits\n\nShell commands moved to the background are now marked to be killed when Claude Code exits, and text output timing is now measured\n\n**Unclear.** Whether background commands were already stopped at exit before this release is not stated.\n\n**What**\n\nWhen a shell command is moved to the background, it now carries a setting that says it should be killed when Claude Code exits. The alternative for this setting is to leave it running. A background command is one that keeps running while you go on working with Claude Code.\n\nSeparately, Claude Code's usage reporting now measures the rhythm of text output:\n\n- How many times text was posted\n\n- How many gaps between posts were longer than half a second\n\n- How late, at most, the timer that sends out text ran\n\n**Why**\n\nA command you moved to the background may now be stopped when you leave Claude Code instead of being left running. If you rely on a long-running background command, check whether it is still running after Claude Code exits.\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}