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
HomeReleasesv2.1.233entry #24

Claude Code v2.1.233 ·

Turning off artifact auto-react now survives a restart

Turning off artifact auto-replies now sticks across a background session restart.

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

A hidden --watch-artifact-no-autoreact option rewrites relaunch arguments, but only matters when artifact watching is enabled.

What

A hidden --watch-artifact-no-autoreact <artifact> option was added and is accepted by the argument sanitizers alongside --watch-artifact. When you disarm auto-react in a session, the launch arguments are rewritten to swap in the new flag with the same artifact id, and background-job respawn flags are updated, so a restarted background session stays disarmed.

Details
Evidence

--watch-artifact-no-autoreact

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

Read from
Names in the bundle--watch-artifact-no-autoreact--watch-artifact
Feature flag
tengu_sorrel_trellis 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.233: 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.

Read once, for one account on one subscription tier, against v2.1.233. 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_sorrel_trellis, 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_sorrel_trellis, 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_sorrel_trellis, 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_sorrel_trellis, 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.233 →

Feedback