Claude is told background command results come back on their own, so it stops polling.
What's wrong with this entry?
New instructions tell the model that a backgrounded command's result comes back on its own, "between your tool calls if you are still working, or by starting a new turn if you have already replied", with variants for when the turn ends and when the session ends. It is told to wait using one blocking foreground command rather than repeated status checks.
- A new task status shape covers working, completed, failed and cancelled, with a task id, status message, creation time and last update time.
- Exited commands convert to completed or cancelled status with output truncated behind an
[… earlier output omitted; full output: ...]header.
between your tool calls if you are still working, or by starting a new turn if you have already replied
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
Background task notifications arrive inside a system-reminder
Both mention background task
-
v2.1.235
Several finished background tasks now report as one line
Both mention background task
-
v2.1.236
Background-task notices no longer look like user approval
Both mention background task