tengu_quirky_shore
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.
A new switch, off by default, makes computer-use actions in auto mode go through further permission checks even when an allow rule covers the whole tool
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.284.
In the changelogs
3Releases whose published page names tengu_quirky_shore.
-
v2.1.284
Allow rules may stop auto-approving computer-use clicks and typing in auto mode
A new switch, off by default, makes computer-use actions in auto mode go through further permission checks even when an allow rule covers the whole tool
gate cited by this entry, found in this entry's text
-
v2.1.284
Auto mode can send computer-use actions to its classifier
In auto mode, computer-use actions can now be kept out of the automatic-approval shortcuts so the classifier judges them instead
gate cited by this entry
-
v2.1.284
Plan mode asks before more kinds of tool calls, and allow rules cover less computer use
Plan mode's "Cannot call this while in plan mode" prompt now covers more tools, and a whole-tool allow rule no longer approves some computer-use actions
gate cited by this entry
Gate readings
1| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.284 read on another version | Not enough to say | no value returned | no value returned | 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.
First cited
1The earliest release whose published evidence quoted tengu_quirky_shore 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
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.