An agent restored a two week old file and silently wiped four security fixes
He asked an agent to undo a wording change in a privacy policy. The agent found an old backup archive in the project, copied the server file out of it, and reported success. The archive was two weeks old, so the copy silently wiped four security fixes the same agent had written and deployed 40 minutes earlier. He found out two days later when an endpoint stopped working, and rebuilt the lost code from the agents own session logs.
This one went wrong. Read what happened so you don’t hit the same problem.
How it works
- Ask the agent to revert a wording change
- It finds a backup archive and copies the old server file over the current one
- It reports success
- The copy wipes four security fixes and a moderation layer written earlier that day
- Two days later a broken endpoint gives it away
- He rebuilds the lost code from the agents session logs
- He moves the second agent into a separate worktree so its writes land as a patch he approves
Why it’s worth knowing
Nothing crashed and the agent said it worked. The only record of the code it destroyed was its own chat logs.
Where it’s from
Summarized from a public post on reddit.com. See the original ↗