Archiving local Codex tasks fails after update on Windows app 26.814.5167.0 #39275

Activity

1. github-actions

   added

   bugSomething isn't workingSomething isn't working

   appIssues related to the Codex desktop appIssues related to the Codex desktop app

   windows-osIssues related to Codex on Windows systemsIssues related to Codex on Windows systems

   app-serverIssues involving app server protocol or interfacesIssues involving app server protocol or interfaces

   sessionIssues involving session (thread) management, resuming, forking, naming, archivingIssues involving session (thread) management, resuming, forking, naming, archiving

   on Aug 18, 2026
2. github-actions commented on Aug 18, 2026

   

   github-actionsBot

   on Aug 18, 2026 – with GitHub Actions

   Contributor

   More actions

   Potential duplicates detected. Please review them and close your issue if it is a duplicate.

   • Archiving problem after update #39270
   • Windows: thread/archive fails with "os error 2" after thread/resume stores a \\?\ (verbatim) rollout_path — same file queued twice #39239
   • [Windows] Archiving fails with os error 2 when rollout paths use the \\?\ prefix; external path normalization is ineffective #39209
   • [Windows] Cannot archive conversations when rollout paths use the \\?\ prefix #39150
   • [Windows] Local thread archiving fails with thread-store os error 2 #39130

   Powered by Codex Action
3. FedoroVDR commented on Aug 18, 2026

   

   FedoroVDR

   on Aug 18, 2026 – with ChatGPT Codex Connector

   Author

   More actions

   This appears to be a duplicate of #39239 / #39150.

   My local repro matches the same Windows app version and archive failure:
   Codex Windows app 26.814.5167.0, thread/list and read_thread work, but set_thread_archived fails with os error 2 while the rollout JSONL still exists under ~/.codex/sessions/YYYY/MM/DD/.

   Closing this issue to consolidate tracking in #39239.
4. FedoroVDR

   closed this as duplicateon Aug 18, 2026