{"version":"2.1.292","anchor":"stopped-main-thread-agents-can-be-resumed-after-worker-resta","canonical_anchor":"stopped-main-thread-agents-can-be-resumed-after-worker-resta","heading":"After a restart, Claude is told which stopped agents it can resume","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/stopped-main-thread-agents-can-be-resumed-after-worker-resta","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### After a restart, Claude is told which stopped agents it can resume\n\nThe notice shown to Claude after a worker restart now lists stopped agents it can resume by messaging their id\n\n**What**\n\nWhen a remote session restarts, Claude Code tells the model about background tasks that were left behind. That notice now also lists built-in agents (helper instances of Claude that work on a task alongside the main conversation) that were stopped and can be resumed. It tells the model to send a message to the agent's id so the agent continues from its saved transcript, the record of what it had done so far.\n\n- The resume list is only added when the tool for messaging agents is available.\n\n- It applies when `CLAUDE_CODE_RESUME_INTERRUPTED_TURN` is set.\n\n- On Linux remote connections, Claude Code also keeps track of programs left running.\n\nBefore, the notice only listed the leftover tasks and gave no guidance on resuming them.\n\n**Why**\n\nA restarted remote session can pick up an agent where it stopped instead of starting a fresh one and redoing its work.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}