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.

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

See here: [image] Codex desktop app opens %20 literally in local file paths with spaces Codex 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 …

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

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.

Codex passes VSCode the wrong path for opening files

Codex

jeffvpace April 7, 2026, 1:54am 4

See here:

Topic		Replies	Views
Codex desktop app opens %20 literally in local file paths with spaces Codex codex-app	1	333	March 12, 2026
[VSCode][openai.chatgpt] File links in chat do not open in editor (macOS) Codex CLI issue	4	425	April 16, 2026
Codex fails to start on Windows when the username contains special characters Codex codex , bug , windows-app , codex-app	1	771	March 27, 2026
Possible bug: "Open config.toml in WSL environment" opens Windows config path Codex windows-app , codex-app	2	925	March 6, 2026
Codex Extension (Webview) Fails After VS Code Update on WSL — Workaround Codex codex	1	194	October 14, 2026

Codex passes VSCode the wrong path for opening files

Related topics