Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.267entry #5

Claude Code v2.1.267 ·

Artifact 'assets' capability now driven by a cached org roster

Whether the artifact tool exposes an 'assets' action is now decided by a cached per-org capability roster fetched from the server

Group of 2 Nothing to try yet 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

  • A new roster subsystem fetches and disk-caches a per-account/org capabilities roster, used to decide whether the artifact tool schema exposes the "assets" action. The CLAUDE_CODE_ARTIFACT_ASSETS environment variable overrides this entirely; otherwise it falls back to an internal flag (gated by tengu_cobalt_plinth_fennel, off by default), and finally to whatever the cached or live roster from the server reports.
  • After an account switch or login, Claude Code now automatically kicks off an async refresh of this artifact-capability roster.

Why

This keeps the artifact tool's available actions in sync with what an account or organization is actually entitled to, refreshing automatically after login rather than relying on stale cached data.

Read from
Feature flag
tengu_cobalt_plinth_fennel 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: off

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

See this entry in the whole of v2.1.267 →

Feedback