tengu_cobalt_plinth_mallow
A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.282, including the newest one read.
Artifact comment and subscription operations can each be switched on separately from the server.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.251.
In the changelogs
4Releases whose published page names tengu_cobalt_plinth_mallow.
-
v2.1.282
Artifacts written by other people get new warning wording, off by default
Claude Code can now wrap artifacts it reads as a non-owner in their own warnings, behind two remote switches that default to off
gate cited by this entry, found in this entry's text
-
v2.1.282
Full reads of shared artifacts beyond your own channel are built but switched off
Claude Code can now let the model read other people's shared artifacts in full, but only when a server switch that is off by default is on
gate cited by this entry
-
v2.1.282
Artifact reads now summarise files from other organizations and hold back unsafe text
Files from another organization's artifacts now come back only as summaries, and files with terminal control bytes are saved to disk instead
gate cited by this entry, found in this entry's text
-
v2.1.251
Per-operation flags for artifact comments, subscriptions and types
Artifact comment and subscription operations can each be switched on separately from the server.
gate cited by this entry, found in this entry's text
Gate readings
2| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.282 read on another version | Off in both readings | off | off | off |
| v2.1.251 | Off in both readings | off | off | 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
8| Read as | Reading | From | Until | Version installed |
|---|---|---|---|---|
| this account | off | 2026-09-10T21:47:12Z | 2026-09-28T08:05:05Z | v2.1.268 to v2.1.283 |
| anonymous | off | 2026-08-28T02:30:05Z | 2026-09-28T08:05:05Z | v2.1.246 to v2.1.283 |
| 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-08-28T02:55:04Z | 2026-09-06T01:55:04Z | v2.1.246 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_mallow was v2.1.282, 24 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
2One 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.