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):
CLAUDE_CODE_DISABLE_PROACTIVITY: turns the proactivity selector off.--proactivitythen has no effect: no proactivity note is sent, the level does not choose the permission mode, and--proactivity askfalls back to manual mode with a notice.CLAUDE_CODE_RELAUNCH_PROACTIVITY_BASELINE,CLAUDE_CODE_RELAUNCH_PROACTIVITY_LEVEL,CLAUDE_CODE_RELAUNCH_PROACTIVITY_DECIDEDandCLAUDE_CODE_RELAUNCH_PROACTIVITY_EVER_ON: these hand the proactivity baseline, level and related state to Claude Code when it restarts itself.
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.
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.
Fixed background workers honoring --allow-dangerously-skip-permissions on respawn without the bypass-permissions disclaimer having been…
New in this build: CLAUDE_CODE_RELAUNCH_PROACTIVITY_BASELINE