Follow Discord
Sweep 27 Oct 2026 · 19:04Z Build v2.1.312 531 read Stable v2.1.308 Latest v2.1.312 Next v2.1.312 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.311 ·

Artifacts MCP setup no longer skipped outright in remote sessions

Claude Code no longer stops early on the artifacts MCP setup when CLAUDE_CODE_REMOTE or CLAUDE_CODE_REMOTE_SESSION_ID is set

You'll notice Improvements
JSON All of v2.1.311
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
ImprovementsKind: in v2.1.311,
ImprovementsSection of the release

Unclear It is not clear whether remote sessions now actually get the artifacts MCP entry, or whether the remaining checks still exclude them.

What

Claude 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.

Why

Remote sessions are no longer ruled out by that one test, so they may now reach the artifacts MCP setup.

Read from
What the documentation says
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear whether remote sessions now actually get the artifacts MCP entry, or whether the remaining checks still exclude them.

See this entry in the whole of v2.1.311 →

Feedback