{"version":"2.1.311","anchor":"restarted-container-notice-says-background-agents-are-resume","canonical_anchor":"restarted-container-notice-says-background-agents-are-resume","heading":"After a container restart, Claude can be told its agents resume on their own","tier":"notice","area":"Background Agents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/restarted-container-notice-says-background-agents-are-resume","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### After a container restart, Claude can be told its agents resume on their own\n\nA new restart notice tells Claude its background agents are resuming from saved transcripts, so it should not launch them again\n\n**Unclear.** When Claude Code sends the new notice rather than the old one is not stated.\n\n**What**\n\nA container is the isolated environment a session runs in. After a container restarts, Claude Code sends Claude a notice about the background agents it had running. Background agents are helper agents doing work alongside the main conversation.\n\nThere is now a second version of that notice. It tells Claude that each agent \"is being resumed automatically from its saved transcript\", so it does not need to launch them again. The earlier notice is kept. It says each agent is stopped and its result never arrived.\n\n**Why**\n\nWhen the new notice is used, Claude stops relaunching agents that are already being resumed after a restart.\n\n- Area: Background Agents\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}