Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.317 ·

Some web-based MCP servers no longer get disconnected after three fatal errors

Behind a switch that defaults to off, some HTTP MCP servers no longer count fatal connection errors toward the three-error disconnect

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

Unclear It is not stated which server addresses pass the URL check, so it is unclear which HTTP servers this covers.

What

MCP servers are outside programs that give Claude Code extra tools. Some of them are reached over the web, as type http. Claude Code counts the connection errors it treats as fatal. After three in a row, it closes the connection with the message 'max consecutive terminal errors'.

Those errors no longer add to the count when all three of these are true:

  • The server is type http.
  • The server's address passes a check on its URL.
  • The tengu_snug_mist_enabled switch is on.

When all three hold, the three-error limit never closes the server's connection. The switch is off unless it is turned on remotely. The most recent reading was taken before this release. In that reading, the flag server returned the switch as on, both for this site's account and for an anonymous baseline, and it had switched on since the reading before that.

Why

An unreliable HTTP server that used to be dropped after three fatal errors can stay connected. This applies only to servers whose addresses match the check.

Read from
Feature flag
tengu_snug_mist_enabled Off by default, switched on for this account

The shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.

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

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.

tengu_mcp_legacy_sse_fallback Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.317: 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.317. It isn't a statement about your account. What a flag value here can and cannot tell you

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 which server addresses pass the URL check, so it is unclear which HTTP servers this covers.
The name it cites is new in this buildNew in this build: tengu_snug_mist_enabled

See this entry in the whole of v2.1.317 →

Feedback