{"version":"2.1.311","anchor":"remotesession-id-check-dropped-from-artifacts-mcp-entry-gat","canonical_anchor":"remotesession-id-check-dropped-from-artifacts-mcp-entry-gat","heading":"Artifacts MCP setup no longer skipped outright in remote sessions","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/remotesession-id-check-dropped-from-artifacts-mcp-entry-gat","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Artifacts MCP setup no longer skipped outright in remote sessions\n\nClaude Code no longer stops early on the artifacts MCP setup when `CLAUDE_CODE_REMOTE` or `CLAUDE_CODE_REMOTE_SESSION_ID` is set\n\n**Unclear.** It is not clear whether remote sessions now actually get the artifacts MCP entry, or whether the remaining checks still exclude them.\n\n**What**\n\nClaude Code has a step that picks a local entry for an artifacts MCP server (MCP servers are outside programs that give Claude extra tools). Before, this step gave up straight away when the environment variable `CLAUDE_CODE_REMOTE` or `CLAUDE_CODE_REMOTE_SESSION_ID` was set, meaning the session was running remotely. That early exit has been removed. The step's other checks remain.\n\n**Why**\n\nRemote sessions are no longer ruled out by that one test, so they may now reach the artifacts MCP setup.\n\n- Area: Artifacts\n- Names: `CLAUDE_CODE_REMOTE`, `CLAUDE_CODE_REMOTE_SESSION_ID`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}