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

Artifact watches can answer comments posted just before the watch started

A comment sent moments before a watch starts could get a reply, but the flag is off.

Nothing to try yet In Development
JSON All of v2.1.236
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.236,
In DevelopmentSection of the release

A recency window for pre-watch comments sits behind tengu_sorrel_trellis_lintel, which falls back to off.

What

When Claude starts watching an artifact for comments, comments addressed to it within a short recency window are no longer treated as already-seen history, so a summons sent moments before the watch existed gets a reply instead of being silently ignored. It is decided by tengu_sorrel_trellis_lintel, which falls back to off, so with no server value the old behaviour of baselining everything stands.

Details
  • Only applies on an explicit publish-time arm of the watch, not on every start.
  • Also forces a refresh of the fast-acknowledgement flag that would otherwise be skipped.
  • The surrounding comment-autoreply feature is itself behind tengu_sorrel_trellis and CLAUDE_CODE_ARTIFACT_COMMENTS_AUTOREACT.
  • Neither the gate nor this code path exists in 2.1.235.
Evidence

tengu_sorrel_trellis_lintel

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.236: off

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

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_sorrel_trellis_lintel

See this entry in the whole of v2.1.236 →

Feedback