{"version":"2.1.248","anchor":"new-tengu-violin-pegbox-gate-layered-on-top-of-tengu-violin-","canonical_anchor":"new-tengu-violin-pegbox-gate-layered-on-top-of-tengu-violin-","heading":"New tengu_violin_pegbox gate layered on top of tengu_violin_wood","tier":"soon","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/new-tengu-violin-pegbox-gate-layered-on-top-of-tengu-violin-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### New `tengu_violin_pegbox` gate layered on top of `tengu_violin_wood`\n\nRemote sessions started from the desktop app now need a second flag as well.\n\n**What**\n\nA 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.\n\n**Details**\n\n- 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.\n- Which user-facing capability this `tengu_violin_*` family covers is not determinable from the shipped code; the call sites are minified.\n\n**Evidence**\n\n`tengu_violin_pegbox`\n\n- Flag `tengu_violin_wood`: Off in both readings (read for one account on one subscription tier against v2.1.248; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Sessions\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}