Desktop: session-ID links fail to open sessions on another connected server #56471

Description

Clicking a session-ID button in an assistant reply shows “This session cannot be found” when the session belongs to another connected server. A local-server session button works from the same reply.

Expected: Desktop opens the session on the connected server that owns it.

Plugins

Reproduced with all external plugins disabled on both servers, verified through /api/plugin. Only built-in plugins remained active.

OpenCode version

Desktop and local CLI: 2.0.32. Docker server: 2.0.31.

Steps to reproduce

1. Open a conversation on server A in OpenCode Desktop.
2. Start an isolated Docker-hosted OpenCode server B with its port published locally.
3. Pair Desktop with B and confirm it is connected.
4. Create an empty session on each server:

   opencode2 api post /api/session \
     --data '{"title":"Session link repro"}'

5. Confirm B’s session exists using GET /api/session/<id> on B.
6. In the conversation on A, have the assistant include both complete session IDs as inline code in the same reply.
7. Click each rendered session-ID button.

Reproduced with newly created, empty sessions; no model execution or provider credentials required. A’s button opens successfully; B’s shows the error above. B’s API returns its session; A’s API returns SessionNotFoundError for that ID.

Screenshot and/or share link

No screenshot or shared conversation attached. Exact toast: “This session cannot be found”.

Operating System

macOS

Terminal

OpenCode Desktop; the failing interaction is in the conversation UI, not a terminal.

Related: #56419, #52080, #53529.