{"version":"2.1.248","anchor":"background-isolation-read-from-a-captured-environment","canonical_anchor":"background-isolation-read-from-a-captured-environment","heading":"Background isolation read from a captured environment","tier":"use","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/background-isolation-read-from-a-captured-environment","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Background isolation read from a captured environment\n\nBackground worktree isolation now reads CLAUDE_BG_ISOLATION from a captured environment copy.\n\n**What**\n\nThe setting that decides whether background work runs in a separate worktree now reads `CLAUDE_BG_ISOLATION` from a captured copy of the environment rather than live process state. It still accepts `worktree` or `none` and otherwise falls back to the `bgIsolation` config value. A new comment documents how terminal recordings are addressed within a session folder.\n\n**Evidence**\n\n`keys.recording(projectKey, sessionId, stamp)`\n\n- Area: Background Tasks\n- Names: `CLAUDE_BG_ISOLATION`, `bgIsolation`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}