tengu_violin_pegbox stacks on tengu_violin_wood; both fall back to false.
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.
- 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.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_violin_wood Off in both readingsThe 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: off
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
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.