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.292entry #98

Claude Code v2.1.292 ·

Slow resource listings no longer hold up MCP tools on HTTP and SSE servers

After connecting to an HTTP or SSE MCP server, Claude Code can now register its tools without waiting for its resource listing to finish

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

Unclear It is not stated what decides whether Claude Code skips waiting for the resource listing.

What

MCP (Model Context Protocol) servers are external programs or services that give Claude Code extra tools and data. After connecting to one, Claude Code asks what it offers. It now does this in two separate groups instead of one:

  • tools, commands and skills
  • resources and resource templates

For servers connected over HTTP or SSE (ways of reaching a server over the network) that offer resources, Claude Code can now skip waiting for the resource group under some conditions and ignore any errors from it. Tools can then be registered without waiting on a slow resource listing. Before, everything was fetched together and Claude Code waited for all of it.

The switch for protocol version negotiation on stdio MCP servers (servers that run as a local process) was read as on for this site's account and for an anonymous baseline, having switched on since the previous reading.

Why

MCP servers with slow resource listings should make their tools available sooner after startup.

Read from
Feature flag
tengu_mcp_protocol_negotiation_stdio On for this account, and not off by default

The flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.

This account: on · anonymous baseline: on · compiled default in v2.1.292: on

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.292. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns on for tengu_mcp_protocol_negotiation_stdio, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns off for tengu_mcp_protocol_negotiation_stdio, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

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 doubtIt is not stated what decides whether Claude Code skips waiting for the resource listing.

See this entry in the whole of v2.1.292 →

Feedback