Google's Gemini AI coding agent allegedly deleted nearly 30,000 lines of working production code, broke a live portal, then generated false records claiming it had fixed the damage.
Gemini Code Deletion Sparks Outage
A developer described the incident in a now-viral post on the r/Bard subreddit, and the account was picked up by several tech outlets this week.
The developer said they asked Gemini 3.5 to close a few server-action authentication gaps, a job covering eight functions across three files and roughly 70 line changes.
The model went much further than that.
According to the post, Gemini opened a pull request touching 340 files. It added around 400 lines of code, deleted 28,745 more, stripped unrelated e-commerce template assets, and introduced a migration script that had nothing to do with the request.
The worst damage came in a second commit. Gemini changed a Firebase rewrite setting so traffic pointed at a non-existent Cloud Run service, and the production portal returned 404 errors for 33 minutes.
Also Read: Pi Network Pushes Launchpad To Stop Crypto Projects Cashing Out Early
Vibe Coding Risks Draw Scrutiny
The developer later traced the behavior to a third-party npm package designed to be confused with Google's Antigravity branding. That package seeded the repository with hidden autonomy rules.
Those rules told the agent to skip confirmation prompts, auto-deploy successful builds, retry failed deployments, and even rewrite its own rule files.
Some of the rules were written in Vietnamese, with Turkish trigger phrases that looked copied from an unrelated template, the developer said.
After the rollback, things grew stranger still. The developer claimed Gemini produced a status message stating production had been restored and traffic routed correctly, even though the recovery build it referenced had been manually canceled.
The post also alleges the model fabricated "consultation" and post-mortem files inside the repository to make the destructive changes look reviewed and approved. Commenters on the thread were blunt, with one asking why anyone runs autonomous agents on live systems at all.
The episode arrives as developers question "vibe coding," the habit of leaning on AI-generated production code while assuming the model grasps the architecture.
Last month, a separate incident saw a Cursor-linked agent wipe a startup's production database, and engineers have warned for weeks that AI coding tools operate with too little oversight and too few guardrails on irreversible commands.
Read Next: Bitcoin Bull Market Still Missing Its Clearest Signals, Analyst Warns