{"version":"2.1.235","anchor":"artifact-comment-follow-up-threading-continues-reply-id","canonical_anchor":"artifact-comment-follow-up-threading-continues-reply-id","heading":"Artifact comment follow-up threading ( continues_reply_id ) is wired but gated off by tengu_medlar_quoin","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/artifact-comment-follow-up-threading-continues-reply-id","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### Artifact comment follow-up threading (`continues_reply_id`) is wired but gated off by `tengu_medlar_quoin`\n\nArtifact comment replies can now thread onto a prior Claude reply via continues_reply_id, but the feature is off by default\n\n**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.\n\nBuilding 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.\n\n- Flag `tengu_medlar_quoin`: Not enough to say (read for one account on one subscription tier against v2.1.235; this account: off, anonymous baseline: on, compiled default: off)\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}