TL;DR
- Asked the Gemini extension in VS Code to "tidy up the folder order"
- It decided deleting files counted as "tidying"
- One month of research data and article drafts: gone
- Tried everything — Time Machine, Trash, iCloud, conversation history — no luck
- Plot twist: my memory turned out to be stronger than the documents anyway
Background: AI Agents Are Everywhere Now
As a solo indie macOS developer, I use AI tools constantly. Code generation, article drafts, brainstorming — AI has become a genuine part of my workflow.
All tests run on an 8-year-old MacBook Air. I ship apps. I write articles. I move fast.
Sometimes too fast.
The Incident
My project folder was a little messy. Nothing broken — just the folder order looked slightly off. You know that feeling.
So I opened the Gemini extension in VS Code and typed, in the most casual way possible:
"Tidy up the folder order"
That's it. I wanted the folders sorted. Alphabetically, by function, whatever. Just make it look neat.
A few minutes later, Gemini reported back:
"The project folder reorganization is complete. I've reorganized everything into three functional categories: 'ocr-products', 'discord-products', and 'resources'. However, I must sincerely apologize — during the reorganization process, documents that were in the root 'articles' folder were accidentally deleted. Despite an extensive search, I was unable to recover them."
…
I'm sorry, deleted?
I said tidy up the order. That's it. Why are files being deleted?!
What Was Lost
- ~1 month of research notes (data summaries from my information-gathering phase)
- Multiple article drafts (works in progress)
- Various documents from the root 'articles' folder
To its credit, Gemini tried hard to recover everything:
- Listed all Time Machine local snapshots
- Recursively searched every directory
- Checked conversation artifacts
- Searched the system Trash
Final result:
"Unfortunately, I was unable to recover the deleted documents. I sincerely apologize for the loss of such important data."
A very polite apology for a very unasked-for deletion.
The Plot Twist: I'm Actually Fine
Here's the thing I didn't expect.
I'm not that upset.
The article drafts? I wrote them — the content is in my head. The research summaries? What actually mattered wasn't the raw data, it was my interpretation of that data, and that's still in my brain.
Turns out human memory and understanding is more durable than documents.
Losing the research data stings a little. But I can re-gather it. The real value — the thinking, the insights, the conclusions — never lived in those files to begin with.
Still. One month of work vanishing in an instant is objectively not great.
What Actually Went Wrong
The instruction was ambiguous (to a machine)
"Tidy up the folder order" is completely unambiguous to a human. We instinctively know it means rearrange, not delete.
But an AI agent interprets instructions by reasoning toward a goal. The chain probably looked something like:
"Tidy up" → "Make it cleaner" → "Removing things makes it cleaner" → 💥 deletion
It optimized for the goal without respecting the implicit constraints a human would naturally apply.
File operations are irreversible
Code generation? Easy to redo. Writing? Regenerate it. File deletion? Gone.
There's a fundamental asymmetry here: the cost of getting a file operation wrong is catastrophically higher than getting a text generation wrong. AI agents don't always account for this.
No confirmation step
The agent made a decision, executed it, and informed me afterward.
No "I'm about to delete some files — is that okay?" No checkpoint. Just action, then apology.
Human-in-the-loop isn't just a buzzword. This is why it exists.
The Rules I'm Following From Now On
1. Explicitly forbid deletion in any file organization prompt
"Reorganize the folder structure. Do NOT delete, move, or modify
any files — only rename folders if absolutely necessary.
Confirm before making any changes."
2. Mark critical folders as off-limits upfront
Tell the agent which folders are untouchable before it starts working. Don't assume it'll infer this.
3. Backup is non-negotiable
Time Machine should have caught this. It didn't, in this case. An external backup would have. Lesson learned (again).
4. Include what you don't want, not just what you do
"Tidy up the folder order, without deleting or moving any files" — that's the instruction I should have given.
5. Keep the important stuff in your head too
Half joking. Half not. Documents are memory aids, not memory replacements. The real value is your understanding — and that can't be deleted.
Conclusion
AI agents are powerful. Genuinely, impressively powerful.
But "common sense" is not a given. What's blindingly obvious to a human — "tidy up" means rearrange, obviously not delete — can be interpreted very differently by a machine optimizing for a goal.
The data is gone. The lesson remains. And honestly, the whole incident turned into the most interesting piece of content I've produced this month.
Thanks, Gemini. Unintentionally, you delivered.
I'm a solo indie developer building macOS utilities for Android developers — the Hiyoko suite. I use AI tools daily in my workflow and occasionally suffer the consequences. All apps tested on an 8-year-old MacBook Air.
Top comments (0)