Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.273 ·

MCP connector prewait logic now distinguishes the first command from later wakes

MCP connector startup waiting now behaves differently on the first command versus later 'wakes', with a new relay-marked flag

TierUnder the hoodhow much it should matter to you
Useful2my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaMCPwhat it touches
KindInternal Changesin v2.1.273,
Group of 2 Under the hood

MCP connector startup waiting now behaves differently on the first command versus later 'wakes', with a new relay-marked flag

What

The 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.

  • On the first command, it still uses the existing deadline and local-only settings.
  • 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.
  • 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.

Why

This 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.

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 doubtWhat effect this has on observable connection behavior is not stated.

See this entry in the whole of v2.1.273 →

Feedback