Markdown file links with spaces in absolute paths render as plain text

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

26.311.21342 (993)

What subscription do you have?

Enterprise

What platform is your computer?

Darwin 24.6.0 arm64 arm

What issue are you seeing?

Markdown file links rendered in responses show as plain text instead of clickable links when the absolute path contains unencoded spaces.

Failed example:

[example.ts](/Volumes/Windows 11/My App/src/example.ts)

Actual: the raw Markdown string is shown in the response
Expected: a clickable file link

If the spaces are percent-encoded, it works:

[example.ts](/Volumes/Windows%2011/My%20App/src/example.ts)

Here's an example from the app:

<img width="777" height="380" alt="Image" src="https://github.com/user-attachments/assets/27ffa815-bc49-4748-9440-11f5ddd06b1d" />

What steps can reproduce the bug?

1. Create a folder whose absolute path contains spaces
2. Create a file inside that folder
3. In a Codex conversation, ask Codex to reference that file as a clickable file link in its response
4. Observe that the response shows the raw Markdown text instead of a clickable link when the path contains unencoded spaces

What is the expected behavior?

Markdown file links rendered in responses should become clickable links even when the absolute path contains spaces, or the renderer/output pipeline should automatically handle/encode spaces in the link target

For example, a file at /Volumes/Windows 11/My App/src/example.ts should render as a clickable link

Additional information

_No response_