{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidab23njsfyuf6dfxocqfgnyzrsxyi457giwnjtnxr2st7pfg4yke",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mgbmnqjuirx2"
  },
  "path": "/t/possible-bug-open-config-toml-in-wsl-environment-opens-windows-config-path/1375730#post_1",
  "publishedAt": "2026-03-04T23:55:46.000Z",
  "site": "https://community.openai.com",
  "textContent": "\n\nHi,\n\nI tried the new Codex Windows app. I’ve been using Codex CLI from WSL, so I expected my existing configuration to carry over.\n\nIn 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.\n\nWhile checking the Configuration page, I noticed the button **“Open config.toml in WSL environment”**. When I click it, it opens:\n\n\n    C:\\Users\\<USER>\\.codex\\config.toml\n\n\ninstead of the WSL path. So it looks like the button is pointing to the Windows filesystem rather than the WSL config.",
  "title": "Possible bug: \"Open config.toml in WSL environment\" opens Windows config path"
}