{"version":"2.1.269","anchor":"new-added-cost-timestamp-field-on-comment-thread-framing","canonical_anchor":"new-added-cost-timestamp-field-on-comment-thread-framing","heading":"New added-cost timestamp field on comment thread framing","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-added-cost-timestamp-field-on-comment-thread-framing","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### New added-cost timestamp field on comment thread framing\n\nNew readAtMs timestamp tracks when an artifact comment thread was last read\n\n**Unclear.** The finding does not confirm exactly how readAtMs is used, only that it is likely for staleness or elision decisions.\n\n**What**\n\nA new small data structure combines a `commentsEmpty` flag with a `readAtMs` timestamp (validated to be a positive number within a plausible date range) for artifact comment threads.\n\n**Why**\n\nThis timestamp likely lets Claude Code know when a comment thread's contents were last read, which can inform decisions about whether comments are stale or should be dropped from context.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}