Codex App 26.608.12217: local file references in assistant responses are not clickable
Open 💬 3 comments Opened Jun 10, 2026 by Lxd-ncwu
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What happened?
In Codex App, assistant responses no longer render local file references as clickable links. They appear only as gray inline-code pills and cannot be opened from the response.
Version
Codex App 26.608.12217
Platform
macOS
Steps to reproduce
- Open any Codex App thread in a workspace.
- Ask the assistant to output a local file reference with a line number.
- Try both absolute and workspace-relative paths, for example:
/Users/lxd/work/Demo/app/src/main/java/com/demo/app/ui/BackupFragment.java:77
app/src/main/java/com/demo/app/ui/BackupFragment.java:77
Expected behavior
The file references should be clickable and should open the target file/line in Codex App.
Actual behavior
The references render as inline-code gray pills and are not clickable. This happens for both absolute paths and workspace-relative paths, and for both tracked source files and ignored local docs files.
Notes
This looks related to prior file-link regressions, but I could not find an exact report for Codex App 26.608.12217:
3 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Additional detail: network/Markdown URLs render and open correctly, so this does not appear to be a general Markdown link rendering issue.
For example, links like the Codex appcast URL and .zip download URL render as blue clickable links.
Only local file references fail to become clickable, including:
They render as gray inline-code pills instead of file links.
I have the same issue, all files that should be downloaded are not clickable. In any chat and any context.