{"version":"2.1.273","anchor":"mcp-prewait-now-distinguishes-first-command-from-later-wake","canonical_anchor":"mcp-prewait-now-distinguishes-first-command-from-later-wake","heading":"MCP connector prewait logic now distinguishes the first command from later wakes","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/mcp-prewait-now-distinguishes-first-command-from-later-wake","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### MCP connector prewait logic now distinguishes the first command from later wakes\n\nMCP connector startup waiting now behaves differently on the first command versus later 'wakes', with a new relay-marked flag\n\n**What**\n\nThe waiting logic Claude Code uses before running MCP (Model Context Protocol) tool calls or slash commands, which decides how long to wait for connectors to be ready and whether to only use local ones, has been reworked for coordinator-mode connections.\n\n- On the first command, it still uses the existing deadline and local-only settings.\n\n- On later 'wakes' (i.e. once a first command has already been taken), it can instead use a separate `mcpPrewait.laterWakes` configuration for the deadline and local-only behavior.\n\n- A new `relayMarked` flag and a deferred-wake payload replace the old single `waitRemoteServerNames` field, and the fresh-wait deadline is now computed based on whether the session is relay-marked.\n\n**Why**\n\nThis lets Claude Code apply different, more appropriate waiting behavior for connectors depending on whether it's the very first command in a session or a later resumption, reducing unnecessary waiting or premature local-only fallback.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}