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

Claude Code v2.1.299 ·

Artifact requests can travel as MCP tool calls

Some artifact requests, such as pinning and listing, can be sent as MCP tool calls through a new relay, with separate tracking for each kind

Group of 2 Nothing to try yet In Development
JSON All of v2.1.299
Nothing to try yetTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
In DevelopmentKind: in v2.1.299,
In DevelopmentSection of the release

What

Artifacts are items Claude Code can create, pin and publish. Requests about them have gone to /api/frame. A new relay can carry some of these requests as MCP tools/call requests instead. MCP (Model Context Protocol) is the standard Claude Code uses to talk to outside tool servers.

  • Pinning or unpinning an artifact goes as pin_artifact or unpin_artifact.
  • Deploying (deploy/direct) goes as publish_version.
  • Listing frames and listing types go as list_artifacts and list_types.
  • The relay is skipped inside remote sessions, and its fallback is off.
  • Tracking for the relay is now split by kind of request (listing, pin, publish and tool listing) instead of being one combined record.

The relay sits behind the switch tengu_cobalt_plinth_teasel. Nothing has been read about that switch, so it is not known whether the relay is in use.

Why

The relay changes how artifact requests travel. If it is turned on, pinning, publishing and listing artifacts would run over MCP instead of direct requests.

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_cobalt_plinth_teasel

See this entry in the whole of v2.1.299 →

Feedback