{"version":"2.1.251","anchor":"bash-tasks-pushed-to-the-background-for-an-incoming-message-","canonical_anchor":"bash-tasks-pushed-to-the-background-for-an-incoming-message-","heading":"Bash tasks pushed to the background for an incoming message say so","tier":"notice","area":"Bash","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/bash-tasks-pushed-to-the-background-for-an-incoming-message-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Bash tasks pushed to the background for an incoming message say so\n\nA command backgrounded to let your mid-run message through now says it's still running.\n\n**What**\n\nWhen a running foreground command is moved to the background specifically so a message you sent mid-run can reach Claude, the result now states that the command was not interrupted and is still running, instead of looking like a timeout or a manual backgrounding.\n\n**Details**\n\n- Driven by a distinct internal state for message-triggered backgrounding, separate from timeout and explicit backgrounding.\n- The message includes the background task ID so the task can still be followed.\n\n**Evidence**\n\n`Command was moved to the background (ID: ${e}) so that a message that arrived while it was running can reach you; it was not interrupted.`\n\n- Area: Bash\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}