Local file links from Codex open empty buffers in Sublime or other IDE tools instead of resolving to existing project files
What version of the Codex App are you using (From “About Codex” dialog)?
26.608.12217
What subscription do you have?
ChatGPT Pro
What platform is your computer?
Darwin 24.6.0 arm64 arm
What issue are you seeing?
In Codex file/Markdown preview, clicking the local Markdown link ./33-source-manifest.tsv from:
<PROJECT_ROOT>/docs1/09-validation/README.md
opens Sublime, but Sublime shows an empty file/buffer.
Expected:
Codex should resolve the relative Markdown link against the current README directory and open:
<PROJECT_ROOT>/docs1/09-validation/33-source-manifest.tsv
Actual:
Sublime opens with no content, suggesting Codex passed an invalid or unresolved path.
Evidence:
The target file exists and is not empty.
Observed size: about 39 KB.
First row:
source action rule target
The README link is valid Markdown:
[33 Source Manifest](./33-source-manifest.tsv)
Why this looks like a Codex bug:
- The Markdown link is a valid relative file link.
- The target file exists and has content.
- Sublime appears to receive the wrong path or a non-existing path.
- Codex should either resolve the relative path correctly or show an error before opening the editor.
<img width="1665" height="1416" alt="Image" src="https://github.com/user-attachments/assets/618f812d-af5f-4af0-a1c1-1b2a578fcc06" />
What steps can reproduce the bug?
Open a local project in Codex on macOS. Open a Markdown document containing a relative local file link, such as <PROJECT_ROOT>/docs1/09-validation/README.md. Click a link such as [33 Source Manifest](./33-source-manifest.tsv). Sublime Text opens, but it shows an empty buffer instead of the existing target file. The target file exists and has content, so Codex appears to be passing an unresolved or invalid path to the editor.
What is the expected behavior?
_No response_
Additional information
_No response_