{"version":"2.1.295","anchor":"claude-code-disable-bg-stable-path-opts-out-of-the-stable-ex","canonical_anchor":"claude-code-disable-bg-stable-path-opts-out-of-the-stable-ex","heading":"New setting to stop background sessions on macOS using the stable program path","tier":"use","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/claude-code-disable-bg-stable-path-opts-out-of-the-stable-ex","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### New setting to stop background sessions on macOS using the stable program path\n\nOn macOS, setting CLAUDE_CODE_DISABLE_BG_STABLE_PATH makes background sessions relaunch from the running program instead of the stable path\n\n**What**\n\nOn macOS, Claude Code sometimes relaunches itself when it starts a background session, which is a session that keeps running without you watching it. This relaunch is tied to macOS privacy permissions. Before, it always used a fixed, stable location for the Claude Code program when one was available.\n\nIt now uses the program that is currently running instead when either of these environment variables is set (an environment variable is a setting you give a program from your shell before starting it):\n\n- `CLAUDE_CODE_DISABLE_BG_STABLE_PATH`, set to any value\n\n- `CLAUDE_PTY_HOST_NO_STABLE_PATH`, set to `1`\n\nThe relaunched program does not inherit `CLAUDE_PTY_HOST_NO_STABLE_PATH`.\n\n**Why**\n\nIf background sessions fail to start because of the stable program location, these settings give you a way around it.\n\n- Area: Sessions\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}