{"version":"2.1.315","anchor":"artifacts-mcp-entry-watch-started-in-sessioncontroller","canonical_anchor":"artifacts-mcp-entry-watch-started-in-sessioncontroller","heading":"Sessions can now watch for an Artifacts MCP entry when they start","tier":"internal","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/artifacts-mcp-entry-watch-started-in-sessioncontroller","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Sessions can now watch for an Artifacts MCP entry when they start\n\nWhen a session starts, Claude Code now starts an optional watch for an Artifacts MCP entry and reports it if that watch fails\n\n**Unclear.** Whether the part of Claude Code that runs this watch is included in this build is not known.\n\n**What**\n\nWhen a session starts, Claude Code now starts an optional watch for an Artifacts MCP entry. MCP servers are add-ons that give Claude extra tools. If starting the watch fails, the error is caught and reported, and the session carries on.\n\n**Why**\n\nThis is part of work on artifacts. A failure in it does not stop the session from starting.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}