Possible bug: "Open config.toml in WSL environment" opens Windows config path

Codex
,
1

image
image1025×813 35.5 KB

Hi,

I tried the new Codex Windows app. I’ve been using Codex CLI from WSL, so I expected my existing configuration to carry over.

In WSL I have a setup with ~/.codex/config.toml, some SKILLS, and several MCP servers defined in the config. In the Windows app, the SKILLS from my WSL ~/.codex directory seem to be detected correctly, but config.toml is not, so my MCP servers are missing.

While checking the Configuration page, I noticed the button “Open config.toml in WSL environment”. When I click it, it opens:

C:\Users\<USER>\.codex\config.toml

instead of the WSL path. So it looks like the button is pointing to the Windows filesystem rather than the WSL config.

1 Like
2

IMO this is DEFINITELY a bug or possibly a necessary feature. The app reviews codex-cli sessions. Ideally it should offer to read both WSL and Windows .codex as a config parameter.

3

Consider use of a distro in the Linux subsystem as a minimum attempt at sandbox, beside giving AI Posix (it sort of understands). You want the AI able to rewrite its own config?

Also, I’m not so certain that they’d be clever enough to map your default Linux to its path; have a look:
\\wsl$

Then consider how it might go wrong when you ponder after running and reading:

wsl --list --online