tengu_cobalt_plinth_sorrel
A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.234, including the newest one read.
Cloud sessions may route artifact calls through a gateway relay, falling back to direct calls on failure.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.234.
In the changelogs
5Releases whose published page names tengu_cobalt_plinth_sorrel.
-
v2.1.287
Artifact tools can refuse network use when an organization policy applies
When an organization network policy covers a session, artifact tools now refuse to post or fetch and explain that network access is off
gate cited by this entry
-
v2.1.247
Artifact relay skips bot-driven sessions
Bot-driven sessions no longer relay artifact requests; they go direct or not at all.
gate cited by this entry, found in this entry's text
-
v2.1.242
Cobalt-plinth flags renamed again
Several artifact feature switches were renamed and re-gated, discarding any prior rollout.
gate cited by this entry, found in this entry's text
-
v2.1.236
Blocked artifact reads retry through the session gateway
Artifact reads blocked by your network allowlist now retry through the session gateway instead of failing.
gate cited by this entry, found in this entry's text
-
v2.1.234
Artifact requests from cloud sessions can go via a gateway relay
Cloud sessions may route artifact calls through a gateway relay, falling back to direct calls on failure.
gate cited by this entry, found in this entry's text
Gate readings
5| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.287 read on another version | On for this account, and not off by default | on | on | on |
| v2.1.247 | On for this account, and not off by default | on | on | not a boolean we can read |
| v2.1.242 | On for this account, and not off by default | on | on | on |
| v2.1.236 | On for this account, and not off by default | on | on | on |
| v2.1.234 | On for this account, and not off by default | on | on | on |
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
12| Read as | Reading | From | Until | Version installed |
|---|---|---|---|---|
| anonymous | on | 2026-10-17T05:30:04Z | 2026-10-22T06:25:04Z | v2.1.302 to v2.1.308 |
| this account | on | 2026-09-10T21:47:12Z | 2026-10-22T06:25:04Z | v2.1.268 to v2.1.308 |
| anonymous | no longer carried | 2026-10-17T05:25:57Z | 2026-10-17T05:25:57Z | v2.1.302 |
| anonymous | on | 2026-08-19T04:25:04Z | 2026-10-17T05:10:04Z | v2.1.233 to v2.1.302 |
| this account | no longer carried | 2026-09-10T21:46:45Z | 2026-09-10T21:46:45Z | v2.1.268 |
| this account | on | 2026-09-08T20:36:15Z | 2026-09-10T17:40:05Z | v2.1.263 to v2.1.267 |
| this account | no longer carried | 2026-09-08T20:34:58Z | 2026-09-08T20:34:58Z | v2.1.265 |
| this account | on | 2026-09-06T02:40:05Z | 2026-09-08T18:45:05Z | v2.1.261 to v2.1.263 |
| this account | no longer carried | 2026-09-06T02:36:19Z | 2026-09-06T02:36:19Z | v2.1.263 |
| this account | on | 2026-08-16T05:25:04Z | 2026-09-06T01:55:04Z | v2.1.233 to v2.1.261 |
| anonymous | no longer carried | 2026-08-19T04:20:14Z | 2026-08-19T04:20:14Z | v2.1.233 |
| anonymous | on | 2026-08-16T04:55:04Z | 2026-08-19T03:45:04Z | v2.1.233 |
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_cobalt_plinth_sorrel was v2.1.234, 17 Aug 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
64One 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.