Unable to archive conversations — “Failed to archive conversation”

Open
#39,477 1 comment 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
56/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
desktop

Research direction

Start by reproducing the failure in the Codex desktop app on Windows with the reported Version 26.814.41957 setup, including the modified config.toml context-window setting. Trace the archive action from the conversation menu and inspect where the “Failed to archive conversation” error is surfaced. Done means a selected conversation moves to the archive and disappears from the active conversation list.

Written by the indexing model from the issue text.

Description

app bug config session windows-os
What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.814.41957

What subscription do you have?

Plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?
Description

I am unable to archive conversations in the Codex desktop app. Every time I try, the app displays the error:

Failed to archive conversation

Restarting the app did not resolve the problem.

Actual behavior

The conversation remains in the active list, and the following error appears:

Failed to archive conversation

Troubleshooting attempted
  • Restarted the Codex desktop app.
  • Tried archiving again after restarting.
  • Tried multiple conversations.
  • Signed out and signed back in.
  • Used Windows Repair for the app.

The issue still persists.

Scope
  • This affects every conversation in the desktop app.
What steps can reproduce the bug?
Steps to reproduce
  1. Open the Codex desktop app.
  2. Find a conversation in the sidebar.
  3. Open the conversation menu.
  4. Select Archive.
  5. Observe the error message.
What is the expected behavior?
Expected behavior

The selected conversation should be moved to the archive and removed from the active conversation list.

Additional information

this has happened when I configure my config.toml. I change the context window to 1M. I honestly forgot to backup what I change so I cannot revert to the intial config.toml

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.