tengu_teal_corbel
A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.221, including the newest one read.
Artifact live-update watching now carries the plumbing needed for automatic comment replies and cancellation.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.221.
In the changelogs
12Releases whose published page names tengu_teal_corbel.
-
v2.1.248
Permission prompts say whose comment is being acted on
Comment permission prompts can name whose comment it is, behind an artifact-comments env var.
gate cited by this entry, found in this entry's text
-
v2.1.246
Artifact comments refuse organization service keys
Artifact comments now explain org service key failures clearly, but comments themselves need an env var.
gate cited by this entry, found in this entry's text
-
v2.1.239
Artifact request schema: auto_reply gated, embeds compiled out
Artifact auto-reply appears only with comments enabled, and an embeds field is compiled out entirely.
gate cited by this entry, found in this entry's text
-
v2.1.239
Artifact watch entries gain unread-comment counters behind the comments flag
Artifact watches can track unread comments and replies, but only with the comments flag on.
gate cited by this entry, found in this entry's text
-
v2.1.235
Artifact MCP is now on by default (no longer behind
tengu_cloth_snorkel)Artifact MCP enablement no longer falls back to a remote flag, defaulting on unless an env var overrides it
gate cited by this entry
-
v2.1.234
Resuming stopped artifact auto-replies, and marking comments the artifact posted itself
Comments Claude posts to an artifact are now marked as its own, so it stops replying to itself.
gate cited by this entry, found in this entry's text
-
v2.1.227
Artifact auto-replies stop describing their own plumbing
Automatic artifact comment replies now sound like plain acknowledgements instead of describing internal plumbing.
gate cited by this entry, found in this entry's text
-
v2.1.227
Artifact tool can resolve comment threads, behind an off-by-default flag
Claude could mark a comment thread on a published artifact as resolved, but the path is off.
gate cited by this entry, found in this entry's text
-
v2.1.221
Artifact live-update arming carries auto-react wiring
Artifact live-update watching now carries the plumbing needed for automatic comment replies and cancellation.
gate cited by this entry, found in this entry's text
-
v2.1.221
Comment replies always ask, and the prompt names who will see them
Replying to an artifact comment always asks first, and tells you whether the artifact is shared.
gate cited by this entry, found in this entry's text
-
v2.1.221
Artifact auto-reply subscriptions can be stopped from the cancel gestures
Escape or double ctrl+x ctrl+k now also turns off automatic replies to comments on your artifacts.
gate cited by this entry, found in this entry's text
-
v2.1.221
New artifact comment threads: read, reply, resolve
Reading, replying to and resolving comment threads on published artifacts is built in but off unless enabled.
gate cited by this entry, found in this entry's text
Gate readings
7| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.248 | Off by default, switched on for this account | on | on | off |
| v2.1.246 | Off by default, switched on for this account | on | on | off |
| v2.1.239 | Off by default, switched on for this account | on | on | off |
| v2.1.235 | Off by default, switched on for this account | on | on | off |
| v2.1.234 | Off by default, switched on for this account | on | off | off |
| v2.1.227 read on another version | Off by default, switched on for this account | on | on | off |
| v2.1.221 read on another version | Off by default, switched on for this account | on | on | 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
17| Read as | Reading | From | Until | Version installed |
|---|---|---|---|---|
| anonymous | on | 2026-10-17T05:30:04Z | 2026-10-22T23:05:05Z | v2.1.302 to v2.1.309 |
| this account | on | 2026-09-10T21:47:12Z | 2026-10-22T23:05:05Z | v2.1.268 to v2.1.309 |
| 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-17T19: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-18T05:40:04Z | 2026-08-19T03:45:04Z | v2.1.233 |
| anonymous | on | 2026-08-17T19:05:05Z | 2026-08-18T04:50:04Z | v2.1.233 |
| this account | off | 2026-08-17T19:05:05Z | 2026-08-17T19:15:04Z | v2.1.233 |
| this account | on | 2026-08-17T19:03:10Z | 2026-08-17T19:03:10Z | v2.1.234 |
| anonymous | off | 2026-08-14T22:10:05Z | 2026-08-17T19:03:10Z | v2.1.232 to v2.1.234 |
| this account | off | 2026-08-14T22:10:05Z | 2026-08-17T17:05:05Z | v2.1.232 to 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
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
1Build by build
77One 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.