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
Remote server responses not updating in desktop app when multiple servers are configured #17654
I’m experiencing an issue with the OpenCode desktop app when multiple remote servers are configured.
I currently have two remote OpenCode servers added in the desktop app:
• Server 1: AlmaLinux (default server)
• Server 2: Ubuntu
The first server (AlmaLinux) works normally.
However, when I switch to the second server (Ubuntu) and send a prompt, the following happens:
• The prompt is accepted by the UI
• The server processes the request (verified)
• But no response appears in the UI
If I switch to another server and then switch back to the Ubuntu server, the response suddenly appears.
So it seems the response is actually generated but the desktop UI does not update in real-time.
I will attach a video recording showing the issue.
Additional issue on Windows
I also tested the desktop app on Windows, and I’m seeing another related problem:
• I send a prompt
• The notification sound plays, indicating a response was received
• But no response is displayed in the UI at all
So the response seems to arrive, but the UI never renders it.
Environment
OpenCode version:
1.2.26
Servers:
Server 1: AlmaLinux
Server 2: Ubuntu
Both servers are running:
opencode serve --hostname 0.0.0.0 --port 4096
Both are running as systemd services.
Observations
• The server does process the prompt
• The response exists and appears after switching servers
• The issue seems to be related to desktop app state / streaming / session refresh
Activity
hajekt2 commentedon Mar 17, 2026
I experience the same issue on Windows 11, having just Local Server and just adding one remote server triggers the issue.
krodak commentedon Mar 17, 2026
Same issue for me, both on macOS
hajekt2 commentedon Mar 17, 2026
I have a fix for this and I’m opening a PR.
github-actions commentedon Jul 7, 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.