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
HomeReleasesv2.1.300entry #76

Claude Code v2.1.300 ·

MCP task endings survive a restart, and there are new failure reasons

MCP task endings are saved before notifying so a restart keeps them, with new needs_sign_in and answered_with_errors ending reasons

Group of 2 You'll notice Improvements
JSON All of v2.1.300
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.300,
ImprovementsSection of the release

What

An MCP task is a long-running job run by an MCP server, an outside program that gives Claude Code extra tools. How these tasks end has changed:

  • When a task finishes, its ending is now saved to a separate file before the notification about it is sent, so a restart does not lose it. If saving fails, Claude Code reports that it "could not save the ending of task".
  • The notification now carries a run ID and the origin of the task.
  • The list of ending reasons gains needs_sign_in and answered_with_errors. Before, a reconnect failure could only end as reconnect_failed or ttl_expired.
  • A server that asks you to sign in while Claude Code is checking on a task is now handled separately from a lost connection.

Why

Long-running MCP tasks are less likely to vanish when Claude Code restarts. When one fails, the reason is more specific, so you can tell "needs sign-in" apart from a dropped connection.

See this entry in the whole of v2.1.300 →

Feedback