{"version":"2.1.236","anchor":"which-artifacts-you-are-watching-is-now-written-into-the-ses","canonical_anchor":"which-artifacts-you-are-watching-is-now-written-into-the-ses","heading":"Which Artifacts you are watching is now written into the session log","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/which-artifacts-you-are-watching-is-now-written-into-the-ses","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Which Artifacts you are watching is now written into the session log\n\nYour session log now remembers which Artifacts you were watching for comments.\n\n**What**\n\nThe set of Artifacts armed for automatic comment replies is saved with the session and read back when the session id changes, so a restored session knows what it was watching rather than starting blank.\n\n**Details**\n\n- Each record is keyed by Artifact slug and holds armed or stopped state, the time it was written, the title, and a marker when a background session owns it.\n- The list is capped and de-duplicated before being written.\n- Failures and rejected records are reported through the Artifact live-subscribe path with reasons `comment_monitor_intent_invalid`, `comment_monitor_intent_foreign`, `comment_monitor_intent_record_invalid` and `comment_monitor_intent_write_failed`.\n\n**Evidence**\n\n`comment_monitor_intent_write_failed`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}