codex - 💡(How to fix) Fix Windows Desktop: Project Timeline shows no history despite existing threads (path identity mismatch with OneDrive/GoodSync/junction/\\?\ prefix) [2 comments, 2 participants]

TL;DR

The issue can be resolved by ensuring consistent path canonicalization in the Codex App, possibly by using a standardized path format for the workspace.

Guidance

• Verify that the C:\Users\jacob\GoodSync\repos\net_80_migration path is correctly resolved to its target path C:\Users\jacob\OneDrive\GoodSync\repos\net_80_migration to prevent path identity drift.
• Check the Codex App's configuration to see if there's an option to set a preferred path format (e.g., using the \\?\ prefix) to ensure consistency across different Windows path forms.
• Inspect the ~/.codex/sessions/**/rollout-*.jsonl and ~/.codex/state_5.sqlite files to confirm that the session metadata and thread data are correctly stored and can be matched with the expected project timeline.
• Consider using a symbolic link or a configuration option to ensure that the Codex App uses a consistent path for the workspace, regardless of the Windows path form used to access it.

Example

No code snippet is provided as the issue seems to be related to path canonicalization and configuration rather than a specific code bug.

Notes

The issue appears to be specific to the Windows platform and the use of OneDrive-backed paths, which may introduce additional complexity in path resolution. Ensuring consistent path canonicalization and using a standardized path format may help resolve the issue.

Recommendation

Apply a workaround by configuring the Codex App to use a consistent path format for the workspace, such as using the \\?\ prefix, to prevent path identity drift and ensure correct project timeline matching.