{"version":"2.1.304","anchor":"new-background-command-warning-text-for-replies-that-end","canonical_anchor":"new-background-command-warning-text-for-replies-that-end","heading":"Claude is warned that background commands may stop after a reply ends","tier":"internal","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/new-background-command-warning-text-for-replies-that-end","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Claude is warned that background commands may stop after a reply ends\n\nA new instruction tells Claude that background commands are likely stopped minutes after a reply ends, so it should run important ones in the foreground\n\n**Unclear.** When this instruction is given to Claude is not known.\n\n**What**\n\nA background command is one Claude starts and leaves running while it carries on. A new instruction tells Claude that once its reply ends, it may not be told when such a command finishes, and that a few minutes later the command is likely stopped along with every other process left running. Claude is told to:\n\n- run commands that must finish in the foreground with a long enough time limit\n\n- otherwise tell you the command will likely be stopped\n\n**Why**\n\nThis changes how Claude handles long-running commands, so you are less likely to assume a background job finished when it was cut off.\n\n- Area: Background Tasks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}