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 ·

New variables to turn off proactivity and carry it across a relaunch

Claude Code adds CLAUDE_CODE_DISABLE_PROACTIVITY and variables that pass proactivity state to a relaunched Claude Code

Use it now Notable No documentation found New Features
JSON All of v2.1.290
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
ProactivityArea: what it touches
New FeaturesKind: in v2.1.290,
What probably matters to youSection of the release
What

Claude Code has new environment variables (settings you pass to a program through the shell) related to proactivity, the level that sets how much Claude does on its own (the --proactivity startup entry has the detail):

When Claude Code starts, the part that picks the starting permission mode reads these relaunch variables and then clears them. If the handed-over baseline is bypassPermissions, the mode that skips permission prompts, it is dropped unless you passed --dangerously-skip-permissions or --allow-dangerously-skip-permissions. CLAUDE_CODE_DISABLE_ATTACHMENTS was added to the same list of handled variables.

Why

There is now a way to turn proactivity off, and a restart cannot carry you into bypass mode unless you asked for it on the command line.

Read from
What has happened since
Corrected by hand The operator corrected this entry by hand after it was published.

See this across every release →

How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's release notes agreeFixed background workers honoring --allow-dangerously-skip-permissions on respawn without the bypass-permissions disclaimer having been…
The name it cites is new in this buildNew in this build: CLAUDE_CODE_RELAUNCH_PROACTIVITY_BASELINE

See this entry in the whole of v2.1.290 →

Feedback