tengu_violin_maple
A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.284, including the newest one read.
Claude Code gains switches for a connected mode for cloud sessions and a file sync that depends on it, both off unless turned on remotely
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.284.
In the changelogs
5Releases whose published page names tengu_violin_maple.
-
v2.1.284
Groundwork for connected cloud sessions with file sync, off by default
Claude Code gains switches for a connected mode for cloud sessions and a file sync that depends on it, both off unless turned on remotely
gate cited by this entry, found in this entry's text
-
v2.1.284
Remote sessions from the desktop app no longer need an extra flag
Remote sessions started from the Claude desktop app now depend on the same single flag as every other starting point
gate cited by this entry, found in this entry's text
-
v2.1.284
Working-folder display in remote mode follows a second remote switch
How the header shows your working folder in remote mode can now also be switched by the remote setting behind connected cloud sessions
gate cited by this entry, found in this entry's text
-
v2.1.284
Cloud-session attach and folder sync get new remote switches
Joining an existing cloud session, trusted-device enrollment and the folder sync offer can now be turned on by two new remote switches, off by default
gate cited by this entry, found in this entry's text
-
v2.1.284
Staying connected to a cloud session from
--cloudcan be switched on by a new remote settingStaying attached to a cloud session started with
--cloudcan now also be turned on remotely, and the offer to sync files hangs on its own switchgate cited by this entry, found in this entry's text
Gate readings
1| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.284 read on another version | Off in both readings | off | off | off |
Two arms, because they disagree: this account is the one account this site reads and anonymous is a baseline with no identity attached. A reading says nothing about your account, and off cannot rule out a rollout both readings sit outside of. What these readings can and cannot show.
Flag server, over time
2| Read as | Reading | From | Until | Version installed |
|---|---|---|---|---|
| anonymous | off | 2026-09-25T22:40:04Z | 2026-09-28T19:25:06Z | v2.1.283 to v2.1.284 |
| this account | off | 2026-09-25T22:40:04Z | 2026-09-28T19:25:06Z | v2.1.283 to v2.1.284 |
One row per unbroken stretch of one reading, newest first, from snapshots taken every twenty-five minutes or so. No longer carried is not off: it means the flag server stopped returning the gate at all, which is what a retired experiment looks like. The version column is what was installed when the reading was taken, not what caused it.
First cited
3The earliest release whose published evidence quoted tengu_violin_maple was v2.1.284, 28 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.
Presence across releases
1Build by build
1One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the feature flag does. All feature flags.