Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.308 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.307 ·

Turning Artifacts off now disconnects the Artifacts MCP server in remote sessions

In Claude Code Remote sessions, switching Artifacts off in settings now leaves out MCP servers that connect to the Artifacts server

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

What

MCP servers are outside services that give Claude extra tools. When Artifacts are turned off in Claude Code settings, MCP server entries whose address points at Claude Code Remote's Artifacts server are now left out and not connected.

  • This only applies when CLAUDE_CODE_REMOTE is set, meaning the session runs remotely.
  • The skipped server shows the message: "Ignored: Artifacts are turned off in Claude Code settings, so this server, which connects to Artifacts, is not connected".
  • The log records how many servers were left out, under '[MCP] Artifacts are switched off in settings'.
  • The filtering sits behind a new remotely controlled switch, tengu_clever_yeti. Nothing has been read about whether it is turned on.

Why

In remote sessions the Artifacts setting can now actually remove the route to Artifacts, rather than leaving its MCP server connected, and the message tells you why the server is not there.

Read from
Names in the bundleCLAUDE_CODE_REMOTE
What the documentation says

See this entry in the whole of v2.1.307 →

Feedback