tengu_radiant_heron
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 Remote Control background process can now tell cloud sessions they may use your local folder and its tools, if a server switch and several checks allow it
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.283.
In the changelogs
5Releases whose published page names tengu_radiant_heron.
-
v2.1.283
Remote Control can offer this folder and its tools to cloud sessions, behind a server switch
A Remote Control background process can now tell cloud sessions they may use your local folder and its tools, if a server switch and several checks allow it
gate cited by this entry, found in this entry's text
-
v2.1.283
Help for
claude daemonlists commands to manage Remote Control serversclaude daemonhelp can now listremote-control list,addandremove, and worker status reports the folder being servedgate cited by this entry
-
v2.1.283
This machine can be offered to cloud sessions as a place to use tools
Claude Code can now tell cloud sessions that this machine's folder and tools are available, under a server setting that is off by default
gate cited by this entry, found in this entry's text
-
v2.1.283
claude daemon remote-controlnow checked separately from other daemon commandsThe remote-control daemon subcommand now has its own availability check, while list, scheduled and hub remain unavailable
gate cited by this entry
-
v2.1.283
A disabled Remote Control sign-in feature can now be switched on remotely
A check in Remote Control's background sign-in code that always said no now follows a server flag that is off by default
gate cited by this entry
Gate readings
1| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.283 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 |
|---|---|---|---|---|
| this account | off | 2026-09-22T19:25:07Z | 2026-09-28T06:45:05Z | v2.1.280 to v2.1.283 |
| anonymous | off | 2026-09-22T19:00:07Z | 2026-09-28T06:45:05Z | v2.1.280 to v2.1.283 |
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_radiant_heron 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
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.