{"version":"2.1.281","anchor":"finished-background-tasks-are-mirrored-so-a-restart-can-repo","canonical_anchor":"finished-background-tasks-are-mirrored-so-a-restart-can-repo","heading":"Finished background tasks are mirrored so a restart can report them (remote transport only)","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/finished-background-tasks-are-mirrored-so-a-restart-can-repo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Finished background tasks are mirrored so a restart can report them (remote transport only)\n\nOver a remote connection, finished background tasks are now recorded so they can be reported after a restart\n\n**What**\n\nWhen Claude Code runs over a remote connection, it now saves completion notices for finished background tasks that have not been delivered yet, up to 32 of them. It stores them as `finished_background_tasks_pending_notification` in the worker's metadata. After a restart, it reads that entry, adds a message about those tasks to the conversation, and clears the entry. On a local connection this does nothing.\n\n**Why**\n\nA restart no longer loses news of background tasks that finished just before it."}