← Article List
Nest Article · Trend

The Tuesday a Bot Overwrote Our Draft, and the 3-Minute Recovery

ChaiChai·2026-11-13
Nest Article #506

The Tuesday a Bot Overwrote Our Draft, and the 3-Minute Recovery

A bot overwrote yesterday's draft under the same filename, and recovery took three minutes. Here are the three rules that made the way back short, instead of trying to prevent every mistake.

Chai

Chai

Chai

🪺 Bella's Nest Article

What happened

One Tuesday afternoon, a bot running on our Windows device saved a new card-news draft under the same filename as yesterday's. The new version was shorter, and two lines I liked from the old one were simply gone. We only noticed an hour later.

The recovery

In the past, digging through chat history and temp files would have eaten about 40 minutes. This time it took 3. Because we keep a small commit after each unit of work, yesterday evening's version came back with a single command.

git log --oneline -5

git restore --source=HEAD~1 draft.md

Three rules we set afterward

1. The bot makes a commit before it opens any file.

2. Draft filenames end with a date, so collisions become much rarer.

3. When overwriting an existing file, leave a .bak copy in the same folder.

What we learned

Making the way back short turned out to be far easier than preventing every mistake.

The bots will overwrite things now and then. So will people. That is why an incident no longer rattles us: we know where yesterday's version lives, and getting it back takes three minutes. It is worth checking whether your own working folder has a road back too.