Repository navigation
Local MCP server spawned twice (duplicate process) on every Desktop restart #42190
Closed as duplicate
Description
Description
OpenCode Desktop starts two instances of the same local (stdio) MCP server every time it restarts, instead of one.
Confirmed with ps -eo pid,ppid,lstart,command: both server processes start at the identical timestamp, both parented under the same "OpenCode Helper (Utility)" process.
Ruled out:
- Config duplication - only one entry for the server exists in opencode.json
- Multiple windows - only one window-state file exists, single window open
Ends up with two idle duplicate server processes after every restart.
Plugins
No response
OpenCode version
1.15.13
Steps to reproduce
- Configure any local (stdio) MCP server in opencode.json
- Launch or restart OpenCode Desktop
- Run
ps -eo pid,ppid,lstart,command | grep <your-server-command> - See two processes with identical start times, same parent PID
Screenshot and/or share link
No response
Operating System
macOS 26.5.2
Terminal
N/A (Desktop app)
Reacted by bacca87
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Aug 13, 2026
This issue might be a duplicate of existing issues. Please check:
mapix-etnc commentedon Aug 27, 2026
Confirmed on Linux/OpenCode Desktop with one Desktop utility worker and no duplicate MCP configuration entries.
Observed 18 local MCP server instances for 9 enabled local MCP server identities: every server starts exactly twice in two waves roughly four seconds apart. This affects unrelated local stdio MCPs, not only one server implementation:
Both waves are descendants of the same long-running Desktop utility worker and each duplicate has its own stdio socket pair. They are not created by
opencode mcp listor a transient CLI diagnostic process.This materially affects reliability for stateful local MCP servers. We observed 60-second tool-call timeouts after repeated otherwise-successful Google Workspace operations. Correlation logging showed normal credential lookup and API calls for successful requests; the duplicated process topology is the common host-side fault observed across every local MCP server.
Expected: one child process tree per enabled local MCP configuration per Desktop worker.
Additional related issues: #31554, #41331, #26714.
neriousy commentedon Oct 1, 2026
Closing as a duplicate of #31554. Same bug: local MCP servers are spawned twice on startup. Tracking in #31554.