{"version":"2.1.227","anchor":"clearer-wording-when-a-command-moves-to-the-background","canonical_anchor":"clearer-wording-when-a-command-moves-to-the-background","heading":"Clearer wording when a command moves to the background","tier":"notice","area":"Bash Tool","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/clearer-wording-when-a-command-moves-to-the-background","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Clearer wording when a command moves to the background\n\nBackgrounded Bash commands now explain why they moved to the background and whether they'll be killed.\n\n**What**\n\nThe message you get when a Bash command is backgrounded is now built in one place, with different wording depending on whether you asked for it, whether it hit the timeout, or whether it will be killed when Claude finishes its reply.\n\n**Details**\n\n- The last case warns explicitly that the process is terminated at the final response, so no completion notice can arrive after that.\n\n**Evidence**\n\n`If it exits while you are still working you will be notified, but it is terminated when you give your final response and no notification can follow that`\n\n- Area: Bash Tool\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}