In bridge mode, unknown MCP errors are collapsed to "connection failed" for remote clients.
What's wrong with this entry?
In bridge mode (CLAUDE_CODE_ENVIRONMENT_KIND=bridge), the per-server error map returned for an MCP server update now only passes through known reasons such as "Blocked by enterprise policy (allowedMcpServers/deniedMcpServers)", "Ignored in hermetic mode (not declared in user config)" and "Ignored in a Remote Control session: MCP servers are loaded only from the verified startup config on this machine". Anything else becomes "connection failed". Outside bridge mode the original text is still returned.
- Two error shapes are additionally allowed by pattern:
Server status: <status>andServer not found: <name>(name limited to 64 characters of letters, digits, space, underscore, dot and hyphen). - Server-name keys are sanitized too and duplicates get a
#2suffix.
Ignored in a Remote Control session: MCP servers are loaded only from the verified startup config on this machine
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.221
Headless MCP startup wait reworked
Both mention environment kind
-
v2.1.221
CCR client can adopt refreshed auth pushed over the event stream
Both mention environment kind
-
v2.1.221
Web sessions can adopt refreshed credentials from the heartbeat
Both mention environment kind