Archiving a chat causes "Failed to resume chat" error and high memory usage loop

Open 💬 3 comments Opened Jun 4, 2026 by igc-svg

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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

codex-cli 0.137.0

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Windows 11 Insider Preview Build 26200.8457

What issue are you seeing?

When I archive a chat from the Codex Desktop application, the archive operation succeeds, but immediately afterwards the application shows a red error message:

"Failed to resume chat"
"session <id> is archived. Run codex unarchive <id> to unarchive it first."

The chat is actually archived correctly, but Codex continues trying to restore the archived session.

What steps can reproduce the bug?

Open Codex Desktop on Windows 11.
Open any existing chat.
Click "Archive Chat".
Wait for the archive operation to complete.
A red error message appears:

"Failed to resume chat"
"session <id> is archived..."

Codex becomes increasingly unresponsive and memory usage starts oscillating continuously.

What is the expected behavior?

The chat should be archived and the UI should return to the chat list or another valid session without errors.

Additional information

Feedback ID: no-active-thread-019e932d-0b20-7c63-b0d2-d4ce05d0c326

The chat is actually archived successfully.
The issue occurs with every chat, not only a specific conversation.
Memory usage continuously fluctuates between roughly 700 MB and 1400 MB until Codex is terminated from Task Manager.

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 2 months ago

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

#25713
#26159
#25769
#26201
#26270

Powered by Codex Action

wingcheungliu-cyber · 8 days ago

I am experiencing the same problem on Windows, and can confirm that it is not limited to one corrupted session.

Archive fails for normal existing chats/threads, and Delete also fails for normal existing chats/threads. The failure is reproducible across multiple sessions, so this appears to affect general thread management rather than a single missing or stale thread.

Expected behavior:

Archive should complete and remove the thread from the active list.
Delete should complete for a normal thread and remove it from the list.

Actual behavior:

Both Archive and Delete fail for ordinary sessions.
There is no session-specific workaround; the problem affects normal sessions generally.

Please investigate the common archive/delete path in the Windows Desktop app. I can provide screenshots, logs, and exact error messages if required.

TheWholesomeCompany · 5 days ago

@wingcheungliu-cyber Reported a similar issue on Windows desktop app (not CLI)