Desktop app v1.15.13 doesn't load MCP/LSP/plugin config from opencode.json #30390

Activity

1. github-actions

   assigned

   Brendonovich

   on Jun 2, 2026
2. github-actions commented on Jun 2, 2026

   

   github-actionsBot

   on Jun 2, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • Desktop v1.15.13: MCP UI shows '未配置 MCPs' despite MCP server running (CLI mcp list shows connected) #30366: Desktop v1.15.13 MCP UI shows 'not configured' despite MCP server running (CLI works)
   • Desktop app v1.15.13 shows "No MCPs configured" despite MCP servers being loaded by sidecar #30368: Desktop app v1.15.13 shows "No MCPs configured" despite MCP servers being loaded by sidecar
   • Desktop 1.15.13 does not load remote MCP servers from ~/.config/opencode (works in CLI same version) #30354: Desktop 1.15.13 does not load remote MCP servers from ~/.config/opencode (works in CLI)
   • MCPs disappeared on electron MacOS desktop app #30299: MCPs disappeared on Electron macOS desktop app (v1.15.13, CLI works)
   • MCPs are loaded but not appearing as such in the MCP panel Window #30328: MCPs are loaded but not appearing in the MCP panel (Desktop v1.15.13)

   All of the above describe the same symptom: Desktop app v1.15.13 does not display MCP servers configured in opencode.json, while the CLI works correctly. Please check these issues before proceeding, and consider adding your information there instead.
3. Astro-Han commented on Jun 3, 2026

   

   Astro-Han

   on Jun 3, 2026

   Last edited by Astro-Han

   More actions

   Your evidence already narrows this down nicely: CLI resolves the config, but the Desktop sidecar's opencode.global.dat has server.list: []. So the sidecar is running with a different config resolution than the CLI, not failing to parse a found file.

   Worth checking which of these the sidecar diverges on:

   • cwd / project root. The CLI resolves project opencode.json relative to where you launched it. A sidecar spawned by Electron often starts with cwd set to the app's resources dir or the user's home, so a project-root config is simply out of scope. Does the global ~/.config/opencode/opencode.json alone get loaded, independent of any project file?
   • Env the sidecar inherits. XDG_CONFIG_HOME, OPENCODE_CONFIG, HOME/USERPROFILE differences between an Electron-spawned process and your shell will send config resolution to a different path. On Windows specifically, %APPDATA%\opencode vs ~/.config/opencode resolve differently depending on which the process thinks is home.
   • Whether the sidecar even runs the same config loader. If Desktop keeps its own store and only merges a subset of fields, mcp/lsp/plugin could be dropped on the way in, which matches "no errors in logs" since nothing failed, the keys were just never read.

   A useful datapoint: launch the sidecar binary the same way Desktop does (same cwd + env) and run the equivalent of debug config from there. If that output is missing mcp while your shell's opencode debug config has it, it's purely a cwd/env resolution gap, which is fixable without touching the loader.
   We had the exact same sidecar-vs-shell config resolution bug in PawWork — the fix was making the sidecar explicitly inherit cwd and config home from the Electron main process's resolved project root, rather than letting the OS default them.
4. Hona commented on Jun 4, 2026

   

   Hona

   on Jun 4, 2026

   Member

   More actions

   Fixed in next version
5. Hona

   closed this as completedon Jun 4, 2026