CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG
A Claude Code environment variable, read out of the shipped bundle. It has been in the build since v2.1.295, including the newest one read.
Setting CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG stops your own skills, agents and hooks from widening permissions, and makes key hooks required
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.295.
In the changelogs
7Releases whose published page names CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG.
-
v2.1.295
A new setting limits what your own skills, agents and hooks can do
Setting CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG stops your own skills, agents and hooks from widening permissions, and makes key hooks required
found in this entry's text, named in this entry
-
v2.1.295
New
CLAUDE_CODE_RESTRICT_PERSONAL_CONFIGmode restricts your own Claude Code filesSetting
CLAUDE_CODE_RESTRICT_PERSONAL_CONFIGstarts a session that restricts your own Claude Code files, alongside the other restricted modesfound in this entry's text, named in this entry
-
v2.1.295
Sessions started by Claude Code can inherit the restrict-personal-config mode
Under a certain condition, Claude Code now sets
CLAUDE_CODE_RESTRICT_PERSONAL_CONFIGto1for the sessions it startsfound in this entry's text, named in this entry
-
v2.1.295
New option to block a session when your personal settings file is broken
With
CLAUDE_CODE_RESTRICT_PERSONAL_CONFIGset, errors in your user settings file block every prompt and tool call until they are fixedfound in this entry's text, named in this entry
-
v2.1.295
Restricted sessions block your own agents' MCP servers and cloud launches
With CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG set, your own agents' MCP servers are skipped and launching an agent in the cloud is refused
found in this entry's text, named in this entry
-
v2.1.295
Your own hooks can no longer rewrite tool calls or answers in personal mode
In a new personal mode, hooks from your own files can no longer change a tool call's input or certain tool results, and Claude Code says so
named in this entry
-
v2.1.295
Cloud agents cannot be launched from a session that restricts personal config
With
CLAUDE_CODE_RESTRICT_PERSONAL_CONFIGset, launching a cloud agent is refused and you are told to use worktree isolationfound in this entry's text, named in this entry
First cited
9The earliest release whose published evidence quoted CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG was v2.1.295, 8 Oct 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.
3 further spans in the ledger name it. The list above is the earliest first and stops at 6.
Presence across releases
1Build by build
1One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the environment variable does. All environment variables.