{"version":"2.1.307","anchor":"mcp-connection-timeout-now-measured-by-an-injectable-clock","canonical_anchor":"mcp-connection-timeout-now-measured-by-an-injectable-clock","heading":"MCP connection timeouts now measure time with a clock that tracks awake time","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/mcp-connection-timeout-now-measured-by-an-injectable-clock","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### MCP connection timeouts now measure time with a clock that tracks awake time\n\nTimeouts when connecting to MCP servers now use a clock that keeps track of time the computer spends awake, not plain wall-clock time\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. When Claude Code connects to one, it gives up after a time limit. That limit is now measured with a clock that keeps track of how long the computer has been awake, instead of the ordinary system time.\n\nTwo smaller changes come with it. A tool call that fails to send is now recorded as a request that never ran, rather than one that was answered. The tracking of sent tool calls has also been moved into a single shared piece of code.\n\n**Why**\n\nThis is meant to stop a connection from timing out only because the computer went to sleep while it was connecting, for example when you close a laptop lid.\n\n- Flag `tengu_mcp_legacy_sse_fallback`: Not enough to say (read for one account on one subscription tier against v2.1.307; this account: no value returned, anonymous baseline: no value returned, compiled default: 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.\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}