{"version":"2.1.312","anchor":"agent-tool-cut-off-agent-calls-after-container-restart-are","canonical_anchor":"agent-tool-cut-off-agent-calls-after-container-restart-are","heading":"Agent calls cut off by a container restart now resume or report clearly","tier":"notice","area":"Subagents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/agent-tool-cut-off-agent-calls-after-container-restart-are","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Agent calls cut off by a container restart now resume or report clearly\n\nIf a container restarts mid-turn, Claude Code resumes interrupted agent calls or tells Claude plainly why it cannot\n\n**What**\n\nClaude Code can start agents, separate helpers that work on part of a task. When Claude Code runs inside a container (an isolated environment) and that container restarts in the middle of a turn, agent calls left waiting are now handled:\n\n- A call that can be resumed is restarted from its saved transcript, and Claude is told to wait for notifications.\n\n- A call that cannot be resumed fails with an error saying the agent stopped when the container restarted and that nothing new was launched.\n\n- A resumed agent that then fails gets a note that it was cut off, along with a recovered report.\n\n- An agent that had already finished but lost its report is told apart from one that ended with no report.\n\nA permission question an agent was waiting on can also be held and picked up again.\n\n**Why**\n\nAfter a restart, Claude gets clear instructions instead of a silent failure or a second copy of the same agent being launched.\n\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}