'Open config.toml in WSL environment' broken (incorrect path)

Open 💬 4 comments Opened Nov 18, 2025 by ThoughtPhotography

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).
https://github.com/openai/codex/discussions/5471#discussioncomment-14915652

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.

Additional information

_No response_

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗