{"version":"2.1.322","anchor":"background-exit-handoff-predicate-now-depends-on-an-adopt-ki","canonical_anchor":"background-exit-handoff-predicate-now-depends-on-an-adopt-ki","heading":"Either of two variables turns off handing over background work on exit","tier":"use","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.322\/e\/background-exit-handoff-predicate-now-depends-on-an-adopt-ki","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.322","markdown":"### Either of two variables turns off handing over background work on exit\n\nBackground exit handoff stays on unless `CLAUDE_CODE_DISABLE_BG_EXIT_HANDOFF` or `CLAUDE_DISABLE_ADOPT` is set\n\n**What**\n\nWhen a background session's process stops, restarts or updates, Claude Code can hand that session's unfinished work, such as running shell commands, over to the next process. This handoff stays on unless one of these environment variables is set:\n\n- `CLAUDE_CODE_DISABLE_BG_EXIT_HANDOFF`, which turns off only this handoff\n\n- `CLAUDE_DISABLE_ADOPT`, which turns off handoff more broadly\n\n**Why**\n\nIf you want background work to stop rather than carry over when a session's process exits, either variable does it.\n\n- Area: Sessions\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}