tengu_violin_purfling
A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.283, including the newest one read.
A forwarded shell command that writes your machine's Claude Code settings files is blocked or sent to you for approval
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.283.
In the changelogs
4Releases whose published page names tengu_violin_purfling.
-
v2.1.288
Agent proxy certificate setup reworked and no longer checks a server setting there
Setting up trust for the agent proxy's certificate no longer checks a server switch there and now catches certificates listed in swapped order
gate cited by this entry, found in this entry's text
-
v2.1.288
Served sessions refuse edits to settings files and flag network paths
In served sessions, Claude can no longer edit settings files, and permission prompts for network paths are never approved automatically
gate cited by this entry, found in this entry's text
-
v2.1.283
Cloud sessions cannot rewrite your Claude Code settings through shell commands
A forwarded shell command that writes your machine's Claude Code settings files is blocked or sent to you for approval
gate cited by this entry
-
v2.1.283
Shell commands from a remote session that change Claude Code settings can be held for review
Two new safeguards against a remote session changing Claude Code's settings files through shell commands
gate cited by this entry
Gate readings
2| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.288 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 | On for this account, and not off by default | on | on | not a boolean we can read |
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
4| Read as | Reading | From | Until | Version installed |
|---|---|---|---|---|
| anonymous | on | 2026-10-17T05:30:04Z | 2026-11-12T17:30:05Z | v2.1.302 to v2.1.322 |
| this account | on | 2026-09-21T19:25:04Z | 2026-11-12T17:30:05Z | v2.1.278 to v2.1.322 |
| anonymous | no longer carried | 2026-10-17T05:25:57Z | 2026-10-17T05:25:57Z | v2.1.302 |
| anonymous | on | 2026-09-21T17:25:05Z | 2026-10-17T05:10:04Z | v2.1.278 to v2.1.302 |
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
2The earliest release whose published evidence quoted tengu_violin_purfling was v2.1.283, 25 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
5Build by build
36One 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.