{"version":"2.1.311","anchor":"background-session-attach-stall-respawn-gets-telemetry-plus","canonical_anchor":"background-session-attach-stall-respawn-gets-telemetry-plus","heading":"Stalled background sessions are now reported before they restart","tier":"notice","area":"Background Agents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/background-session-attach-stall-respawn-gets-telemetry-plus","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Stalled background sessions are now reported before they restart\n\nBefore restarting a stalled background session, Claude Code now looks up its saved state and reports why it is restarting\n\n**What**\n\nA background session is a Claude Code session that keeps running without a terminal window attached to it. When reconnecting to one stalls, or uses an older way of reconnecting, Claude Code restarts it. Before doing so, it now:\n\n- looks up the session's saved state if no live record of it is found\n\n- reports whether the restart is because of a stall or the older reconnect method\n\nThere is also a new check for whether a session has messages that can be resumed, used with Remote Control.\n\n**Why**\n\nIt gives better insight into why background sessions stall and get restarted.\n\n- Area: Background Agents\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}