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
Desktop update does not update CLI, causing version mismatch and session sync issues #35122
When updating the OpenCode desktop application, the globally installed CLI version does not update automatically. This creates a version mismatch between the desktop app and the CLI/Web UI.
Because of this version gap, when I start the headless server via the CLI (opencode serve) for remote access, the chat sessions do not synchronize properly. To resolve this, I have to manually open a terminal, run the opencode command, and trigger the CLI update separately.
Updating the Desktop application should automatically update the associated CLI version to maintain version parity across all interfaces.
Plugins
opencode-gemini-auth
OpenCode version
1.17.13
Steps to reproduce
Update the OpenCode Desktop application to a newer version (e.g., 1.17.13).
Open a terminal and run opencode --version.
Observe that the CLI remains on the older version (e.g., 1.14.x).
Run opencode serve and connect via the Web/Remote UI.
Notice that chat sessions are not synchronized due to the version mismatch.
I agree that keeping the Desktop and CLI versions synchronized is important, but I would also like them to feel like two interfaces for the same OpenCode installation.
Ideally, installing OpenCode Desktop on Windows or Linux could optionally install the matching opencode CLI as well. Both should use the same version, authentication, configuration, sessions, providers, models, Agents, Skills, MCP servers, plugins, and permissions.
For example, if I add a Skill, Agent, or MCP server from the terminal, it should appear in Desktop automatically. A session created in Desktop should also be visible and resumable from the CLI/TUI.
Using the same backend and data directories—and updating Desktop and CLI together—would prevent version mismatches and make switching between the graphical and terminal workflows much smoother.
Activity
github-actions commentedon Jul 3, 2026
This issue might be a duplicate of an existing issue. Please check:
solcoteh commentedon Aug 3, 2026
I agree that keeping the Desktop and CLI versions synchronized is important, but I would also like them to feel like two interfaces for the same OpenCode installation.
Ideally, installing OpenCode Desktop on Windows or Linux could optionally install the matching opencode CLI as well. Both should use the same version, authentication, configuration, sessions, providers, models, Agents, Skills, MCP servers, plugins, and permissions.
For example, if I add a Skill, Agent, or MCP server from the terminal, it should appear in Desktop automatically. A session created in Desktop should also be visible and resumable from the CLI/TUI.
Using the same backend and data directories—and updating Desktop and CLI together—would prevent version mismatches and make switching between the graphical and terminal workflows much smoother.
github-actions commentedon Oct 4, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.