MCP connection code references two settings controlling connect-timeout retries and legacy SSE fallback
MCP (Model Context Protocol) connection handling now references two settings: tengu_mcp_connect_timeout_retry, which controls whether a connection timeout is treated as something worth retrying, and tengu_mcp_legacy_sse_fallback, which controls whether Claude Code falls back to the older HTTP+SSE (Server-Sent Events) connection style when a server rejects its initial connection request.
These give Claude Code more resilient fallback behavior when an MCP server times out or doesn't support the newer connection method, though no reading of either setting's current value is available yet for this account.
tengu_mcp_connect_timeout_retry 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.274: 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.
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.274: 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.274. It isn't a statement about your account. What a flag value here can and cannot tell you