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
HomeReleasesv2.1.295entry #27

Claude Code 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

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

When the environment variable CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG is set, two things change for agents (helpers Claude can hand work to) that you defined in your own files:

  • MCP servers listed in the agent's own definition are skipped. MCP servers are outside programs that give Claude extra tools.
  • Launching an agent to run in the cloud, on a remote machine, fails with an error.

The permission mode used for agents run remotely can now also be limited so that it can only be narrowed, never widened.

Why

In a locked-down session, agents you defined yourself cannot bring in their own tools or move work to a remote machine.

Read from
Names in the bundleCLAUDE_CODE_RESTRICT_PERSONAL_CONFIG
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