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
{{ message }}
Repository navigation
[FEATURE]:Reload MCP servers without starting a new session #51597
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Description: When a new MCP server is added to opencode.json while a session is already open, the running session never picks it up. The only way to get the new tools is to close the conversation and start a new session. Restarting the app alone is not enough if the old session is resumed.
Steps to reproduce:
Open a session in OpenCode Desktop.
Add a new MCP server to opencode.json (e.g. chrome-devtools-mcp).
Verify with opencode mcp list that the server shows connected.
Go back to the open session: the new MCP tools are not available there.
Only a brand-new session gets the tools.
Expected: A way to reload/reconnect MCP servers mid-session (like Claude Code's /mcp reconnect), without losing the current conversation.
Actual: Tools are frozen at session start; config changes require a new session.
Reference: Claude Code and Codex CLI both support reconnecting MCP servers at runtime. OpenCode currently does not.
Env:
OpenCode Desktop for Windows
MCP added: chrome-devtools-mcp@1.10.1 as local server
Thanks for the suggestion. We're tracking applying MCP configuration changes without restarting the running session in #39987, so I'm closing this as a duplicate. Please follow that issue for updates.
Activity
github-actions commentedon Sep 27, 2026
This issue might be a duplicate of existing issues. Please check:
neriousy commentedon Oct 20, 2026
Thanks for the suggestion. We're tracking applying MCP configuration changes without restarting the running session in #39987, so I'm closing this as a duplicate. Please follow that issue for updates.