Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.232 ·

Artifacts upload conditions simplified

Artifact availability now hinges on one gate, and direct upload kicks in for create paths.

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

Artifacts remain behind tengu_cobalt_plinth, off by default, with direct upload overridable via CLAUDE_CODE_ARTIFACT_DIRECT_UPLOAD.

What

The check for whether artifacts are available dropped a secondary condition and is now the environment term or the tengu_cobalt_plinth gate, which is off by default. Direct upload, gated by tengu_cobalt_plinth_direct (on by default) and CLAUDE_CODE_ARTIFACT_DIRECT_UPLOAD, now also kicks in whenever a create path is supplied.

Details
  • The entrypoint set that previously forced direct upload still does so.
Evidence

tengu_cobalt_plinth_direct

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Feature flag
tengu_cobalt_plinth Off by default, switched on for this account

The shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.

This account: on · anonymous baseline: on · compiled default in v2.1.232: off

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

tengu_cobalt_plinth_direct 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.232: on

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.232. 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, 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 nothing at all, having stopped carrying it for tengu_cobalt_plinth, 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.
Gate removed from the code v2.1.260 removed the tengu_cobalt_plinth gate from the code while it was still reading on for the account this site reads. The code path no longer asks a flag before it runs.

See this across every release →

See this entry in the whole of v2.1.232 →

Feedback