Our earlier post on Claude Code 2.1.325 covered the changes that can leave an unattended run waiting for permission. Version 2.1.330 was the latest release on npm on 22 November 2026, five releases on, and this follow-up is about a different quiet failure: an agent session that starts normally but has no tools from an MCP (Model Context Protocol) server, or a tool call that waits instead of failing.
For someone at the keyboard, that's a puzzle to solve. For a job nobody is watching, it can look exactly like a quiet day. Below are three open issues on Claude Code's public tracker that end this way, and two fixes in the latest releases that close related gaps. The issues are reports from users, opened between August and 19 November 2026; each is given with its own date.
Three open issues
1. The server starts twice, and the real connection loses (#85895)
Opened 11 August 2026, labelled reproduced and platform:linux. The reporter found that, on one of their Linux machines, every launch started the project's .mcp.json stdio server twice: once immediately, outside the part of Claude Code that manages MCP connections, and once about two seconds later through it. That only breaks something because of how their server behaves:
"Our stdio server's backend enforces one connection per client identity, so the second (legitimate) connection is rejected and the session comes up with zero tools (
Failed to fetch tools: Not connected)."
The condition matters: the consequence needs a server that allows only one connection per client identity, which is the reporter's setup, not a general property of MCP servers. A server that accepts several connections would still be started twice, but nothing would visibly fail. The report was made against versions 2.1.226 and 2.1.227.
2. A 401 that never becomes an error (#111192)
Opened 19 November 2026 and not labelled reproduced, so treat it as a report rather than a confirmed bug. It concerns a remote MCP server over Streamable HTTP with OAuth that answers 401 Unauthorized with a WWW-Authenticate: Bearer error="invalid_token" challenge, which in the reporter's steps happens once the OAuth access token expires. The reporter's description of what happens next:
Instead, the tool call hangs silently until the 120s idle timeout fires, gets backgrounded, and eventually fails with "Connection closed" or "no response for 1800s."
The workaround they give is manual: "Run /mcp in Claude Code to manually reconnect the MCP server session."
3. An expired sign-in replayed forever (#84614)
Opened 6 August 2026 and labelled reproduced; a collaborator on the repository reproduced the core of it in a comment. Some authorization servers delete the client registrations that MCP clients create for themselves. When that happens, Claude Code keeps reusing the cached registration, the rejection (Unrecognized client_id) appears in the browser rather than in Claude Code, and:
"Every retry replays the same dead
client_id. No amount of/mcpre-authentication recovers."
The issue describes a manual workaround, but it means editing Claude Code's stored credentials, which hold every server's sign-in. Read the issue in full before trying it.
This one is easy to confuse with a fix in 2.1.329 that sounds similar but covers a different signature, a registration the server reports as retired with HTTP 410:
"Fixed
claude mcp loginand/mcpsaying a service doesn't accept sign-ins from Claude Code when the service's client registration had been retired (HTTP 410 Gone)"
That fix doesn't close #84614, which was still open on 22 November 2026.
Two fixes that are already out
These are quoted whole from the changelog, with the version each one is in.
2.1.329:
"Fixed Claude not being told that a connected MCP server's tools could not be loaded, and taking it for a server with no tools, in sessions with tool search"
So in sessions with tool search, "no tools" could itself be a reporting error: the tools existed but failed to load, and Claude was not told. This is fixed from 2.1.329; the changelog limits it to sessions with tool search.
2.1.330:
"Fixed an MCP server that subagents declare being shut down when one of them finished, while other subagents or the session were still using it"
This one is specific to setups where subagents declare their own MCP servers: one subagent finishing could take the server away from the others mid-run.
Also worth knowing if you run agents unattended
- 2.1.329: “Added a "Server message" row to a server's page in
/mcpthat shows the JSON-RPC error message of a remote HTTP MCP server that refuses the connection” - 2.1.329: "Fixed
~/.claude.jsonsometimes being reset to defaults when a network stall or file lock made it unreadable and cleared during a save" - 2.1.330: "Fixed changes to user settings being lost when several Claude Code processes saved them at the same time"
How to check your own setup
- Update first. The two fixes above are in 2.1.329 and 2.1.330. Check what version your unattended jobs actually run, not just the one on your own machine.
- Check for a double start. If you use a project stdio server, list its processes during a session (for example with
ps) and look for two instances started by the sameclaudeprocess. Two instances under one parent is the signature in #85895. If eachclaudeprocess has one, you're not seeing it. Either way, it only breaks things if your server refuses a second connection. - Treat "no tools" as a failure. If a job expects tools from an MCP server, have it check that the tools are there before it starts work, and stop loudly if they aren't.
- Put a time limit on tool calls in jobs nobody watches. A call that waits on a rejected token doesn't error; a timeout or an alert on unusually long runs turns it into one.
- Know where sign-in errors show up. With OAuth servers, the error can appear in a browser tab rather than in Claude Code, and
/mcpis where to look first.
Sources: Anthropic, Claude Code changelog, 2.1.329 and 2.1.330 sections; npm registry, version 2.1.330 as latest; GitHub issues #85895, #111192 and #84614 on anthropics/claude-code. All read 22 November 2026. The changelog does not carry release dates.

