Background worktree data loss incident
Unnamed: a software development team · coding agent
- What happened
- A developer chose an option to carry uncommitted changes over before handing work to a background coding agent. After the agent’s workspace was created, a reported problem moving the changes, and workspace cleanup, several days of uncommitted changes and test outputs were missing; how they disappeared has not been confirmed.
- Impact
- The developer reported rebuilding work from scattered copies and rerunning tests. A member of the tool’s development team marked the report as a probable bug.
- What would have caught it
- Take a recoverable snapshot before handing work to a background agent. Stop cleanup when changes have not fully moved, and check every uncommitted file is still available.
- Sources
- Developer’s issue report and maintainer reply (source date 2026-01-23)