{"version":"2.1.292","anchor":"background-command-flag-now-covers-headless-sessions-that-ta","canonical_anchor":"background-command-flag-now-covers-headless-sessions-that-ta","heading":"Claude is told more clearly when a background command will not report back","tier":"notice","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/background-command-flag-now-covers-headless-sessions-that-ta","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Claude is told more clearly when a background command will not report back\n\nHeadless sessions that take no more input now mark background commands as ending with the final response, so no completion notice follows\n\n**What**\n\nClaude can start a command in the background and normally gets a notice when it finishes. Some background commands are stopped when the thing that started them gives its final response, so no notice can arrive.\n\nBefore, that case only covered commands started by a subagent (a helper Claude runs to do part of a task) that runs while the main conversation waits. Now it also covers a headless session (one run without an interactive terminal, such as from a script) that takes no more input and is not waiting for background commands.\n\nThe separate wording Claude used to see for that session case, \"This session takes no further input, though\", has been removed.\n\n**Why**\n\nIn headless runs, Claude is told plainly that a background command will not report back, so it does not expect a result that will never come.\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}