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
Fix: Handle network errors in instruction fetch gracefully
Wrap the fetch() call in fetchLatestInstructions with a try-catch block
to handle transport-level errors (DNS failure, connection refused,
network timeout) that cause fetch to throw rather than returning a
Response object.
Previously, these errors would propagate unhandled through getInstructions
and newMcpServer, causing the entire MCP server to fail to handle
requests in HTTP mode, or preventing server startup in stdio mode.
Now, network errors are caught and logged, and the server falls back to
the default instructions, matching the existing behavior for HTTP-level
errors (!response.ok).
0 commit comments