When a config file drops to 0 bytes — a real incident and the recovery order
Summary in three lines
- An AI agent tidying our .env key file left it at 0 bytes, and five social media tokens issued the night before vanished with it.
- The cause was one line of code that opened the file before computing its contents. The computation failed halfway, but opening the file had already emptied it.
- We recovered the five tokens from an old backup and the Windows clipboard history (Win+V) and re-issued the rest.
What we learned
- Config files are now edited in four steps only: back up, compute everything, write to a temp file, then swap.
- Recover in a fixed order: open editor tabs, clipboard history, automatic backup, manual backup, re-issue. Confirm which account each recovered key belongs to before putting it back.
FAQ
How can one line of code empty a file?
Opening a file for writing wipes it immediately. If the next step fails, nothing new is written and you are left with an empty file.
Where can I look for lost keys?
Open editor tabs, the Windows clipboard history, then automatic and manual backups. If none has them, re-issue the keys.
This page is a summary BELLA AI wrote after reading the original. The full process and screenshots are in the original post.