Windows Desktop starts duplicate MCP processes at idle, causing multi-GB RAM usage

What happened

On Windows, OpenCode Desktop appears to start many duplicate local MCP server processes when the desktop app opens with several existing tabs/projects restored. This happens while idle, before sending a new request.

The duplication is much larger than expected: instead of one process per configured local MCP server, the same servers appeared roughly 10 times each. This caused several gigabytes of RAM usage immediately after opening the app.

Environment

• OpenCode Desktop: 1.18.25
• OS: Windows
• Multiple existing tabs/projects restored on startup
• No active model request when the process snapshot was taken

Observed process breakdown

In one idle snapshot, the OpenCode embedded NodeService owned approximately:

• 10 GSD MCP server processes
• 10 OpenViking MCP proxy processes
• 10 Dida365 MCP server processes
• 10 grep-app MCP server processes
• 10 CodeGraph server processes
• 20 cmd.exe wrappers
• 55 conhost.exe processes

The OpenCode process tree contained about 147 descendants. Across the system, six OpenCode desktop processes were present. The OpenCode-owned Node workers used roughly 4 GB of working memory, with the OpenCode desktop/WebView processes adding several more GB.

The duplication was visible even though the app was idle. Some CodeGraph processes corresponded to previously opened projects, so restored tabs/projects may be involved, but the repeated tenfold launch of the same MCP servers seems excessive.

Expected behavior

Each configured local MCP server should have at most one active process per required OpenCode instance/session, with terminated or replaced processes cleaned up reliably. Restoring tabs or reconnecting the desktop UI should not multiply every local MCP server by approximately 10.

Related reports

This appears related to #26336, #42270, #43845, #46035, and #31554. The older #26336 report is closed, so this report provides updated data from OpenCode Desktop 1.18.25.

Please let me know if a diagnostic command or process dump would help. The measurements above intentionally omit personal paths, project names, account information, and credentials.