What probably matters to youSection of the release
Unclear Which of your own files and settings this mode actually stops from loading is not settled.
What
Claude Code recognizes a new environment variable, CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG. An environment variable is a named value set in your shell before you start a program. When it is set, Claude Code describes the session as one that restricts your own Claude Code files. It is checked alongside the existing locked-down modes:
When Claude Code starts a background session in tmux (a program that keeps terminal sessions running out of sight), it can now launch that session with CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG=1 set, and still passes --restricted as well.
Why
This is a new switch for locking down the configuration that belongs to you personally, and Claude Code checks it in many places.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhich of your own files and settings this mode actually stops from loading is not settled.
Anthropic's release notes agreeFixed --tools and --restricted not applying to built-in tools that register after launch, and deprecated tool names reaching tools outside…
The name it cites is new in this buildNew in this build: CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG
