{"version":"2.1.301","anchor":"background-shell-kill-output-file-handling-changes-new-aut","canonical_anchor":"background-shell-kill-output-file-handling-changes-new-aut","heading":"Stopped background commands point to their real output file","tier":"notice","area":"Background Shells","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/background-shell-kill-output-file-handling-changes-new-aut","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Stopped background commands point to their real output file\n\nStopping a background command whose output is saved elsewhere no longer adds \"[killed]\", and the notice points to that file\n\n**Unclear.** It is not clear what the new auto mode skip reason applies to.\n\n**What**\n\nA background shell is a command Claude Code runs while you keep working. When one is stopped and its output is saved somewhere other than the usual place, Claude Code no longer adds \"[killed]\" to that output, and the notice that it stopped points to where the output really is. Before, it always added \"[killed]\" and pointed to the usual place.\n\nClaude Code also gains a new reason for skipping something in auto mode, related to background commands running under a rule, and now keeps track of background shells that were kept.\n\n**Why**\n\nThe stop notice sends you to the right file for a command's output.\n\n- Area: Background Shells\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}