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.235 Home All releases olderv2.1.234 v2.1.236newer
Claude Code v2.1.235

Fixed-menu fast acknowledgment for artifact comments, behind two nested off-by-default gates

Not switched on
Useful1 Signal4
Artifacts Notable not in their notes

A cheaper canned way to acknowledge artifact comments exists but needs two env vars switched on.

Fixed-menu fast acknowledgment for artifact comments sits behind CLAUDE_CODE_ARTIFACT_COMMENT_FAST_ACK_FIXED nested inside CLAUDE_CODE_ARTIFACT_COMMENT_FAST_ACK, both false by default.

Feature flag
tengu_gorse_sill Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.235: on

tengu_gorse_pylon Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.235: on

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

CLAUDE_CODE_ARTIFACT_COMMENT_FAST_ACK_FIXEDCLAUDE_CODE_ARTIFACT_COMMENT_FAST_ACK
What

A second way to produce the quick "on it" reply to an artifact comment: instead of writing one freely, the model picks a numbered line from a fixed list and is told to output only its number — a single digit, nothing else, capped at 5 output tokens with a deadline. It runs only when CLAUDE_CODE_ARTIFACT_COMMENT_FAST_ACK_FIXED (or tengu_gorse_sill) is on, itself inside CLAUDE_CODE_ARTIFACT_COMMENT_FAST_ACK (or tengu_gorse_pylon). Both fall back to false, so two opt-ins are needed.

Details
  • Failure telemetry is separate from the free-form path: fast_ack_select_error, fast_ack_select_unparsed, fast_ack_select_timeout, fast_ack_select_threw
  • Ships with a permission shortcut, artifact_comment_fixed_ack_on_probe_verdict, that reuses a verdict from an earlier permission probe instead of asking again
  • Nothing in this build turns either gate on, so whether it runs is decided by server-side config or by setting the environment variables yourself
Usage
export CLAUDE_CODE_ARTIFACT_COMMENT_FAST_ACK=1
export CLAUDE_CODE_ARTIFACT_COMMENT_FAST_ACK_FIXED=1
Evidence

CLAUDE_CODE_ARTIFACT_COMMENT_FAST_ACK_FIXED

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

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.235 →