[BUG] Void creating files outside of WSL

[WilliamBenEmbarek]

VSCode Version: 1.99.30023 (system setup) Void Version: 1.3.2 Commit: 56c2f7a900fd2e98cd96cef2498840cbcda8230e Date: 2025-05-08T20:53:45.582Z 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

2. Describe the issue/feature here.

When working on a windows host but developing within WSL the agent is not fully aware that it is run inside WSL. When files are created it saves them in C:\home<username>... instead of saving them inside the WSL filesystem. It also often appears it has trouble finding files on the filesystem when they are in WSL.

[andrewpareles]

Just to confirm, you opened the folder as a workspace, right?

[WilliamBenEmbarek]

I would believe so? I normally always open VSCode, connect the VSCode window to WSL, and then go file open and then open the folder I was working in.

[WilliamBenEmbarek]

@andrewpareles 100% confirm folder is opened as a workspace. Is there anyways I can generate debug logs from a conversation? I can get the gather mode relatively often to try to search for files on my windows host and not within the WSL filesystem.

[moziboo]

This is the same thing I see on my system. Agent insists that it has created a file in the workspace but it's actually in the home directory of my C drive