You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
'Open config.toml in WSL environment' broken (incorrect path) #6809
What version of the VS Code extension are you using?
0.5.43
What subscription do you have?
Plus
Which IDE are you using?
VS Code Insiders
What platform is your computer?
Win10-64
What issue are you seeing?
In the WSL testing discussion I reported the menu option to open the config.toml was broken (nothing happens). #5471 (comment)
After more investigation I found I could open the file fine from Windows Explorer. Located here: Network\wsl$\Ubuntu\home\[username]\.codex
aka \\wsl.localhost\Ubuntu\home\[username]\.codex
The extension likely fails to open it as the path is misconfigured, but it must know the correct path or WSL mode wouldn't work at all.
What steps can reproduce the bug?
Settings->Codex Settings->Open config.toml in WSL environment
What is the expected behavior?
Same as non-WSL mode.
If the extension can't find the file it should notify the user instead of failing silently.
A workaround that worked for me was to create a symlink from inside WSL so the Windows path points to the config file in the WSL home directory like so:
You can verify it from WSL by reading the file through the Windows-mounted path. The contents should come from the target file in the WSL home directory:
Activity
TABmk commentedon Nov 28, 2025
Found a temporary workaround:
When you click "Open config.toml in WSL environment", it shows an error in devtools:
[openai.chatgpt]UNC host 'wsl.localhost' access is not allowedDisabling
security.restrictUNCAccessin settings makes it work.I tried adding
wsl.localhosttosecurity.allowedUNCHosts, but that doesn’t work.ashbeka commentedon Dec 8, 2025
The config.toml file was a bit #hard for me to find (WSL on Windows), but I found it here:
\\wsl.localhost\Ubuntu\mnt\wslg\distro\root\.codexJust type it in the file explorer path.
ofek commentedon Mar 8, 2026
I made a tracking issue for the root cause of these classes of bugs #10347
wojciechmro commentedon Mar 12, 2026
A workaround that worked for me was to create a symlink from inside WSL so the Windows path points to the config file in the WSL home directory like so:
You can verify it from WSL by reading the file through the Windows-mounted path. The contents should come from the target file in the WSL home directory: