{"version":"2.1.311","anchor":"auto-resume-of-background-agents-after-container-restart","canonical_anchor":"auto-resume-of-background-agents-after-container-restart","heading":"Background agents can resume automatically after a container restart","tier":"notice","area":"Background Agents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/auto-resume-of-background-agents-after-container-restart","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Background agents can resume automatically after a container restart\n\nAfter a container restart, background agents that resume automatically are reported as resuming and reporting back instead of all being reported as lost\n\n**Unclear.** Whether automatic resuming is switched on for every remote session is not stated.\n\n**What**\n\nA background agent is a separate helper that Claude Code runs to work on a task while the main conversation carries on. Remote and cloud sessions run inside a container, an isolated environment on another machine, and that container can restart. Before, the notice after a restart said all background agents were lost and their work had to be started again. Now, agents that are resumed automatically are reported as \"being resumed automatically and will report back\".\n\nThe restart notice also records that the agents were started by the restart.\n\n**Why**\n\nRemote and cloud sessions can recover background work after a restart instead of dropping it, so you may not need to start those tasks again.\n\n- Area: Background Agents\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}