tengu_violin_soundpost
A Claude Code feature flag, read out of the shipped bundle. It was in the build from v2.1.277 and was gone by v2.1.282.
Directory sync gains a pre-attach safety check to verify a checkout can attach cleanly, behind a new gate
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.277.
In the changelogs
7Releases whose published page names tengu_violin_soundpost.
-
v2.1.284
Directory sync no longer waits on a remote switch before offering to sync a cloud session
When a cloud session attaches, Claude Code now offers directory sync without first checking a remotely controlled switch that could hold it back
gate cited by this entry
-
v2.1.284
Cloud folder sync now signs uploads from your device and can be switched off by Anthropic
Folder sync for cloud sessions now signs uploads as the bound device, and stops with a message if this computer can't or Anthropic switches it off
gate cited by this entry, found in this entry's text
-
v2.1.283
Directory sync keeps the .gitattributes files it relies on and explains git settings it can't follow
Directory sync now keeps the committed .gitattributes files it read, and refuses with a fix-it message when a git setting changes attribute rules
gate cited by this entry
-
v2.1.282
Attaching a local git folder to a cloud session with file sync is built but off
Code to attach a local git checkout to a running cloud session and keep files in sync is built, behind a switch that is off by default
gate cited by this entry, found in this entry's text
-
v2.1.282
Attaching to a cloud session can set up its connection sooner
When attaching to a cloud session in serve mode, Claude Code can now prepare the connection while it reads the stream position, not afterwards
gate cited by this entry
-
v2.1.277
New attach-sync safety check for directory sync (git worker), gated by tengu_violin_soundpost
Directory sync gains a pre-attach safety check to verify a checkout can attach cleanly, behind a new gate
found in this entry's text, named in this entry
-
v2.1.277
New "sync at attach" flow for cloud/dir-sync sessions, gated behind two flags plus a peer capability
A new 'sync at attach' step can pull a peer's files in before directory sync starts, gated behind flags and a peer capability
found in this entry's text, named in this entry
Gate readings
3| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.284 read on another version | On for this account, and not off by default | on | on | not a boolean we can read |
| v2.1.283 read on another version | Off by default, switched on for this account | on | on | off |
| v2.1.282 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
6| Read as | Reading | From | Until | Version installed |
|---|---|---|---|---|
| anonymous | on | 2026-10-17T05:30:04Z | 2026-11-06T13:15:04Z | v2.1.302 to v2.1.318 |
| this account | on | 2026-09-25T15:25:05Z | 2026-11-06T13:15:04Z | v2.1.282 to v2.1.318 |
| anonymous | no longer carried | 2026-10-17T05:25:57Z | 2026-10-17T05:25:57Z | v2.1.302 |
| anonymous | on | 2026-09-25T15:15:05Z | 2026-10-17T05:10:04Z | v2.1.282 to v2.1.302 |
| this account | off | 2026-09-23T19:25:05Z | 2026-09-25T15:15:05Z | v2.1.280 to v2.1.282 |
| anonymous | off | 2026-09-23T19:00:06Z | 2026-09-25T12:50:04Z | v2.1.280 to v2.1.282 |
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
1The earliest release whose published evidence quoted tengu_violin_soundpost was v2.1.277, 18 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
2Build by build
39One 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.