{"version":"2.1.311","anchor":"background-session-respawn-can-settle-from-on-disk-row-stal","canonical_anchor":"background-session-respawn-can-settle-from-on-disk-row-stal","heading":"Restarted background sessions no longer always resume the interrupted turn","tier":"notice","area":"Background Agents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/background-session-respawn-can-settle-from-on-disk-row-stal","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Restarted background sessions no longer always resume the interrupted turn\n\nWhen a background session restarts and has no transcript to resume, Claude Code now drops the setting that resumes an interrupted turn\n\n**What**\n\nA background session is one Claude Code runs without you watching it. When one restarts after stopping, Claude Code can now use a record of the session it already has loaded, rather than reading it again, and treat the session as finished with no transcript (the saved record of the conversation). In that case it removes `CLAUDE_CODE_RESUME_INTERRUPTED_TURN` from the restarted process's environment. Before, it always reread the record and could set that variable.\n\n**Why**\n\nThis changes how background agents recover after a crash. A session with nothing to resume is no longer told to pick up an interrupted turn.\n\n- Area: Background Agents\n- Names: `CLAUDE_CODE_RESUME_INTERRUPTED_TURN`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}