Codex passes VSCode the wrong path for opening files

[E-Roll]

Codex passes space characters as %20 when passing the file path to VSCode. This happens on macOS.

For example, if the file is at ‘/Users/mainuser/Code/Xcode Projects/project.swift’ it will open the ‘/Users/mainuser/Code/Xcode%20Projects/project.swift’ file in VSCode, which does not exist.

[jeffvpace]

Well, In web development and internet communication, %20 is the URL-encoded representation of a space character

[E-Roll]

Ok, its still wrong and a bug.

[jeffvpace]

See here:

Codex desktop app opens %20 literally in local file paths with spaces

I found a bug in the Codex desktop app when clicking local file links. If a file path contains spaces, the app appears to URL-encode the path and then tries to open the encoded path literally instead of decoding it first. Example linked path: /Users/example/projects/demo/output/Test%20Cases%20-%20BUG-123.xlsx Actual file on disk: /Users/example/projects/demo/output/Test Cases - BUG-123.xlsx Expected behavior: Clicking the link should open the real local file path with spaces. Actual beha…

[E-Roll]

Ok, we’re supposed to report bugs on github. I found an issue already filed: Issue 11102

[OpenAI_Support]

Hi @E-Roll

This is a known issue, Codex is URL-encoding spaces in file paths (%20), which breaks how VS Code resolves them.

Avoiding spaces in folder names or opening files directly from within VS Code should work as a workaround.