Desktop app uses Windows file picker for projects when connected to WSL2 server #25264

Description

What happened?

When the OpenCode Desktop app connects to a server running inside WSL2 (via http://localhost:4096), clicking "Add Project" opens a Windows native file picker that only browses Windows drives (C:\, D:\, etc.). WSL2 paths like /home/user/project are not accessible. The only workaround is to start opencode serve from inside the target project directory, which defeats the purpose of the desktop app's project management.

What did you expect to happen?

When connected to a WSL2 server, the project picker should detect that the remote environment is Linux and either:

• Open a WSL-aware directory browser, or
• Provide a text input field where the user can type a WSL2 absolute path (e.g., /home/user/projects/my-repo).

Steps to reproduce

1. In WSL2, start a server:

   opencode serve --hostname 0.0.0.0 --port 4096

2. On Windows, open OpenCode Desktop and connect to http://localhost:4096.
3. Click "+ Add Project" in the sidebar.
4. A Windows file dialog opens — WSL2 directories are not reachable.

Client information

• OpenCode Desktop version: v1.14.31
• Platform: Windows 11 + WSL2 (Ubuntu)
• Connection method: Desktop app → http://localhost:4096 (WSL2 serve instance)

Related issues

• Windows: desktop app (WSL) tries to open projects from local pc #13089 — Desktop app (WSL) tries to open projects from local pc
• feat(desktop): Add option to run OpenCode backend via WSL on Windows #5635 — Add option to run OpenCode backend via WSL on Windows
• fix: WSL UNC paths break bash and git on Windows #22215 — WSL UNC paths break bash and git on Windows

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response