anomalyco / anomalyco/opencode

Desktop: remote server on Windows cannot correctly load/use projects and sessions from macOS client

Open
#42,627 2 comments 0 reactions 1 assignee View on GitHub

@Brendonovich is already working on this.

Since Aug 14, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Description

OpenCode Desktop can connect successfully to an opencode serve instance running on a Windows workstation from a macOS Desktop client, but the remote projects/sessions are not usable from the macOS client.

The underlying API works correctly: the Mac can retrieve the Windows server's sessions and projects, and the Desktop connection is shown as green. However, the Desktop UI does not correctly load/use those remote projects and sessions.

Plugins

No response

OpenCode version

1.18.18 in both machines

Steps to reproduce

Environment

  • OpenCode Desktop: 1.18.18
  • Server: Windows 11
  • Client: macOS
  • Server: opencode serve --hostname 127.0.0.1 --port 4096
  • Connection: SSH tunnel
  • Windows Desktop can use the server normally

Reproduction

  1. Run opencode serve --hostname 127.0.0.1 --port 4096 on Windows.
  2. Connect Windows OpenCode Desktop to 127.0.0.1:4096.
  3. Create/use sessions and projects on that server.
  4. Expose port 4096 to a Mac through an SSH tunnel.
  5. Connect macOS OpenCode Desktop to 127.0.0.1:4096.
  6. The connection is shown as green.
  7. From the Mac, verify that the server contains the sessions:
    curl http://127.0.0.1:4096/session
  8. The Desktop UI, however, does not correctly populate/use the remote projects/sessions.
    Opening a new session (in the client) gets stuck, it doesn't produce any error, simply it doesn't respond.
    New sessions in the host don't show up either.

The same server works correctly from Windows Desktop.

From macOS, /session returns the Windows sessions successfully, demonstrating that this is not a networking or server-state problem.

Related issues:

#19348
#29766
#25264

Screenshot and/or share link

No response

Operating System

Windows 10 and MacOS 26.5.2

Terminal

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.