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

Claude Code v2.1.302 ·

MCP tasks can keep being checked slowly after Claude Code gives up on them

A long MCP task that would have failed can now be let go but still checked slowly, and picked up again when its server answers

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

Unclear Whether this mode is on by default is not settled.

What

An MCP server is a separate program that gives Claude Code extra tools, and some of its work runs as long tasks that Claude Code checks on (polls) until they finish. Before, any of the following ended the task as failed:

  • the server is not configured
  • an identity mismatch
  • an era mismatch
  • the server needs you to sign in
  • reconnecting failed
  • the task's time limit expired
  • the server no longer offers the needed capability

In a new mode, Claude Code instead records the outcome, stops holding the process open for the task, and keeps checking on it at a slower rate. When the server answers again, the task is picked up and checked at the server's own pace.

Why

Long-running MCP tasks can survive a server outage or sign-in problem instead of being marked failed.

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 doubtWhether this mode is on by default is not settled.

See this entry in the whole of v2.1.302 →

Feedback