tengu_cobalt_plinth_samphire
A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.260, including the newest one read.
Multi-file artifact publish can copy published files between artifacts, tracked while still gated off.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.260.
In the changelogs
5Releases whose published page names tengu_cobalt_plinth_samphire.
-
v2.1.260
Multi-file artifact publish can now also copy published files between artifacts
Multi-file artifact publish can copy published files between artifacts, tracked while still gated off.
gate cited by this entry
-
v2.1.260
Copy-from asset language pre-written into upload/read consent prompts
Consent prompt wording for copying assets between artifacts is written but not yet shown.
gate cited by this entry
-
v2.1.260
Artifact publishing can copy files from other artifacts, but it's off by default
Artifact publishing can copy files from other artifacts server-side, but it's off by default.
found in this entry's text, gate cited by this entry
-
v2.1.260
Artifact asset store gains a server-side copy_from action
Artifact assets can now be copied server-side between artifacts without downloading them.
gate cited by this entry
-
v2.1.260
Artifacts tool gains a "copy_from" action, behind a new flag defaulting off
The artifact copy_from action is gated behind a new flag that defaults off.
found in this entry's text, named in this entry, gate cited by this entry
Gate readings
1| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.260 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
19| Read as | Reading | From | Until | Version installed |
|---|---|---|---|---|
| this account | on | 2026-11-02T13:05:04Z | 2026-11-12T08:10:04Z | v2.1.316 to v2.1.322 |
| anonymous | off | 2026-10-17T05:30:04Z | 2026-11-12T08:10:04Z | v2.1.302 to v2.1.322 |
| this account | off | 2026-11-02T12:55:05Z | 2026-11-02T12:55:05Z | v2.1.316 |
| this account | on | 2026-11-01T20:45:05Z | 2026-11-02T12:40:07Z | v2.1.316 |
| this account | off | 2026-11-01T20:40:05Z | 2026-11-01T20:40:05Z | v2.1.316 |
| this account | on | 2026-11-01T20:25:04Z | 2026-11-01T20:30:06Z | v2.1.316 |
| this account | off | 2026-11-01T20:20:05Z | 2026-11-01T20:20:05Z | v2.1.316 |
| this account | on | 2026-10-22T00:10:04Z | 2026-11-01T19:30:06Z | v2.1.307 to v2.1.316 |
| this account | off | 2026-10-21T21:10:07Z | 2026-10-21T23:05:05Z | v2.1.306 to v2.1.307 |
| this account | on | 2026-10-21T21:09:42Z | 2026-10-21T21:09:42Z | v2.1.307 |
| this account | off | 2026-09-10T21:47:12Z | 2026-10-21T20:45:05Z | v2.1.268 to v2.1.306 |
| anonymous | no longer carried | 2026-10-17T05:25:57Z | 2026-10-17T05:25:57Z | v2.1.302 |
| anonymous | off | 2026-09-03T19:05:05Z | 2026-10-17T05:10:04Z | v2.1.259 to v2.1.302 |
| this account | no longer carried | 2026-09-10T21:46:45Z | 2026-09-10T21:46:45Z | v2.1.268 |
| this account | off | 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 | off | 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 | off | 2026-09-03T19:25:04Z | 2026-09-06T01:55:04Z | v2.1.259 to v2.1.261 |
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_samphire was v2.1.260, 3 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
56One 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.