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.238 ·

Artifact auto-reply state written into the transcript so it survives resume and fork

Automatic replies to artifact comments would survive resume and fork, but the opt-in is off by default.

Nothing to try yet Notable No documentation found In Development
JSON All of v2.1.238
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.238,
What probably matters to youSection of the release

Two transcript record types carry auto-reply intent across resume and clear, reachable only via CLAUDE_CODE_ARTIFACT_COMMENTS_AUTOREACT or a flag that falls back to off.

What

Two new record types are appended to the session transcript so that automatic replies to artifact comments carry across resume, fork and clear, and so a session can hand its intent to a successor. Reachable only where the artifact comment auto-reply opt-in is on: CLAUDE_CODE_ARTIFACT_COMMENTS_AUTOREACT, or the tengu_sorrel_trellis flag, whose compiled fallback is false.

Details
  • artifact-autoreact-ledger holds per-artifact thread state, seen and sent state, turn timestamps and an interrupted flag, scoped to the account uuid, with a roughly 160 KB budget and progressive shedding, debounced writes and a re-stamp on exit.
  • artifact-comment-monitor holds armed or stopped intent per artifact, with parked lines belonging to other sessions and a torn-tail variant that downgrades armed rows to stopped.
  • A ledger written under a different account is downgraded on load, reported as ledger_foreign_account; write failures report ledger_write_failed.
Evidence

artifact-autoreact-ledger, type: "artifact-autoreact-ledger"

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

Read from
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.238: off

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

Feedback