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.241 Home All releases olderv2.1.240 v2.1.242newer
Claude Code v2.1.241

Narration gate state now reported to the VS Code extension

Not switched on
Useful2 Signal4
IDE Integration Notable not in their notes

A narration-summary feature can be forced on with an env var, but it's off by default here.

Narration summaries sit behind a flag that is off unless server config or CLAUDE_CODE_SABLE_THRUSH turns it on, and the VS Code extension is now told its state.

Feature flag
tengu_sable_thrush 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.241: on

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

CLAUDE_CODE_SABLE_THRUSH
What

Claude Code sends the VS Code extension a map of experiment flags at startup, and that map gains one entry, tengu_sable_thrush, so the IDE side can branch on whether narration summaries are enabled. The flag is off by default in this build unless a server config turns it on. Set CLAUDE_CODE_SABLE_THRUSH to force it on or off in either direction.

Details
  • The value comes from the narration module's own check: the environment variable wins if set, otherwise the remote flag is consulted with an in-source fallback of false.
  • The result is read once and latched for the process; a test-only helper exists to clear that latch.
  • The flag itself is not new, it already drove narration-summary rendering in 2.1.240. What is new is that its state is shared with the extension.
  • What the extension does with the value lives outside this build.
Evidence

tengu_sable_thrush: (Cmr(), ln(uYr)).isSableThrushEnabled(),

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

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.241 →