Headless runs decide more carefully whether to wait for MCP servers before starting.
What's wrong with this entry?
The decision about whether headless startup waits for MCP servers moved into two dedicated helpers.
- one helper reports whether an explicit MCP config asks the run to wait, returning true if any configured server is not of type
sdk - the other computes a
deadlineMsand alocalOnlyflag localOnlyis set for SDK-URL sessions that are notCLAUDE_CODE_ENVIRONMENT_KIND === "bridge"and not in coordinator mode
explicitMcpConfigRequestsWait
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.248
MCP errors sent to Remote Control clients are filtered to a fixed list
Both mention environment kind
-
v2.1.248
get_settings is refused on remote connections
Both mention environment kind
-
v2.1.248
SDK stream transport can re-read auth headers, except in managed environments
Both mention environment kind