{"version":"2.1.323","anchor":"terminal-setup-and-artifact-message-tweaks","canonical_anchor":"terminal-setup-and-artifact-message-tweaks","heading":"Clearer reasons when an artifact is not published or an MCP server is disabled","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/terminal-setup-and-artifact-message-tweaks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Clearer reasons when an artifact is not published or an MCP server is disabled\n\nPublishing refusals now cover files on the artifact Claude can't see, and MCP enable or disable reports who holds a disabled server\n\n**What**\n\nAn artifact is something Claude publishes for you, made up of one or more files. When Claude Code refuses to publish, it previously only had wording about files Claude had to read before replacing them. There is now a third case:\n\n- Files already on the artifact that Claude cannot see: Claude Code says it was not published, and that Claude will not replace or remove those files unless you ask.\n\nSeparately, when you enable or disable an MCP server (a connection that gives Claude extra tools), Claude Code now reports who holds a disabled server.\n\n**Why**\n\nThe message tells you the real reason a publish was refused, so you know whether to ask Claude to replace those files.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}