{"version":"2.1.296","anchor":"background-attach-reconnect-honours-onlytoretry","canonical_anchor":"background-attach-reconnect-honours-onlytoretry","heading":"Reconnecting to a background session can skip the \"stalled\" error","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/background-attach-reconnect-honours-onlytoretry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Reconnecting to a background session can skip the \"stalled\" error\n\nWhen reconnecting to a background session in retry-only mode, Claude Code now skips the \"stalled\" error\n\n**Unclear.** It is not clear when Claude Code reconnects in retry-only mode, so it is not clear when you would stop seeing the stalled error.\n\n**What**\n\nClaude Code keeps trying to reconnect to a background session, meaning one that runs while you do something else. Each attempt can now carry an extra option. When the option says the attempt is only a retry, Claude Code skips the \"stalled\" error it would otherwise report.\n\n**Why**\n\nThis changes how reconnecting to a background session behaves when the connection is slow to come back.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}