codex - 💡(How to fix) Fix macOS: file paths in chat are not clickable (e.g. /Users/.../Foo.cs:116) [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#17744Fetched 2026-04-14 05:40:53
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Timeline (top)
labeled ×2commented ×1

In the Codex desktop app on macOS, file path references in chat messages are no longer clickable. Previously, I could click a path like /Users/.../Foo.cs:116 to open the file (and jump to the line). Now it renders as plain text/inline code and cannot be opened by clicking.

Root Cause

In the Codex desktop app on macOS, file path references in chat messages are no longer clickable. Previously, I could click a path like /Users/.../Foo.cs:116 to open the file (and jump to the line). Now it renders as plain text/inline code and cannot be opened by clicking.

RAW_BUFFERClick to expand / collapse

Summary

In the Codex desktop app on macOS, file path references in chat messages are no longer clickable. Previously, I could click a path like /Users/.../Foo.cs:116 to open the file (and jump to the line). Now it renders as plain text/inline code and cannot be opened by clicking.

Steps to reproduce

  1. Open the Codex desktop app on macOS.
  2. Send/receive a message that includes an absolute file path with a line number, e.g.
    • /Users/<username>/project/Assets/Scripts/Foo.cs:116
  3. Also try with backticks (inline code), e.g.
    • `/Users/<username>/project/Assets/Scripts/Foo.cs:116`
  4. Click the rendered path in the message.

Expected behavior

Clicking the file path opens the file in the configured editor (or at least triggers an “open file” action), ideally jumping to the specified line.

Actual behavior

The path is displayed, but it is not clickable and nothing opens.

Environment

  • OS: macOS 26.4.1 (arm64)
  • Codex: Desktop app (version unknown; please tell me where to find it if needed)

Additional context

  • This appears to be a regression (used to work).
  • I have a screenshot of the rendering if helpful.

extent analysis

TL;DR

The file path references in chat messages are no longer clickable due to a potential regression in the Codex desktop app, and verifying the app version may help identify the cause.

Guidance

  • Check the Codex desktop app version, as the issue might be specific to a particular version, and look for any release notes or changelogs that mention fixes for clickable file paths.
  • Try to find any settings or configurations in the Codex app that might be related to clickable links or file paths, as it's possible that a setting has been changed or reset.
  • If the issue is confirmed to be a regression, consider reaching out to the Codex support team or checking their issue tracker for any known issues or fixes related to clickable file paths.
  • Test the behavior with different types of file paths and line numbers to see if the issue is specific to certain formats or characters.

Example

No code snippet is provided as the issue seems to be related to the Codex app's rendering and handling of file paths rather than a specific code implementation.

Notes

The exact cause of the issue is unclear without more information about the Codex app version and its configuration. Additionally, the issue might be specific to the macOS environment or the arm64 architecture.

Recommendation

Apply workaround: Since the issue appears to be a regression, it's likely that a fix will be released in a future version of the Codex app. In the meantime, users may need to manually copy and paste file paths into their editor or use a different method to open files.

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…

FAQ

Expected behavior

Clicking the file path opens the file in the configured editor (or at least triggers an “open file” action), ideally jumping to the specified line.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING