Unclear The flag server returned off for this feature for both this site's account and the anonymous baseline, and no reading has been taken under this release yet, so whether it is enabled anywhere currently is unclear.
Building on the duplicate-reply guard for artifact comment threads, replies can now declare which of Claude's own earlier replies they follow up on via a new continues_reply_id field in the POST body. Posted reply IDs are remembered in a capped set, and the existing duplicate guard now checks that set rather than relying solely on acknowledge_duplicate. Reply bookkeeping is also account-epoch aware, so a reply recorded under a different account epoch is ignored. New telemetry reasons continues_reply_id_malformed and follow_up_marker_unconsumed fire only on this new path.
tengu_medlar_quoin Not enough to sayNothing 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: 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
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.
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.
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.
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.
The flag server returned off for this feature for both this site's account and the anonymous baseline, and no reading has been taken under…
New in this build: tengu_medlar_quoin