Perforce users get a one-time tip to turn on Perforce mode

In a Perforce workspace with Perforce mode off, Claude Code shows a tip once to set CLAUDE_CODE_PERFORCE_MODE=1

Use it now Notable Improvements

JSON All of v2.1.323

Use it nowTier: how much it should matter to you

3Useful: my rating, 1 to 5

1Signal: worth watching, 1 to 5

PerforceArea: what it touches

ImprovementsKind: in v2.1.323, 12 Nov 26

What probably matters to youSection of the release

What

Perforce is a version control system that keeps files read-only until you check them out. When Claude Code detects a Perforce workspace and Perforce mode is off, it now shows a tip suggesting you set CLAUDE_CODE_PERFORCE_MODE=1 to protect read-only files. The tip is shown only once.

Why

Perforce users are pointed to a protection mode they might not otherwise know about.

Read from

Names in the bundleCLAUDE_CODE_PERFORCE_MODE

How sure we are

One source agreesOne thing we can check says the same as this entry.

Anthropic's release notes agreeAdded a one-time startup notice naming CLAUDE_CODE_PERFORCE_MODE when Perforce settings are found and the mode is off

See this entry in the whole of v2.1.323 →

The build it came inv2.1.323

12 Nov 2026 · 888 entries, this one is #96.

Use it now77
You'll notice533
Nothing to try yet64
Under the hood214

Either side of it

v2.1.322Older

Open the release →

Names in this entry

envCLAUDE_CODE_PERFORCE_MODE
Environment variables from your settings are now added before Claude Code filters the environment it passes to programs it starts

Anthropic's note

Upstream's own release notes for v2.1.323 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.

Added a one-time startup notice naming CLAUDE_CODE_PERFORCE_MODE when Perforce settings are found and the mode is off

Is this right?