Source Intelligence
Follow Discord

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

Replies to artifact comments can say which earlier reply they continue

Not switched on
Useful1 Signal4
Artifacts

Claude's replies on artifact comment threads could link back to its earlier reply, but that's off.

Threaded comment replies are wired up but sit behind a server flag that falls back to off.

Feature flag
tengu_medlar_quoin 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: off · anonymous baseline: on · 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

What

A reply Claude posts to a comment thread can now declare the id of its own previous reply in that thread, so follow-ups are threaded rather than looking like fresh answers. It is off unless the server turns on tengu_medlar_quoin, whose fallback is off, so replies post exactly as before.

Details
  • The id is taken from the agent's own last posted reply, with an account-epoch check so an id minted under a different account is not reused.
  • The "already answered" duplicate guard also consults the set of reply ids this session posted.
  • Two telemetry reasons exist for the gated path: continues_reply_id_malformed and follow_up_marker_unconsumed.
Evidence

continues_reply_id

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