Claude Code v2.1.304 · 19 Oct 2026
A new environment variable, CLAUDE_CODE_PERSONAL_CONFIG_FIX , is read by Claude Code and passed on to tmux sessions and child processes
Use it now Notable
No documentation found New Features
Copy link
Copy markdown
JSON
All of v2.1.304
Use it now Tier: how much it should matter to you
4 Useful: my rating, 1 to 5
4 Signal: worth watching, 1 to 5
Configuration Area: what it touches
New Features Kind: in v2.1.304, 19 Oct 26
What probably matters to you Section of the release
Unclear What values CLAUDE_CODE_PERSONAL_CONFIG_FIX accepts and what it changes are not known.
What
Claude Code reads a new environment variable, CLAUDE_CODE_PERSONAL_CONFIG_FIX . An environment variable is a named value you set in your shell before starting a program. Claude Code passes it on to the tmux sessions it starts (tmux is a tool for running terminal sessions in the background) and to other programs it launches. It is handled in the same lists as CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG , which control which variables are passed on or removed.
Why
It looks like a new switch related to how personal configuration is restricted or repaired, and it now reaches every process Claude Code starts.
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 values `CLAUDE_CODE_PERSONAL_CONFIG_FIX` accepts and what it changes are not known.
The name it cites is new in this build New in this build: CLAUDE_CODE_PERSONAL_CONFIG_FIX
See this entry in the whole of v2.1.304 →
19 Oct 2026 · 371 entries, this one is #15.
Use it now20 You'll notice186 Nothing to try yet7 Under the hood158
Open the release →
Names in this entry
env CLAUDE_CODE_PERSONAL_CONFIG_FIX Setting CLAUDE_CODE_SKIP_PLUGIN_LOCAL_MCP_SERVERS keeps only remote MCP servers from plugins, and several other environment variables are new
env CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG Setting CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG stops your own skills, agents and hooks from widening permissions, and makes key hooks required
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 · 14 of 371
Linux sandbox blocks nested user namespaces by default, with a new…
Use it now Sandbox
In v2.1.304 What probably matters to you release-page order
Next → · 16 of 371
Background agents cut off by a restart can be resumed
You'll notice Background Agents