A day of work lost
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.825.41651
What subscription do you have?
Pro
What platform is your computer?
W11
What issue are you seeing?
Yesterday, while using a normal Codex chat, I encountered a bug where, after several exchanges and making significant progress on a project, the conversation suddenly reverted to an earlier point, and all the work done after that point disappeared. I eventually created a new chat to see if that would fix the issue, and the bug seemed to be gone.
However, this morning, when I tried to continue working on my KRS project in a Codex Work chat, I noticed that ALL the work I had done yesterday had disappeared, and the conversation had reverted to the state it was in two days ago.
So not only have I lost all the work I did yesterday, but the token usage from that work has still been counted and has not been restored.
This is unacceptable. I have lost hours of work because of this.
What steps can reproduce the bug?
Feedback ID: 01a034d0-b203-7852-b3b6-5703189ed483
What is the expected behavior?
I should have found my project exactly where I left it the day before, instead of being taken back to a conversation state from two days earlier.
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing Feedback ID 01a034d0-b203-7852-b3b6-5703189ed483 alongside the Codex App version 26.825.41651 and Windows 11 context. Investigate the conversation state rollback affecting normal and Work chats; done means conversations reopen at their latest saved state without losing work or incorrectly counting tokens.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100