Claude Code v2.1.290 · 5 Oct 2026
Chrome permission and unattended-tools variables get safe defaults and are kept from child processes
Claude Code now knows safe values for three Chrome variables, can clear them, and keeps a new unattended-tools variable out of child processes
You'll notice Tier: how much it should matter to you
2 Useful: my rating, 1 to 5
3 Signal: worth watching, 1 to 5
Chrome & Browser Area: what it touches
Improvements Kind: in v2.1.290, 05 Oct 26
Improvements Section of the release
Unclear What triggers the clearing of these variables, and what sets them in the first place, is not settled.
What
Claude Code now holds a safe value for three environment variables (settings you pass to a program through the shell) that control Claude in Chrome:
It can check whether each one is still at its safe value and can remove all three from its own environment. These three, along with CLAUDE_AFK_TIMEOUT_MS , CLAUDE_AFK_COUNTDOWN_MS and CLAUDE_CODE_USER_DIALOG_TIMEOUT_MS , were added to a list of variables Claude Code handles specially.
A new variable, CLAUDE_CODE_REMOTE_TOOLS_HOST_ALLOWS_UNATTENDED , is also on that list and is removed from the environment of child processes, the programs Claude Code starts. CLAUDE_CODE_REMOTE_HERMETIC_MODE now only counts when CLAUDE_CODE_REMOTE is also set.
Before a session is allowed to run tools on your computer, Claude Code now keeps a copy of the folder's settings. If it cannot, it stops with a message asking you to check disk space and ~/.claude/state.
Why
This looks like a lock-down of the Chrome and unattended permission settings, so that programs Claude Code starts cannot pick up relaxed values from the environment.
How sure we are
Something disagrees Something we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt What triggers the clearing of these variables, and what sets them in the first place, is not settled.
Anthropic's release notes agree Fixed CLAUDE_CODE_USER_DIALOG_TIMEOUT_MS=5m being read as 5 ms and cancelling remote dialogs at once; values with a unit suffix now fall…
See this entry in the whole of v2.1.290 →
5 Oct 2026 · 548 entries, this one is #93.
Use it now36 You'll notice386 Nothing to try yet8 Under the hood118
Open the release →
Names in this entry
env CLAUDE_CHROME_CLASSIFIER_FLOOR The terminal tab status toggle, Claude API tip and Chrome classifier default only moved; their gate fallbacks are unchanged
env CLAUDE_CHROME_PERMISSION_MODE Claude Code now knows safe values for three Chrome variables, can clear them, and keeps a new unattended-tools variable out of child processes
env CLAUDE_CODE_ENABLE_CFC Restricted sessions skip Claude in Chrome browser wiring, same as safe mode.
env CLAUDE_AFK_TIMEOUT_MS How many milliseconds of idle time before an unanswered AskUserQuestion dialog auto-continues without you. Auto-continue is off by default; opt in with the askUserQuestionTimeout setting. This variable is an override for demos and automated tests: when set, it takes precedence over that setting and turns auto-continue on even when the setting is unset or never. Setting 0 doesn't turn the timeout off; it closes the dialog immediately. In v2.1.198 and v2.1.199, auto-continue was on by default with a 60000 (60 seconds) timeout. Requires Claude Code v2.1.198 or later
env CLAUDE_AFK_COUNTDOWN_MS How many milliseconds before auto-continue the on-screen countdown appears on an unanswered AskUserQuestion dialog. Default 20000 (20 seconds), capped at the auto-continue timeout. Has no effect unless auto-continue is on; see the askUserQuestionTimeout setting and CLAUDE_AFK_TIMEOUT_MS. Requires Claude Code v2.1.198 or later
env CLAUDE_CODE_USER_DIALOG_TIMEOUT_MS Set dialogExpiry to control how long a forwarded permission prompt waits before resolving to its safe default.
env CLAUDE_CODE_REMOTE_TOOLS_HOST_ALLOWS_UNATTENDED Claude Code's lists of allowed usage events and host environment variables gain entries about MCP, skills and hosted setups
env CLAUDE_CODE_REMOTE_HERMETIC_MODE More environment variables get carried into remote sessions; none are set by default.
env CLAUDE_CODE_REMOTE Remote sessions started from review can skip writing some state to disk.
Anthropic's note
Upstream's own release notes for v2.1.290 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.
Is this right?
0
0
Feedback
What's wrong with this entry?
Hard to understand Too vague Looks wrong Not relevant to me Too long Missing the detail I wanted Duplicate of another card
Clear Learned something new I can act on this Good catch
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
← Previous · 92 of 548
New status messages when this window runs no local tools
You'll notice Remote Control
In v2.1.290 Improvements release-page order
Next → · 94 of 548
Remote tool calls can be refused for a further kind of path
You'll notice Remote Control