{"version":"2.1.274","anchor":"orphaned-background-task-recovery-on-resume-now-restricted-t","canonical_anchor":"orphaned-background-task-recovery-on-resume-now-restricted-t","heading":"Orphaned background-task recovery on resume now restricted to remote transport","tier":"notice","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/orphaned-background-task-recovery-on-resume-now-restricted-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Orphaned background-task recovery on resume now restricted to remote transport\n\nRecovering interrupted background tasks on restart now requires a remote session\n\n**Unclear.** The finding doesn't say why recovery is now restricted to remote sessions specifically, only that the condition was added.\n\n**What**\n\nOn startup, Claude Code can recover background tasks that were still running when a previous session was interrupted, controlled by the `CLAUDE_CODE_RESUME_INTERRUPTED_TURN` setting. This recovery now also requires that the session is using remote transport, meaning it won't attempt this recovery for local sessions.\n\n**Why**\n\nThis narrows automatic recovery of interrupted background work to remote sessions, presumably because that's where recovering an orphaned task makes sense; local sessions no longer attempt it.\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}