Windows ChatGPT app generates incorrect local file hyperlink for Work artefacts

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

Version 26.727.51351

What subscription do you have?

Plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

When a Work task completes, the generated hyperlink to the output Markdown file points to an invalid local path.
Example generated path:
C:\Users\User.codex.chatgpt-projects\g-p-6a70af3ddf248191ae90ff9ed95de4a9\Competitor Analysis.md
The actual file is correctly created at:
C:\Users\User\.codex\.chatgpt-projects\g-p-6a70af3ddf248191ae90ff9ed95de4a9\Competitor Analysis.md
The Windows app appears to concatenate the path incorrectly, omitting the required \ separators around the .codex directory.
The file itself is created successfully; only the hyperlink is incorrect.

Reproduction steps
Open a Project in the Windows ChatGPT app.
Start a Work task that generates a Markdown artefact.
Wait for completion.
Click the generated hyperlink.
Observe that the link points to:C:\Users\<user>.codex.chatgpt-projects\...

Verify that the file actually exists in:C:\Users\<user>\.codex\.chatgpt-projects\...

Expected behaviour
The hyperlink should point to the actual file location inside:

C:\Users\<user>\.codex\.chatgpt-projects\

<img width="999" height="342" alt="Image" src="https://github.com/user-attachments/assets/626b8b54-b62f-4c65-9ae5-c28f30994d08" />

What steps can reproduce the bug?

Feedback ID: no-active-thread-019fce73-dbd9-79b3-af23-83d3063a5bb6

What is the expected behavior?

The hyperlink should point to the actual file location inside:

C:\Users\<user>\.codex\.chatgpt-projects\

Additional information

"The Work artefacts are written correctly to the local project workspace. It would be helpful if the Windows app exposed an 'Open containing folder' action in addition to the hyperlink."

That's not a bug—it's a feature request—but it's a sensible quality-of-life improvement for users working with generated documents.
Overall, this is a high-quality bug report because you've:
isolated the issue,
identified the incorrect and correct paths,
confirmed the file generation succeeds,
and provided a simple way to reproduce it. That makes it much easier for the engineering team to diagnose.