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.312 ·

Artifacts tool setup and publishing checks change for desktop and Cowork

Artifacts can run from a local server, CLAUDE_CODE_HOST_GUARDS_ARTIFACTS_MCP stops the desktop skip, and publishing obeys Read rules

You'll notice Improvements
JSON All of v2.1.312
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.312,
ImprovementsSection of the release
What

The Artifacts tool is provided through MCP (Model Context Protocol, the way Claude Code connects to extra tool servers). How Claude Code sets it up and checks publishing has changed:

  • It can now run the tool from a local server on your machine instead of Anthropic's web endpoint, and passes it the directories your Read permission rules cover.
  • Setting the environment variable CLAUDE_CODE_HOST_GUARDS_ARTIFACTS_MCP lets sessions running inside the desktop app keep the tool instead of skipping it, as they did before.
  • The tool is now skipped for a desktop share action, in place of the old skip for evaluation runs.
  • Publishing files is refused when one of your Read rules forbids reading a file being sent.
  • In Cowork, a publish that would need an approval card is refused, because no one there can answer the card.
Why

This changes whether desktop and Cowork sessions get the Artifacts tool, and makes publishing respect the same Read rules as the rest of Claude Code.

See this entry in the whole of v2.1.312 →

Feedback