[Windows] Cannot resume thread due to stale path mismatch between normal path and \\?\ verbatim path

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

26.601.21317

What subscription do you have?

plus

What platform is your computer?

_No response_

What issue are you seeing?

Environment

• OS: Windows
• Codex version: unknown
• Install method: Codex App / CLI / VSCode extension
• Account type: Plus

Problem

When reopening a Codex conversation, Codex failed to resume the thread and showed the following error:

恢复对话失败
cannot resume running thread 019e7ed5-a438-7881-966c-a2bdf7df9ddf with stale path:
requested `C:\Users\admin\.codex\sessions\2026\06\01\rollout-2026-06-01T00-19-55-019e7ed5-a438-7881-966c-a2bdf7df9ddf.jsonl`,
active `\\?\C:\Users\admin\.codex\sessions\2026\06\01\rollout-2026-06-01T00-19-55-019e7ed5-a438-7881-966c-a2bdf7df9ddf.jsonl`
Expected behavior

Codex should normalize Windows paths before comparing them.

C:\Users\admin\... and \\?\C:\Users\admin\... should be treated as equivalent paths when they refer to the same local session file.

Actual behavior

Codex refuses to resume the thread and reports a stale path error.

Possible cause

This looks like a Windows path normalization issue involving the \\?\ verbatim path prefix.

Impact

The affected local conversation cannot be resumed normally, although new Codex conversations still work.

### What steps can reproduce the bug?

1. On Windows, start Codex and create/open a conversation.
2. Let Codex create a local session file under `C:\Users\admin\.codex\sessions\...`.
3. Close and reopen Codex.
4. Try to resume the previous conversation.
5. The resume operation fails with:

`cannot resume running thread ... with stale path`

The error shows a mismatch between:

`C:\Users\admin\.codex\sessions\...jsonl`

and:

`\\?\C:\Users\admin\.codex\sessions\...jsonl`

### What is the expected behavior?

_No response_

### Additional information

_No response_