Repository navigation
desktop: SSH server version mismatch shows "running OpenCode 1" instead of real version #53375
Description
Description
When the Desktop app connects to an SSH server whose background service is a slightly different V2 version, the server row says:
This server is running OpenCode 1, which isn't compatible with this app. Upgrade it to OpenCode V2 to continue.
The remote server was actually running 2.0.22 and the app was 2.0.23. It was a patch-level mismatch, not V1.
Cause (from the 2.0.23 bundle):
Ssh.bootstrapreads the remoteservice.json. If its version differs from the app's version, it fails withSshFailure("version", "2.0.22"), and the SSH stage becomesincompatible.- The renderer maps the
incompatiblestage to{ healthy: false, incompatible: true }, so the remote version is dropped. - The server row renders
t("server.row.incompatible", { version: health?.version ?? "1" }), so it always falls back to "1".
Expected: show the real remote version, for example "running OpenCode 2.0.22". For a V2 mismatch, use the existing "Server update required" / "Update and reconnect" wording instead of telling the user to upgrade to V2.
Workaround: running opencode upgrade and opencode service restart on the remote fixed it.
Plugins
None relevant (Desktop SSH connection)
OpenCode version
Desktop 2.0.23 (macOS), remote service 2.0.22 (Linux)
Steps to reproduce
- On a remote Linux host, run the OpenCode background service at version N (for example 2.0.22).
- Connect to that host from OpenCode Desktop at version N+1 (for example 2.0.23) using an SSH server.
- The server row shows "This server is running OpenCode 1…".
Operating System
macOS (Darwin 27.0.0, arm64) client; Linux remote
Terminal
N/A (Desktop app)
Activity
github-actions commentedon Oct 5, 2026
This issue might be a duplicate of an existing issue. Please check:
opencodejr commentedon Oct 27, 2026
Thanks for the detailed report. I couldn't reproduce this here because it needs the Desktop app connected to a remote background service over SSH, and our sandbox can't run that. A maintainer with that setup will need to confirm it.
I didn't run it, but the code on the latest
dev(f7d0ce1) still has the path you describe. The SSH bootstrap fails with the remote version, the stage becomesincompatible, and the renderer'sstageHealth(packages/app/src/runtime/server/health.ts) keeps onlyincompatible: trueand drops the version. The server row (home/projects/view.tsx) and the server-unavailable panel (session/server-unavailable-panel.tsx) then fall back to"1".The workaround you found is the right one for now: run
opencode upgrade, thenopencode service restart, on the remote.A related open issue is #55429, a different Desktop SSH version problem that causes a reconnect loop.