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.248 Home All releases olderv2.1.247 v2.1.250newer
Claude Code v2.1.248

New tengu_violin_pegbox gate layered on top of tengu_violin_wood

Not switched on
Useful1 Signal3
Sessions

Remote sessions started from the desktop app now need a second flag as well.

tengu_violin_pegbox stacks on tengu_violin_wood; both fall back to false.

Feature flag
tengu_violin_wood Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.248: on

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

What

A second feature flag now applies to remote sessions started from the Claude desktop app. Where the entrypoint is remote_desktop, the remote feature set requires both tengu_violin_pegbox and tengu_violin_wood; everywhere else tengu_violin_wood alone still decides. Both flags compile in with a fallback of false, so without server-side values the feature is off.

Details
  • There is a matching asynchronous check, and a helper that reports which flag name a decision should be attributed to, naming pegbox only on the desktop entrypoint with wood already on.
  • Which user-facing capability this tengu_violin_* family covers is not determinable from the shipped code; the call sites are minified.
Evidence

tengu_violin_pegbox

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.248 →