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.295 ·

New option to block a session when your personal settings file is broken

With CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG set, errors in your user settings file block every prompt and tool call until they are fixed

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

A new environment variable, CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG, turns on a stricter check of your user settings file (your personal Claude Code settings). An environment variable is a named value set in the shell before Claude Code starts.

When the session starts with it set, Claude Code reads your user settings file. If the file has errors, or its hooks or permission rules have errors, Claude Code blocks every prompt and every tool call (an action Claude wants to take, such as running a command or editing a file) for the whole session. A blocked tool call gives the reason "A problem in your user settings file is blocking tool calls".

Hooks are actions you configure to run automatically at set points. With this check on, these hooks are rejected unless they are command hooks or http hooks:

Why

The session fails closed, meaning it stops rather than carrying on. A broken personal settings file therefore cannot quietly drop deny rules or hooks that an organisation relies on in a managed or restricted setup.

Read from
How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG

See this entry in the whole of v2.1.295 →

Feedback