A command backgrounded to let your mid-run message through now says it's still running.
What's wrong with this entry?
When 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.
- Driven by a distinct internal state for message-triggered backgrounding, separate from timeout and explicit backgrounding.
- The message includes the background task ID so the task can still be followed.
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.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.223
Bash
[[ ]]conditionals: two new bail-outs for shell-lexer divergenceBoth mention bash
-
v2.1.246
Shell function snapshots no longer round-trip through base64
Both mention bash
-
v2.1.246
Shell snapshot records shell options before functions
Both mention bash