Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.290 ·

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 Improvements
JSON All of v2.1.290
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Chrome & BrowserArea: what it touches
ImprovementsKind: in v2.1.290,
ImprovementsSection 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 disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat triggers the clearing of these variables, and what sets them in the first place, is not settled.
Anthropic's release notes agreeFixed 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 →

Feedback