Unclear Whether the legacy HTTP+SSE fallback path is switched on for any account is not known.
MCP servers are outside programs that give Claude extra tools. Claude Code now handles two reconnect failures more carefully:
- Legacy HTTP+SSE fallback: when Claude Code retries a server using this older connection method, it first releases the earlier connection state and puts it back if the fallback fails.
- Step-up reauthentication: when a server asks you to sign in again with more access and the new connection is not accepted in place of the old one, the reconnect now fails with
adopt_refusedand is thrown away. Before, that result was ignored.
A failed reconnect is now less likely to leave a server half-connected or in a mixed state.
tengu_mcp_legacy_sse_fallback Not enough to sayNothing 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.290: 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.290. It isn't a statement about your account. What a flag value here can and cannot tell you
Whether the legacy HTTP+SSE fallback path is switched on for any account is not known.