You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Claude chat shows system:init as an error card when an MCP server failed to connect #28856
When any configured MCP server fails to connect, a Claude native chat session starts with a red claude · message:system:init error card, whose disclosure dumps the raw init frame (tool list, MCP servers, plugins, ...).
Cause:classifyProviderFrame runs hasProviderError over the whole payload before consulting the catalog. Claude's system:init lists every MCP server with its connect status, so one entry like { "name": "marimo", "status": "failed" } matches the status → fail* rule and promotes the catalogued status-chrome init frame to error-surface.
Repro: configure an MCP server that cannot connect (e.g. a URL nothing listens on), start a Claude chat, send any message.
Expected: no raw-frame card for init (it is session inventory, not an operation outcome), but a readable warning naming the MCP server(s) that failed to connect and how to find out why.
Activity
feat(native-chat): warn once per session when a Claude MCP server fai…
paul-vd commentedon Oct 15, 2026
duplicate of #25477?