Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.234 Home All releases olderv2.1.233 v2.1.235newer
Claude Code v2.1.234

Artifact comment auto-reply gets a settling window and a stand-down, both server-gated

Not switched on
Useful2 Signal4
Artifacts

Artifact comment replies get grouped wakes and a stand-down when everything was already answered, both switched off.

A settling window and a stand-down path for auto-replies exist but neither is enabled by anything in this build.

Feature flag
tengu_madrone_spindle Gate removed from the code

This release deleted the gate from the code while it was still reading on for the account this site reads, so the code path no longer asks a flag before running.

This account: on · anonymous baseline: on · compiled default in v2.1.234: not a boolean we can read

Read once, for one account on one subscription tier, against v2.1.234. It isn't a statement about your account. What a flag value here can and cannot tell you

What

The scheduler that decides when Claude scans and answers comments on an artifact was reworked so that repeated wakes are grouped together instead of each triggering a scan. Wakes can now be tagged as confirmations or re-entries and are coalesced within a settling window, timers carry extra padding, and the fast-acknowledge flag can be refreshed against a deadline before a decision is made. Alongside it sits a stand-down path that skips replying when every comment addressed to Claude was already answered in a visible turn, and neither the window override nor the stand-down is switched on by anything in this build.

Details
  • The settling window defaults to 2000 ms, can be overridden per call, and can be overridden remotely by the tengu_sorrel_trellis_finial server flag, whose value is clamped to a maximum.
  • The stand-down branch requires the tengu_madrone_spindle server flag to be exactly true and additionally requires every comment recipient to individually pass a check, so it does nothing unless a server config enables it.
  • When the stand-down does fire it records stood_down_visible_turn, which is the string to watch for if the flag is ever turned on.
  • Neither flag has a value set anywhere in the shipped build, so the handoff branch stays off and the wait falls back to the built-in 2000 ms.
  • The instructions Claude receives for handling these comments gained a new label for where a comment came from, "human, posted by the artifact".
Evidence

stood_down_visible_turn, tengu_madrone_spindle

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

See this entry in the whole of v2.1.234 →