Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.251 Home All releases olderv2.1.250
Claude Code v2.1.251

In-product permissions for Claude for Chrome is off in this build

Not switched on
Useful2 Signal4
Permissions

The in-product permissions path for Claude for Chrome is hard-disabled here.

The gate now returns false outright, so the server can no longer enable it.

Feature flag
tengu_cfc_in_product_permissions On for this account, and not off by default

The flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.

This account: on · anonymous baseline: on · compiled default in v2.1.251: not a boolean we can read

Read once, for one account on one subscription tier, against v2.1.251. It isn't a statement about your account. What a flag value here can and cannot tell you

What

The check controlling the in-product permissions path for Claude for Chrome used to consult a server-side flag. It now returns false outright, so the path cannot be reached in this build no matter what the server sends.

Details
  • The flag name tengu_cfc_in_product_permissions remains in the build but is no longer read.
Evidence

tengu_cfc_in_product_permissions

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.251 →