Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.267 ·

Artifact feature: env var and gate renamed (artifact DB -> artifact type catalog)

The artifact type catalog's override variable and internal flag were renamed

Nothing to try yet No documentation found In Development
JSON All of v2.1.267
Nothing to try yetTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
In DevelopmentKind: in v2.1.267,
What probably matters to youSection of the release
What

An internal feature related to Artifacts (browsing published artifact types) had its override environment variable and internal feature flag renamed: CLAUDE_CODE_ARTIFACT_DB became CLAUDE_CODE_ARTIFACT_TYPE_CATALOG, and the underlying flag went from tengu_umber_lattice to tengu_cobalt_plinth_larch. Both still default to off unless a value is supplied.

Why

This is a naming cleanup for a feature that lets Claude browse and describe published artifact types to start new work from; the rename doesn't change whether the feature is on, only what it's called internally.

Read from
Feature flag
tengu_cobalt_plinth_larch Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.267: not a boolean we can read

tengu_umber_lattice On for this account, and not off by default

The flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.

This account: on · anonymous baseline: on · compiled default in v2.1.267: not a boolean we can read

Read once, for one account on one subscription tier, against v2.1.267. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns on for tengu_cobalt_plinth_larch, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns off for tengu_cobalt_plinth_larch, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns on for tengu_cobalt_plinth_larch, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

See this entry in the whole of v2.1.267 →

Feedback