voideditor
[Bug] Agents cannot access WSL Remote directories
VSCode Version: 1.99.30034 (system setup) Void Version: 1.3.10 Commit: 906502f6600146442d41bc314c2dd011c686941f Date: 2025-05-16T20:35:23.913Z Electron: 34.3.2 ElectronBuildId: undefined Chromium: 132.0.6834.210 Node.js: 20.18.3 V8: 13.2.152.41-electron.0 OS: Windows_NT x64 10.0.26100
Models can't access my WSL directories, despite having activated the WSL remote environment
it is opening my local files, not on the WSL Distro
i'm connected to my WSL Remote on Void
I'm hitting this as well. Is there any known workaround for this issue? Would be really nice to be able to use void via the WSL remote connection.
This is a known issue, sorry about this! When connected to WSL or SSH we need to make the edits apply to the socket instead of the main file system. This sounds like an easy task, will look into it. Asking Claude nicely might resolve this.
I'm having this issue with SSH remote too, the agent thinks it's done stuff on the server but it's all in my local filesystem. VSCode works, in the same scenario.
have same issue too. windows system + remote ssh + centos.
- The terminal can not be open.
- chat to modify code, the path is windows style \home\user\workspace.
Sorry about this again! We just pushed a fix that might resolve this, can anyone try updating and see if edits work over SSH/WSL?
I tried over SSH after updating, but the model (GPT-4.1 in Agent mode) still wrote all the files to the local filesystem instead of to the remote server over the SSH connection. so all on C:\home\username\projects\projectname\app\features... instead of on the remote /home/usename/projects/projectname/app/features...
VSCode Version: 1.99.30038 (system setup)
Void Version: 1.4.3
Commit: bf062146c93fc98f0d19cad53528d012a652ffce
Date: 2025-06-06T08:49:49.945Z
Electron: 34.3.2
ElectronBuildId: undefined
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100
I hope that helps, Grant.
FWIW I've noticed Void is significantly more token efficient that GitHub Copilot. Keep up the great work.
Sorry about this again! We just pushed a fix that might resolve this, can anyone try updating and see if edits work over SSH/WSL?
ok for my windows + ssh + remote centos environment now.
I tried using a Windows + WSL (Ubuntu) environment, but Read File is still not working. It looks like Searched by file name and Write File are working properly.
VSCode Version: 1.99.30038 (user setup)
Void Version: 1.4.3
Commit: bf062146c93fc98f0d19cad53528d012a652ffce
Date: 2025-06-06T08:49:49.945Z
Electron: 34.3.2
ElectronBuildId: undefined
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100
Remote SSH works, but WSL does not. It mangles all POSIX paths.
VSCode Version: 1.99.30039 (user setup)
Void Version: 1.4.4
Commit: da425ab0fe34edfc3c082367edff7e05e0719b2d
Date: 2025-06-10T00:36:08.103Z
Electron: 34.3.2
ElectronBuildId: undefined
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.22631
Great! Anyone else still having any problems?
Windows + ssh + remote linux。 still not work well every time. The Void detect the work environment is Windows, and use file path style "\home\xxx", when apply to linux server side the path cause error。Please provide an manual setting, let the user choose the work environment (auto detect/ window / linux etc)
Windows + ssh + remote linux。 still not work well every time. The Void detect the work environment is Windows, and use file path style "\home\xxx", when apply to linux server side the path cause error。Please provide an manual setting, let the user choose the work environment (auto detect/ window / linux etc)
I am also seeing this issue.
