Backgrounded Bash commands now explain why they moved to the background and whether they'll be killed.
What's wrong with this entry?
The 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.
- The last case warns explicitly that the process is terminated at the final response, so no completion notice can arrive after that.
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
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.234
Every session now gets the
cdpermission warning in the Bash toolBoth mention bash tool
-
v2.1.234
Command lessons are recorded with the command that produced them
Both mention bash tool
-
v2.1.238
Directory tracking for backgrounded commands no longer breaks early
Both mention bash tool