Follow Discord
Sweep 01 Oct 2026 · 17:27Z Build v2.1.287 508 read Stable v2.1.285 Latest v2.1.287 Next v2.1.287 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.286entry #206

Claude Code v2.1.286 ·

CLAUDE_CHROME_TAB_GROUP_KEY is used only in remote sessions and then cleared

Claude Code now keeps CLAUDE_CHROME_TAB_GROUP_KEY only in remote sessions and removes it so programs it starts do not inherit it

Under the hood Internal Changes
JSON All of v2.1.286
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ChromeArea: what it touches
Internal ChangesKind: in v2.1.286,
Internal ChangesSection of the release
What

At 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.

Why

Grouping Chrome tabs by this key now applies only to remote sessions, and the key no longer leaks into every program Claude Code runs.

Read from
Names in the bundleCLAUDE_CHROME_TAB_GROUP_KEYCLAUDE_CODE_REMOTE_SESSION_ID
What the documentation says
Documented inclaude-code/cloud-environments
How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: CLAUDE_CHROME_TAB_GROUP_KEY

See this entry in the whole of v2.1.286 →

Feedback