Follow Discord
Sweep 28 Sep 2026 · 18:16Z Build v2.1.284 505 read Stable v2.1.277 Latest v2.1.284 Next v2.1.284 Feeds RSS JSON llms.txt llms-full.txt Unofficial

tengu_drifting_reef

flag in the build JSON

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.

First seen v2.1.284 28 Sep 2026
Last seen v2.1.284 28 Sep 2026
Builds1 / 127on this box, as of v2.1.284
Written about v2.1.284 first named in a changelog, 28 Sep 2026
v2.1.284in the build not in the build never minedv2.1.284

In the changelogs

3

Releases whose published page names tengu_drifting_reef.

  1. 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

  2. v2.1.284
    Browser and computer-use actions can carry a short summary of their effect

    Browser and desktop control tools can ask Claude for a few words on what each action does, off unless switched on remotely

    gate cited by this entry

  3. v2.1.284
    Chrome browser tools can ask Claude to summarise each action

    Claude Code's Chrome tools can ask Claude for a few words describing each click, keypress, typing or form fill, off unless switched on remotely

    gate cited by this entry

Gate readings

1
ReleaseResolvedThis accountAnonymousCompiled 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.

Flag server, over time

2
Read asReadingFromUntilVersion installed
this account [] 2026-09-25T22:40:04Z 2026-09-28T20:55:04Z v2.1.283 to v2.1.284
anonymous [] 2026-09-25T22:35:04Z 2026-09-28T20:55:04Z 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

1

The earliest release whose published evidence quoted tengu_drifting_reef 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.

ReleaseDateThe span that was quoted
v2.1.28428 Sep 2026tengu_drifting_reef

Presence across releases

1
BuildsHow manyDatesReading
v2.1.2841 build28 Sep 2026 ◆in the build

Build by build

1

One 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.

BuildDateStateThe record behind it
v2.1.28428 Sep 2026·addedverdict: added · default unknown

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.

Feedback