Codex mac app: “Open in editor” fails on Cursor when workspace path contains spaces
Open 💬 1 comment Opened Feb 8, 2026 by waleedzeb
What version of the Codex App are you using (From “About Codex” dialog)?
Version 260206.1448 (565)
What subscription do you have?
Plus
What issue are you seeing?
When using Codex Desktop with Cursor as the editor target, clicking file links (open-in-editor/file references) fails if any parent directory in the workspace path contains spaces.
Cursor opens multiple empty tabs, as if the path was split by spaces (for example: 2., Example, Projects).
What steps can reproduce the bug?
- Set Codex Desktop editor target to Cursor.
- Open a workspace whose path includes spaces, for example:
/Users/example/Dev/2. Example Projects/demo-repo
- Click a file path link in Codex output.
What is the expected behavior?
Cursor opens the intended file path.
Additional information
Scope
- Reproduces only with Cursor target.
- Does not reproduce with non-Cursor editor targets.
Environment
- Platform: macOS
- App: Codex Desktop
- Editor target: Cursor
Additional context
This looks like path arguments are not being quoted/escaped correctly when launching Cursor from Codex Desktop.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗