Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.290entry #154

Claude Code v2.1.290 ·

Claude Code as an MCP server runs each tool call in its own context

When serving tools over MCP, each tool call now runs in its own session context, and a slow workspace diff returns a structured error

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

Unclear What difference running each call in its own context makes for users is not clear.

What

MCP is a protocol that lets programs share tools. When Claude Code acts as an MCP server, so another program calls its tools, each tool call now runs in its own separate session context instead of the shared one.

When a workspace diff, the list of file changes, takes too long, the call now returns a structured error with the code workspace_diff_pending rather than failing outright.

Why

This is mostly internal rework. A program calling Claude Code's tools may now receive the workspace_diff_pending error code where it previously got a raw failure.

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 doubtWhat difference running each call in its own context makes for users is not clear.

See this entry in the whole of v2.1.290 →

Feedback