Mac app: local file links render as rich cards and show bogus F: path prefix

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

Version 26.409.20454 (1462)

What subscription do you have?

ProLite

What platform is your computer?

Darwin 25.4.0 arm64 arm

What issue are you seeing?

In the macOS Codex app, local file links that previously rendered as inline file references now render as rich cards.

Example of the underlying link text in TUI-style output:

F:/Users/a/b/c/workspace.py†L70-L87】【F:/Users/a/b/c/workspace.py†L182-L188]

Current behavior in the Mac app:

• each file link renders as a large card
• the visible title is just workspace
• the subtitle is PY
• the path/line range is no longer visible inline or in the tooltip
• clicking on the large card does not jump to the associated lines

Expected behavior:

• local file links should render as normal file references, not rich cards
• line ranges should remain visible
• macOS should not show a Windows-style F: drive prefix for local paths

Why this looks like a regression:

• the TUI renderer in codex-rs/tui/src/markdown_render.rs is explicitly designed to render local file links as code-like path text derived from the target path
• on macOS, the app now appears to be misclassifying those local file links and/or preserving an invalid Windows-style path form

Impact:

• file references are much harder to scan in transcripts
• line-specific context is obscured
• the F: prefix is confusing and appears incorrect on macOS

Attached:

• screenshot of current Mac app rendering

<img width="1512" height="820" alt="Image" src="https://github.com/user-attachments/assets/fbf045e1-7de1-411b-b221-4a605d8885f2" />

What steps can reproduce the bug?

What steps can reproduce the bug?

1. Open the macOS Codex app on a recent build.
2. Start a session in a workspace containing a file such as workspace.toml.
3. Ask Codex a question that causes it to cite the file with line references, or otherwise produce local file links in the response.
4. Observe how those file references render in the transcript.

What is the expected behavior?

Local file links should render as inline file references, not rich cards.

Expected text-style rendering should look something like:

workspace.py:70-87
workspace.py:182-188

Or, if absolute/relative paths are shown:

/Users/a/b/c/workspace.py:70-87
/Users/a/b/c/workspace.py:182-188

At minimum:

• the file path/name should be shown inline
• the line numbers or ranges should remain visible
• macOS local paths should not display a bogus Windows-style F: prefix

Additional information

_No response_