Codex Desktop on Windows drops the backslash before .codex when copying/opening local file paths

What issue are you seeing?

In Codex Desktop on Windows, a local file path shown in the chat UI is correct, but the right-click actions produce an invalid path.

Correct path shown by Codex:

C:\Users\13852\.codex\automations\java\yangzhou_guoyangqi_baseline.md

After using the right-click copy action, the copied path becomes:

C:\Users\13852.codex\automations\java\yangzhou_guoyangqi_baseline.md

The backslash before .codex is dropped, so Windows interprets it as a different directory: C:\Users\13852.codex.

That folder does not exist.

The right-click "Open in File Explorer" action also fails, likely because the same malformed path is passed to Explorer.

Steps to reproduce

1. On Windows, create or reference a file under a dot-prefixed folder, for example:

C:\Users\<user>\.codex\automations\java\yangzhou_guoyangqi_baseline.md

1. Ask Codex Desktop to output a clickable Markdown file link to that path.
2. Right-click the rendered file link.
3. Use the copy path action.
4. Paste the copied path somewhere.
5. Try the "Open in File Explorer" action.

Expected behavior

The copied path should preserve the directory separator:

C:\Users\<user>\.codex\automations\java\yangzhou_guoyangqi_baseline.md

"Open in File Explorer" should open the correct file or containing folder.

Actual behavior

The copied path loses the backslash before .codex:

C:\Users\<user>.codex\automations\java\yangzhou_guoyangqi_baseline.md

This points to a non-existent folder, and "Open in File Explorer" fails.

Platform

Windows / Codex Desktop app.

Notes

This looks like a Windows local file link path normalization or escaping bug in the Codex Desktop right-click context menu actions.

Related existing issues appear to cover other Windows local path handling cases, but I did not find this exact separator-dropping behavior for a dot-prefixed path segment.