{"version":"2.1.286","anchor":"chrome-tab-group-key-passed-only-for-remote-sessions-and-the","canonical_anchor":"chrome-tab-group-key-passed-only-for-remote-sessions-and-the","heading":"CLAUDE_CHROME_TAB_GROUP_KEY is used only in remote sessions and then cleared","tier":"internal","area":"Chrome","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/chrome-tab-group-key-passed-only-for-remote-sessions-and-the","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### `CLAUDE_CHROME_TAB_GROUP_KEY` is used only in remote sessions and then cleared\n\nClaude Code now keeps `CLAUDE_CHROME_TAB_GROUP_KEY` only in remote sessions and removes it so programs it starts do not inherit it\n\n**What**\n\nAt startup, Claude Code now records `CLAUDE_CHROME_TAB_GROUP_KEY` only when `CLAUDE_CODE_REMOTE_SESSION_ID` is set, which marks a remote session. It then removes `CLAUDE_CHROME_TAB_GROUP_KEY` from its environment, the set of settings a program passes to the programs it starts. Commands and tools that Claude Code launches no longer receive it.\n\n**Why**\n\nGrouping Chrome tabs by this key now applies only to remote sessions, and the key no longer leaks into every program Claude Code runs.\n\n- Area: Chrome\n- Names: `CLAUDE_CHROME_TAB_GROUP_KEY`, `CLAUDE_CODE_REMOTE_SESSION_ID`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}