Archiving problem after update

English translation:

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

Powered by Codex&OWL 26.814.41407 18.08.2026

What subscription do you have?

Plus, I currently use credits

What platform is your computer?

Edition Windows 10 Home Version 22H2 Installed on 19.09.2022 OS build 19045.7663

What issue are you seeing?

Subject: Codex Desktop Windows — error archiving local sessions after update

Hello,

After updating Codex Desktop on Windows, I can no longer archive local Codex chats. The problem occurs with several Architect chats, including chats from today and yesterday.

The chats are visible and can be opened and read normally. The error occurs only when moving them to the archive.

Exact log message:

failed to archive session: thread-store internal error:
failed to archive thread:
The system cannot find the file specified. (os error 2)

Error code: -32603
Method: thread/archive

I checked the local session files. The conversation files physically exist in dated subfolders, for example:

C:\Users\pawli\.codex\sessions\2026\08\18\
rollout-2026-08-18T15-03-22-01a014f8-27aa-7743-9cc3-c17b9cb7a229.jsonl

However, the existing local archive uses a flat layout:

C:\Users\pawli\.codex\archived_sessions\

Please check whether the current version of Codex Desktop for Windows correctly supports archiving sessions located in dated sessions\YYYY\MM\DD subfolders. The log indicates that the archiving procedure cannot find the required file even though the session file exists.

Log containing one of the errors:

C:\Users\pawli\AppData\Local\Codex\Logs\2026\08\18\
codex-desktop-3c49c65c-b065-4eaf-b19d-65f3a068a55b-8348-t0-i1-191357-0.log

The problem occurred on 18.08.2026 after updating the application.
Sign-in method: [I will fill this in]
Workspace / organization name, if applicable: [I will fill this in]

If necessary, I can provide a screenshot of the error message or point out additional log entries.

Regards

What steps can reproduce the bug?

Feedback ID: 01a015f4-18af-7171-a262-31f71c1b8e42

What is the expected behavior?

Please investigate the problem

Additional information

_No response_

<!-- codex-issue-translator -->

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

• #39239
• #39209
• #39150
• #39130

Powered by Codex Action

Update, 19 Aug 2026:

Further testing confirms that this is not limited to several older Architect chats.

At present, every local Codex Desktop conversation that I try to archive fails on this Windows installation, including both older and current local conversations.

The conversations remain visible and can be opened and read normally, but none can be moved to the archive. The error remains unchanged:

failed to archive session: thread-store internal error:
failed to archive thread:
The system cannot find the file specified. (os error 2)

This suggests that the problem affects local conversation archiving generally after the update, rather than only one legacy or resumed thread.

Update, 19 Aug 2026:

A second failure mode occurred today.

I tried to archive a newly created/current local Codex conversation immediately after creating it. The archive attempt failed. After that failed attempt, the conversation became unusable: I could no longer send messages to it, and the app showed:

thread not found: 01a0166e-1788-7881-9731-27bd9b919625

I then deleted the entire project. Project deletion itself succeeded, but its chats were not deleted: they were moved to the ungrouped/loose conversation list. Those moved conversations still cannot be archived or deleted.

So this problem now has two effects:

1. Local conversation archiving fails.
2. A failed archive attempt can leave a current conversation unusable, and deleting its project does not restore the ability to archive or delete the moved conversations.

Further update, 19 Aug 2026:

I found a project-related pattern during testing:

1. I created a completely new project and then created a new conversation in it. That new conversation archived successfully.
2. New conversations created within an older, existing project still could not be archived.
3. I attached an older conversation to the new project. It opened and otherwise worked normally there, but it still could not be archived.

This suggests that the failure is not caused simply by the current project container. It appears to remain associated with the older conversation or its original local metadata, while a newly created conversation in a newly created project can archive normally.