Bookkeeping that tracks Claude's own posted comment replies is present but entirely switched off.
Reply-id tracking and a stronger duplicate guard for comment threads sit behind a flag with fallback off.
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: 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's wrong with this entry?
Supporting machinery for threading comment replies is present and inert: the reply POST body can carry a continues_reply_id, posted reply ids are kept in a size-capped set, and the duplicate guard consults that set instead of trusting the server's acknowledge_duplicate alone. Every branch sits behind tengu_medlar_quoin with fallback off.
- Reply records became account-epoch aware; a reply recorded under a different account epoch is ignored.
continues_reply_id_malformedandfollow_up_marker_unconsumedonly fire once the gate is on.
continues_reply_id_malformed
Strings lifted out of the shipped bundle, so the claim above can be checked against them.