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
Thanks for the report. We couldn't investigate from the screenshot alone, and MCP connection handling has changed a lot since v1.0.7 — for example, remote MCP connections retry on transient network failures (v1.0.25), MCP failure warnings include the server's stderr output (v1.0.42), and MCP tools recover more reliably from transient connection failures (v1.0.88). Please update to the latest version (v1.0.103) with copilot update or your package manager; if you still see the circuit-breaker error, open a new issue with your CLI version, the exact error text, your MCP server configuration (secrets redacted), whether it only happens with --resume, and debug logs (--log-level all --log-dir <dir>).
Triaged as part of a Copilot SDK backlog review, with help from GitHub Copilot.
Activity
patniko commentedon Oct 26, 2026
Thanks for the report. We couldn't investigate from the screenshot alone, and MCP connection handling has changed a lot since v1.0.7 — for example, remote MCP connections retry on transient network failures (v1.0.25), MCP failure warnings include the server's stderr output (v1.0.42), and MCP tools recover more reliably from transient connection failures (v1.0.88). Please update to the latest version (v1.0.103) with
copilot updateor your package manager; if you still see the circuit-breaker error, open a new issue with your CLI version, the exact error text, your MCP server configuration (secrets redacted), whether it only happens with--resume, and debug logs (--log-level all --log-dir <dir>).Triaged as part of a Copilot SDK backlog review, with help from GitHub Copilot.