{"version":"2.1.301","anchor":"background-shell-exit-marker-replaced-by-a-structured-call","canonical_anchor":"background-shell-exit-marker-replaced-by-a-structured-call","heading":"End-of-run note for background shell commands is written a different way","tier":"notice","area":"Background Shells","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/background-shell-exit-marker-replaced-by-a-structured-call","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### End-of-run note for background shell commands is written a different way\n\nWhen a background shell command ends, Claude Code no longer writes the plain [killed] or [exited with code N] line itself\n\n**Unclear.** What the new end-of-run note looks like is not stated.\n\n**What**\n\nWhen a shell command running in the background finishes, Claude Code adds a note to its output. It used to write a plain line saying `[killed]` or `[exited with code N]`. It now passes whether the command was killed, or its exit code, to a separate step that records the ending, so the note may look different.\n\n**Why**\n\nThis changes how the end of a background command shows up in its output.\n\n- Area: Background Shells\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}