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

A second, fixed-menu artifact fast-acknowledgment selector exists behind two gates that both default off

A second fast-ack mode lets Claude pick a fixed numbered acknowledgment instead of writing one, off behind two gates

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

Alongside the existing free-form fast-acknowledgment composer for artifact comment threads, a new selector mode asks the model to pick one numbered acknowledgment from a fixed list, instructed to output only its number. It runs with a 5-token output cap, a deadline, and its own failure telemetry (fast_ack_select_error, fast_ack_select_unparsed, fast_ack_select_timeout, fast_ack_select_threw). It also adds a permission shortcut that can reuse a prior probe verdict instead of re-asking.

This selector only runs when CLAUDE_CODE_ARTIFACT_COMMENT_FAST_ACK_FIXED (or its underlying gate) is true, and that check is nested inside the pre-existing fast-ack gate that governs the original composer. Both default to false, so turning this on requires opting in to both.

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

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

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

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_gorse_sill

See this entry in the whole of v2.1.235 →

Feedback