{"version":"2.1.309","anchor":"artifact-rosterframe-urls-notification-filtered-by-publish","canonical_anchor":"artifact-rosterframe-urls-notification-filtered-by-publish","heading":"Artifact address updates are filtered by where the Artifact was published","tier":"internal","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/artifact-rosterframe-urls-notification-filtered-by-publish","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Artifact address updates are filtered by where the Artifact was published\n\nUpdates about Artifact frame addresses now apply one rule to Artifacts published here through MCP and another to the rest\n\n**Unclear.** The two rules that decide which Artifacts are kept or dropped are not known.\n\n**What**\n\nWhen an Artifact's details change, Claude Code may send a notice listing its frame addresses. It now decides which Artifacts to include using two separate rules: one for Artifacts marked as published from this session through MCP (a way of connecting Claude Code to outside tools), and one for all others. Before, a single check applied to every Artifact.\n\n**Why**\n\nThis changes which Artifacts get announced when their details change.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}