tengu_cobalt_plinth_holly
A Claude Code feature flag, read out of the shipped bundle. It was in the build from v2.1.259 and was gone by v2.1.285.
Artifacts gain full pin and unpin actions, wired end to end but off by default behind a gate with an env override.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.259.
In the changelogs
6Releases whose published page names tengu_cobalt_plinth_holly.
-
v2.1.285
Artifact pinning no longer depends on a server switch and defaults to on
Artifact pinning is now on by default unless
CLAUDE_CODE_ARTIFACT_PINturns it off, with no server switch consultedgate cited by this entry
-
v2.1.285
Artifact pinning no longer waits on a remote switch
Artifact pinning is now on by default in local sessions, and
CLAUDE_CODE_ARTIFACT_PINstill overrides itgate cited by this entry
-
v2.1.269
CLAUDE_CODE_ARTIFACT_PIN gate gains an extra suppression condition
Artifact pinning is now also suppressed for remote sessions when an additional internal check is true
gate cited by this entry, found in this entry's text
-
v2.1.259
Artifact pin/unpin — gated off by default
Artifacts gain full pin and unpin actions, wired end to end but off by default behind a gate with an env override.
gate cited by this entry
-
v2.1.259
Artifact tool gains a publish-time 'pin' parameter, behind a flag
The artifact publish action can offer a pin field, but it is refused outright in cloud sessions and otherwise depends on an env var or gate.
gate cited by this entry
-
v2.1.259
Artifact pinning gated behind new flag, with richer relay error handling
Pin and unpin go through a relay path with clearer failure messages, and a gated helper decides whether pinning is offered at all.
gate cited by this entry
Gate readings
3| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.285 read on another version | On for this account, and not off by default | on | on | not a boolean we can read |
| v2.1.269 | Off by default, switched on for this account | on | on | off |
| v2.1.259 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
12| Read as | Reading | From | Until | Version installed |
|---|---|---|---|---|
| anonymous | on | 2026-10-17T05:30:04Z | 2026-11-12T12:20:06Z | v2.1.302 to v2.1.322 |
| this account | on | 2026-09-10T21:47:12Z | 2026-11-12T12:20:06Z | v2.1.268 to v2.1.322 |
| anonymous | no longer carried | 2026-10-17T05:25:57Z | 2026-10-17T05:25:57Z | v2.1.302 |
| anonymous | on | 2026-09-10T17:15:04Z | 2026-10-17T05:10:04Z | v2.1.267 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-10T17:40:05Z | 2026-09-10T17:40:05Z | v2.1.267 |
| this account | off | 2026-09-08T20:36:15Z | 2026-09-10T17:15:04Z | v2.1.263 to v2.1.267 |
| anonymous | off | 2026-08-31T21:35:04Z | 2026-09-10T17:10:08Z | v2.1.251 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-31T23:15:05Z | 2026-09-06T01:55:04Z | v2.1.251 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
0No release's published evidence quotes this name. The ledger indexes the Evidence lines of every changelog on this site, so this says nobody here has ever quoted it; it says nothing about how old the name is.
Presence across releases
2Build by build
57One 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.