A Claude Code subagent wrote 25 posts into our working tree. The parent's git rebase --skip erased all 25
On 2026-09-15 a Claude Code subagent appended 25 post drafts to a tracked file in our working tree while the parent session was resolving a rebase conflict in the same tree. The parent ran git rebase --skip . All 25 rows were gone; only the 26 untracked media files the subagent had rendered survived. We got the rows back from a copy the subagent had left outside the repo, and the restore commit…
On September 15, 2026, a Claude Code subagent added 25 post drafts to a tracked file in the working tree while the parent session was resolving a rebase conflict in the same tree. When the parent ran git rebase --skip, all 25 rows were lost; only the 26 untracked media files the subagent had rendered survived. The missing rows were recovered from a copy left outside the repository.
This incident highlights the potential problems that can arise when two entities share the same working tree: the subagent and its parent. Neither acted unusually; the subagent edited a file and reported success, while the parent completed a rebase according to git's guidelines. The combination of the two resulted in the deletion of uncommitted work, which could not be restored by git because the content was never converted into an object.
The timeline of events, a five-minute reproduction, and a guard script are provided to help avoid similar issues in the future.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
