{"version":"2.1.314","anchor":"artifacts-mcp-skip-reasons-gain-finer-detail-and-agent-cloud","canonical_anchor":"artifacts-mcp-skip-reasons-gain-finer-detail-and-agent-cloud","heading":"Clearer reasons when the artifacts tool server is not offered","tier":"internal","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/artifacts-mcp-skip-reasons-gain-finer-detail-and-agent-cloud","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Clearer reasons when the artifacts tool server is not offered\n\nWhen Claude Code skips the artifacts server, the recorded reason now names the cause, such as an admin policy or a deny rule\n\n**What**\n\nClaude Code can offer an artifacts server. This is an MCP server, a connector that plugs extra tools into Claude Code. When Claude Code decides not to offer it, it records a reason. That reason used to say only that the artifact tool was denied or switched off. It now also says what caused it:\n\n- `admin_policy` or `not_found`, for why the server was skipped\n\n- `tools_list` or `deny_rule`, for how a denied tool was blocked\n\n- an `agentCloudSession` field, recording whether the session runs as an agent in the cloud\n\n**Why**\n\nThese details are mostly diagnostics. They make it easier to work out why artifacts are missing from a session.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}