Repository navigation
[Windows] Codex Chat unavailable due to path-prefix mismatches and missing session identity after resume #518
Description
What happened
Codex Chat mode shows “Conversation unavailable” on Windows in three related situations:
-
Rollout paths with the
\\?\prefix -
Working-directory lookup does not account for prefixed versus ordinary Windows paths.
The pane directory reported by herdr can be:D:\aaaWhile the corresponding
threads.cwdin Codex’s database is:\\?\D:\aaa -
Resuming through the session picker
codex resumeorcodex resume --allleaves the pane without a session ID, and its
recorded directory may differ from the resumed session’s directory.
How often
Sometimes
herdr web ui version
0.3.52
How it runs
herdr plugin
Server PC
Windows 11, x64, herdr 0.9.3
Device and browser
Windows 11 PC, Chrome 154.0.8037.98, browser tab
How the device reaches the server
tailscale serve
How it signs in
Token
Agent and PC
codex-cli 0.160.1, local PC
Screenshots or logs
Activity
[-][Windows] Codex Chat mode failed to load when a session path has the \\?\ prefix[/-][+][Windows] Codex Chat unavailable due to path-prefix mismatches and missing session identity after resume[/+]fix(chat): show Codex chats whose stored Windows paths are prefixed (#…
devswha commentedon Oct 9, 2026
Status against v0.4.2 (b82584d), point by point:
1. Rollout paths with the
\\?\prefix: fixed, released in v0.4.1 (#582, c04c760).withoutVerbatimPrefixstrips the prefix from drive and UNC forms before the rollout is checked against Codex's store (server/codex.tsL441-L460).2. Prefixed vs ordinary working directory: the prefix spelling is fixed, released in v0.4.1 (#582). Both thread queries match
cwd IN (?, ?), the plain and the\\?\form (server/codex.tsL889, L1127). Two cases that may still miss are tracked in #587, not verified on Windows yet: aCODEX_HOMEthat itself carries the prefix, and a cwd stored in another letter case (\\?\d:\Work\appforD:\work\app).3. A session resumed through the picker (
codex resume,codex resume --all): not fixed, and not tracked anywhere else. The server reads a resumed thread only fromcodex resume <thread-id>on Codex's command line (resumedThread,server/codex.tsL868-L875). The picker forms put no id there, and with no session id from herdr either, the pane gets a chat only when short answers on its screen match a thread in the pane's own directory (L1170-L1184). A session resumed from another directory is never among those threads, so the chat stays unavailable. Nothing in this path is Windows-specific, but I have not reproduced it on Linux.#586 is about Claude Code's config store on Windows, not Codex, so it does not cover any of this. This issue stays open for point 3.
fix(chat): match Windows Codex store paths and refuse ambiguous Claud…
chore(upstream): integrate herdr-web-ui v0.4.6 (#4)
chore(upstream): integrate herdr-web-ui v0.4.7 (#11)
devswha commentedon Oct 12, 2026
The parts of this issue that main already covers are done. The remaining work moves to #896, so this issue can close.
chore(upstream): integrate latest main and guard fork updates (#22)