[FEATURE]: Double click to retry on MCP Error #53780

Activity

1. opencode-agent commented on Oct 7, 2026

   

   opencode-agentbot

   on Oct 7, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the suggestion, @manoharreddyporeddy! In short: when an MCP tool call or server shows an error (as with Playwright MCP), you'd like to double-click it to reconnect and retry, instead of recovering by hand. Maintainers will consider it.

   In the meantime, on OpenCode v2 you can reconnect a failed server from /mcps. Recent v2 builds also retry short-lived MCP connection failures automatically, so if you're on 1.x, upgrading may cut down how often you see this.

   These open issues and PR are about recovering from MCP failures automatically, which overlaps with what you're asking for:

   • mcp: remote MCP servers that fail once are never retried until service restart #52237: remote MCP servers that fail once are never retried until restart
   • mcp: no reconnect after network change/socket reset; stale Error until server process is killed #52564: no reconnect after a network change or socket reset; the Error stays until the server process is killed
   • mcp: local server not restarted after transport error #53226: local MCP server not restarted after a transport error
   • [FEATURE] Official MCP warm-up / pre-spawn mechanism (+ reconnect path) — all local MCPs marked failed at session start when many cold-start concurrently #48743: MCP warm-up and a reconnect path when local MCPs fail at session start
   • fix(mcp): reconnect dropped servers with backoff #52943 (PR): reconnect dropped MCP servers with backoff
2. github-actions

   assigned

   Brendonovich

   on Oct 7, 2026