codex - 💡(How to fix) Fix Codex app can’t open clickable local file paths when the path contains spaces (macOS) [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#17682Fetched 2026-04-14 05:41:21
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×2commented ×1cross-referenced ×1
RAW_BUFFERClick to expand / collapse

What version of the Codex App are you using (From “About Codex” dialog)?

26.409.20454 (1462)

What subscription do you have?

Pro

What platform is your computer?

Darwin 25.4.0 arm64 arm

What issue are you seeing?

Clicking a file path link that includes spaces does nothing (not opening the file with my chosen IDE/Finder)/ shows “Unable to load file” on the preview page. I inspected the link and they seem to be written with % in the spaces.

<img width="1198" height="1348" alt="Image" src="https://github.com/user-attachments/assets/868de8c6-cebf-479d-902e-e93afba9b452" />

What steps can reproduce the bug?

  1. In Codex app, open any view where Codex renders a clickable local path in a message.
  2. Use a local path containing a space, e.g. /Users/username/My Drive/.codex.
  3. Click the rendered hyperlink.

What is the expected behavior?

It should open the clicked file in an IDE/Finder and shows it on the preview page.

Additional information

No response

extent analysis

TL;DR

The issue can likely be resolved by properly handling URL-encoded spaces in file paths.

Guidance

  • Verify that the Codex App correctly handles URL-encoded spaces (%20) in file paths by checking the link generation logic.
  • Inspect the link target to ensure it matches the expected file path, considering the URL encoding of spaces.
  • Test the link with a file path containing no spaces to isolate the issue.
  • Consider manually replacing %20 with a space in the link target to test if it resolves the issue.

Example

No code snippet is provided as the issue does not imply a specific code change.

Notes

The issue seems to be related to how the Codex App handles URL-encoded spaces in file paths. Without access to the app's codebase, it's difficult to provide a definitive fix. However, ensuring proper handling of URL encoding should resolve the issue.

Recommendation

Apply workaround: The user can try manually replacing %20 with a space in the link target to test if it resolves the issue, as this might indicate the need for a more robust URL decoding mechanism in the Codex App.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING