[BUG] Uncommitted work was silently lost
Resolved 💬 3 comments Opened Apr 17, 2026 by muncrief Closed May 26, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Here's what Claude said to report:
- Uncommitted work was silently lost — GTK changes were done but not committed before Qt commits went in, and nothing warned that work was about to be lost.
- API timeouts on large code generation — caused endless restart loops during the recovery work.
- The step-at-a-time workaround — small edits committed individually was the only reliable way to complete the work.
What Should Happen?
Code changes should never be silently lost. It took hours to recreate what had already been done, adding even more stress to your already overloaded servers. It was truly shocking and mind boggling when it happened.
Error Messages/Logs
There were none. It was just a complete debacle.
Steps to Reproduce
It's a big project. I couldn't possibly tell you the specific steps, or when or why it happened. As I said it was just crazy and shocking and infuriating.
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
Claude Code 2.1.112, running Claude Sonnet 4.6
Platform
Anthropic API
Operating System
Other Linux
Terminal/Shell
Other
Additional Information
I was using XFCE Terminal on CachyOS Linux with all the latest updates.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗