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.265 ·

MCP prewait can now target specific remote servers by name

MCP prewait gains a waitRemoteServerNames option to block on named remote MCP servers, not just local ones

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.265,
Group of 2 Under the hood No documentation found

MCP prewait gains a waitRemoteServerNames option to block on named remote MCP servers, not just local ones

What

The MCP client prewait step, which waits for MCP clients before a turn is dispatched, now accepts a waitRemoteServerNames option alongside the existing localOnly and waitForDeferrable options. In headless mode, this lets the prewait gate also block on specific named non-local MCP servers, not just local-only ones.

New telemetry fields remoteByNamePendingBefore/remoteByNamePendingAfter are reported on the headless MCP prewait telemetry event.

Why

This lets Claude Code wait for particular remote MCP servers it actually depends on for a turn, rather than only being able to wait for local servers or none at all.

Read from
Names in the bundlewaitRemoteServerNames
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 waitRemoteServerNames actually does with the server names it's passed isn't stated.

See this entry in the whole of v2.1.265 →

Feedback