New env var to suppress the CFC (co-founder?) prompt

A new env var lets you or your org suppress the CFC prompt outright.

Use it now Notable New Features

JSON All of v2.1.257

Use it nowTier: how much it should matter to you

5Useful: my rating, 1 to 5

3Signal: worth watching, 1 to 5

AgentsArea: what it touches

New FeaturesKind: in v2.1.257, 01 Sep 26

What probably matters to youSection of the release

The CFC prompt's disabled state can now also be controlled with the CLAUDE_CODE_DISABLE_CFC_PROMPT environment variable, giving users and organizations a way to suppress it that doesn't depend on the existing internal check.

Read from

Names in the bundleCLAUDE_CODE_DISABLE_CFC_PROMPT

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_DISABLE_CFC_PROMPT

See this entry in the whole of v2.1.257 →

The build it came inv2.1.257

1 Sep 2026 · 505 entries, this one is #73.

Use it now45
You'll notice231
Nothing to try yet71
Under the hood158

Either side of it

v2.1.252Older
v2.1.258Newer

Open the release →

Names in this entry

envCLAUDE_CODE_DISABLE_CFC_PROMPT
Set to 1 to keep the Claude in Chrome browser tools available while omitting the Chrome section of the system prompt and the /claude-in-chrome bundled skill. For hosts that embed Claude Code and supply their own browser guidance. Requires Claude Code v2.1.257 or later

Is this right?