Orphaned background tasks after a cloud restart are deduplicated before you get the notice.
What's wrong with this entry?
After a cloud worker restart, the lists of running tasks and tasks awaiting notification are merged through one shared deduplication helper instead of hand-written map merging, and if a task was still running an extra wait happens before the orphaned-task notice is shown. The component that restores MCP tasks is now also given the app-state setter, so restored tasks can write back into app state.
- On the
CLAUDE_CODE_RESUME_INTERRUPTED_TURNpath.
orphaned_background_tasks_pending_notification
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