{"version":"2.1.311","anchor":"recorded-background-agents-are-resumed-after-a-ccr-worker-re","canonical_anchor":"recorded-background-agents-are-resumed-after-a-ccr-worker-re","heading":"Background agents in remote sessions can resume after the worker restarts","tier":"notice","area":"Background Agents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/recorded-background-agents-are-resumed-after-a-ccr-worker-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Background agents in remote sessions can resume after the worker restarts\n\nRemote sessions can now resume background agents that were running or cut off when the remote worker restarted, within a set limit\n\n**Unclear.** It is not known what has to be switched on for this resume to happen.\n\n**What**\n\nA background agent, sometimes called a subagent, is a helper Claude starts to work on part of a task while the main conversation continues. In a remote session, the machine running the work can restart. Claude Code can now pick back up the background agents that were running, or were cut off, when that happened.\n\n- `restartResumes` sets how many of them can be resumed.\n\n- Each one is checked against the session's permission rules first.\n\n- An agent the rules now block, or one that needs approval, is not resumed. Claude Code shows a message saying the rules block it or that background agents are off.\n\n**Why**\n\nWork that background agents were doing in a remote session can carry on after a restart instead of being lost. Permission rules are checked again before anything resumes.\n\n- Area: Background Agents\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}