Repository navigation
Desktop shows "OpenCode 1" for incompatible SSH servers even when remote is V2 #62582
Closed as duplicate
Description
Summary
When an SSH remote is marked incompatible, Desktop always shows:
This server is running OpenCode 1, which isn't compatible with this app. Upgrade it to OpenCode V2 to continue.
even if the remote is actually running OpenCode V2 (e.g. background service 2.2.5).
Screenshot
Environment
- Client: OpenCode Desktop 2.2.6 on Linux
- Remote over SSH running OpenCode background service 2.2.5 (
opencode-cli serve --service;~/.local/state/opencode/service.jsonreports"version":"2.2.5") - CLI on the remote PATH is also V2 (
opencode v2.2.5) - SSH auth succeeds; failure is the post-connect incompatible UI
Expected
- Do not claim the remote is OpenCode 1 when the version is unknown or is a V2 build
- If the remote is V2 at the wrong patch version, prefer the exact-version / "Server update required" path
- If truly incompatible, show the actual probed version when known
Actual
Tooltip says the server is running OpenCode 1 and asks to upgrade to V2.
Suspected cause
selectServerVersion only returns a version for healthy health. For incompatible it returns undefined, and the UI falls back to "1":
// packages/app/src/runtime/server/health-machine.ts
export function selectServerVersion(health: ServerHealth | undefined) {
return health?.type === "healthy" ? health.version : undefined
}
// packages/app/src/home/projects/view.tsx
props.language.t("server.row.incompatible", {
version: selectServerVersion(props.health) ?? "1",
})Same fallback in packages/app/src/session/server-unavailable-panel.tsx.
Notes
Updating the remote from 2.2.5 → 2.2.6 restores connectivity in this setup, but the OpenCode 1 label is still incorrect and misleading.
Activity
opencodejr commentedon Nov 7, 2026
Thanks for the clear report and for tracking down the cause in the code.
I think this is a duplicate of #53375. It's the same problem: an SSH remote running a slightly different V2 version is marked incompatible, its version is lost, and the UI falls back to
?? "1", so it says "running OpenCode 1". That issue also asks for the real version to be shown and for the "Server update required" / "Update and reconnect" path to be offered.Possible duplicates and related issues, most likely first:
Until it's fixed, Settings → Servers → ⋯ → Connect → Update and reconnect works around it, as does upgrading the remote (which you've already done).
The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different.
DonnieFi commentedon Nov 7, 2026
Agreed this is a duplicate of #53375.
Opened a fix against the canonical issue: #62584 (
Fixes #53375). Fine to close this one as a duplicate.opencodejr commentedon Nov 7, 2026
Thanks for confirming, and for opening #62584 against #53375. I'll leave this issue to close as a duplicate as planned. Please follow #53375 and the PR for progress.
opencodejr commentedon Nov 8, 2026
Closing this as a duplicate of #53375, as agreed above. Thanks again for the report and for opening #62584 against #53375. Please follow that issue and the PR for progress on the incorrect "OpenCode 1" label for V2 SSH remotes.