Cache-break diagnostics note when the baseline was loaded from disk / Claude Code v2.1.232

Under the hood

Useful1 Signal2

Elsewhere

Cache diagnostics know when the baseline came from disk and skip misleading difference reports.

Feature flag

tengu_prompt_cache_diagnostics 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.232: on

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

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

What

Prompt cache diagnostics now record whether the comparison baseline came from the on-disk snapshot rather than the current process, and suppress removed-tool and removed-beta diffs while that is the case to avoid false positives.

Details

The flag is cleared after the first comparison and reported in the tengu_prompt_cache_break event.
Gated behind the tengu_prompt_cache_diagnostics flag, which falls back to off.

Evidence

baselineFromDisk

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