Chrome tabs a session opened are closed when you leave it, unless they hold real content.
tengu_chrome_tab_group_close Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.239: off
Read once, for one account on one subscription tier, against v2.1.239. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
When you switch away from a session or exit, Claude Code now asks the browser bridge for that session's tab group and closes its tabs. It keeps the group if any tab has real content, if the tab list cannot be read, or if the group holds more tabs than a cap. This is on by default (tengu_chrome_tab_group_close, fallback true) and skipped entirely in remote sessions.
- A tab counts as content unless it is a new tab or a blank page; one such tab keeps the whole group open.
- Telemetry event
chrome_tab_group_closerecords the outcomesover_cap,tabs_unreadableandclose_failed. - Skipped when the environment variable
CLAUDE_CODE_REMOTE_SESSION_IDis set.
tengu_chrome_tab_group_close
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.242
Shape rules for Claude in Chrome batched actions, off without server config
Both mention browser
-
v2.1.242
Browser navigation is given to the safety judge as ground truth
Both mention browser
-
v2.1.242
Browser tools reached over a remote device get the same handling as local ones
Both mention browser