Windows paths are rendered as /c:/... instead of C:/..., breaking VS Code file opening

What platform is your computer?

Windows

What issue are you seeing?

Codex sometimes renders absolute Windows file paths in a Unix-like form such as /c:/Users/name/project/src/file.ts instead of a native Windows form such as C:/Users/name/project/src/file.ts.

On Windows, this breaks a common workflow in VS Code: the /c:/... form is not reliably recognized as a normal local Windows path, so Ctrl+Click does not directly open the file.

What steps can reproduce the bug?

1. Use Codex on Windows.
2. Ask Codex to print or reference an absolute local file path.
3. Observe that the path may be shown as /c:/... instead of C:/....
4. Try to use that path in VS Code as a clickable local file reference.
5. Observe that direct file opening does not work reliably.

What is the expected behavior?

Codex should render local absolute Windows paths in a native Windows-compatible form such as C:/Users/name/project/src/file.ts or C:\Users\name\project\src\file.ts.

Additional information

This appears related to Windows path normalization / presentation rather than being only a link-handling issue.