Desktop crashes when opening project after attach to remote server #4162

Open
opened 2026-02-16 17:42:51 -05:00 by yindo · 2 comments
Owner

Originally created by @HoYiShui on GitHub (Jan 4, 2026).

Originally assigned to: @adamdotdevin on GitHub.

Description

When using OpenCode Desktop (beta) to attach to a remote opencode serve instance over a private network (Tailscale), the Desktop app crashes with an UnknownError: No such file or directory after clicking/selecting the project directory in the UI.

The remote server is running correctly, and the project directory does exist on the remote server.
The same remote server works reliably when accessed via OpenCode CLI, both locally on the server and from a local machine using opencode attach.

This strongly suggests the issue is specific to OpenCode Desktop (beta), rather than the server, network, or project setup.

Plugins

No response

OpenCode version

No response

Steps to reproduce

  1. On a remote Linux server (EC2, Ubuntu), start opencode server from a valid project directory:

    cd
    opencode serve --hostname --port

  2. On local machine, open OpenCode Desktop (beta).

  3. Attach to the remote server using:
    http://:

  4. In the Desktop UI, click/select the project directory shown in the interface.

  5. The app immediately throws an error and becomes unstable.

Screenshot and/or share link

Image Image Image

Operating System

No response

Terminal

No response

Originally created by @HoYiShui on GitHub (Jan 4, 2026). Originally assigned to: @adamdotdevin on GitHub. ### Description When using OpenCode Desktop (beta) to attach to a remote `opencode serve` instance over a private network (Tailscale), the Desktop app crashes with an `UnknownError: No such file or directory` after clicking/selecting the project directory in the UI. The remote server is running correctly, and the project directory does exist on the remote server. The same remote server works reliably when accessed via OpenCode CLI, both locally on the server and from a local machine using `opencode attach`. This strongly suggests the issue is specific to OpenCode Desktop (beta), rather than the server, network, or project setup. ### Plugins _No response_ ### OpenCode version _No response_ ### Steps to reproduce 1. On a remote Linux server (EC2, Ubuntu), start opencode server from a valid project directory: cd <project-path> opencode serve <project-path> --hostname <remote-ip> --port <remote-port> 2. On local machine, open OpenCode Desktop (beta). 3. Attach to the remote server using: http://<remote-ip>:<remote-port> 4. In the Desktop UI, click/select the project directory shown in the interface. 5. The app immediately throws an error and becomes unstable. ### Screenshot and/or share link <img width="3840" height="2080" alt="Image" src="https://github.com/user-attachments/assets/1b74e991-cf3c-4a8e-b8cd-ce3fbd50ebb9" /> <img width="3840" height="2080" alt="Image" src="https://github.com/user-attachments/assets/00933a16-b1f9-46ce-9a03-63ef68ad0962" /> <img width="3840" height="2080" alt="Image" src="https://github.com/user-attachments/assets/774aab30-8290-475f-9938-baaea5e3c4eb" /> ### Operating System _No response_ ### Terminal _No response_
yindo added the bugweb labels 2026-02-16 17:42:51 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 4, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #4967: opencode attach: File path duplicates client's relative directory, causing ENOENT - This involves similar path resolution errors when attaching to remote servers
  • #5380: TUI referencing local directory when using attach --dir to connect to a remote server - Directly related to path resolution issues with remote connections
  • #4686: TUI sends absolute local paths causing ENOENT on server side - Similar client-to-server path mismatch issues, particularly when connecting from different OS platforms to remote servers

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Jan 4, 2026): This issue might be a duplicate of existing issues. Please check: - #4967: `opencode attach`: File path duplicates client's relative directory, causing ENOENT - This involves similar path resolution errors when attaching to remote servers - #5380: TUI referencing local directory when using attach --dir to connect to a remote server - Directly related to path resolution issues with remote connections - #4686: TUI sends absolute local paths causing ENOENT on server side - Similar client-to-server path mismatch issues, particularly when connecting from different OS platforms to remote servers Feel free to ignore if none of these address your specific case.
Author
Owner

@HoYiShui commented on GitHub (Jan 4, 2026):

The three related issues suggested by the action bot are all related to the TUI client.

In my case, the issue is triggered exclusively in the OpenCode Desktop app.
I confirmed that the same remote server and project directory work correctly when accessed via the OpenCode CLI.

This makes me believe the issue is Desktop-specific rather than a duplicate of the existing TUI-related issues.

@HoYiShui commented on GitHub (Jan 4, 2026): The three related issues suggested by the action bot are all related to the TUI client. In my case, the issue is triggered exclusively in the OpenCode Desktop app. I confirmed that the same remote server and project directory work correctly when accessed via the OpenCode CLI. This makes me believe the issue is Desktop-specific rather than a duplicate of the existing TUI-related issues.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#4162