{"version":"2.1.304","anchor":"artifacts-panel-mcp-published-artifacts-are-checked-before","canonical_anchor":"artifacts-panel-mcp-published-artifacts-are-checked-before","heading":"Artifacts published through MCP are checked before they open","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/artifacts-panel-mcp-published-artifacts-are-checked-before","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Artifacts published through MCP are checked before they open\n\nOpening an artifact published through MCP now runs a check first, and a second open is refused until that check finishes\n\n**What**\n\nIn the artifacts panel, opening an artifact that was published through MCP (Model Context Protocol, a way to connect Claude Code to outside tools and servers) used to open it straight away. Claude Code now checks it first and shows \"Checking the artifact before opening it\u2026\" while it does. If you try to open another one before the check finishes, it answers \"Still checking the last artifact you chose.\"\n\nWhen you are asked to confirm deleting an artifact, the arrow keys now do nothing.\n\n**Why**\n\nYou get a short wait and a visible check before such artifacts open. Ignoring arrow keys on the delete prompt stops them from moving the selection by accident while you confirm.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}