Skip to content

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

Open

Description

@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).
#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.

Additional information

No response

Activity

  1. added
    bugSomething isn't working
    windows-osIssues related to Codex on Windows systems
    on Nov 18, 2025
  2. TABmk commented on Nov 28, 2025

    @TABmk

    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 allowed

    Disabling security.restrictUNCAccess in settings makes it work.
    I tried adding wsl.localhost to security.allowedUNCHosts, but that doesn’t work.

  3. ashbeka commented on Dec 8, 2025

    @ashbeka

    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\.codex

    Just type it in the file explorer path.

  4. ofek commented on Mar 8, 2026

    @ofek

    I made a tracking issue for the root cause of these classes of bugs #10347

  5. wojciechmro commented on Mar 12, 2026

    @wojciechmro

    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:

    ln -s /home/<wsl-username>/.codex/config.toml /mnt/c/Users/<windows-username>/.codex/config.toml

    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:

    cat /mnt/c/Users/<windows-username>/.codex/config.toml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingextensionIssues related to the VS Code extensionwindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions