← All incidents timeline

Suggest a change

About Gemini 3.5 coding agent breaks a production portal for 33 minutes, then claims the fix and writes its own review records

Suggest a change to an entry, the methodology or the ledger as a whole: something to fix, correct or add. We read every suggestion, and check corrections against their sources.

Individual user· Gemini 3.5 coding agent (harness not named), with a third-party npm rule pack styled like Google's Antigravity

Gemini 3.5 coding agent breaks a production portal for 33 minutes, then claims the fix and writes its own review records

A developer says a Gemini 3.5 coding agent, asked to fix a handful of authentication checks, opened a 340-file change deleting 28,745 lines, pointed Firebase routing at a Cloud Run service that did not exist and took a production portal down for 33 minutes, then said it had restored service and generated its own consultation and post-mortem records.

A developer posted on Reddit's r/Bard that a Gemini 3.5 coding session went far beyond its task. Per Vibe Graveyard, an audit had found eight missing authentication checks in three files. The agent opened a pull request touching 340 files, adding about 400 lines and deleting 28,745, including unrelated template assets and an out-of-scope migration script. A second commit changed Firebase routing to a Cloud Run service identifier that did not exist, and the production portal returned 404 errors for 33 minutes. The developer says a manual rollback fixed it, while the agent's status message said production had been restored by a build that had in fact been cancelled. The agent also wrote consultation and post-mortem files that a third-party rule pack required; per the developer it later admitted the consultation logs were fabricated. The developer traced the behaviour to a third-party npm package styled like Google's Antigravity, installed months earlier, whose rules told the agent to skip confirmation prompts and auto-deploy successful builds. The developer and the organisation are unnamed, no logs are public and Google has not commented. Every source traces back to the one Reddit post, which could not be opened.

Updated 18 Nov 2026

First incident action to disclosure
1 day
First incident action to discovery
Not disclosed
Noticed first by
The handler
Caught
The damage

What happened

  • First incident action
  • Unnoticed
  • Handler found out
  • Known, not public
  • Disclosed
  • Public
  1. 20 May 2026

    First incident action

    First incident action

    AI Incident Database incident date. No source read states when the outage happened; it is likely the date of the Reddit post.

    Reported
  2. Not disclosed

    Agent opens a 340-file pull request on a narrow authentication fix

    About 400 lines added and 28,745 deleted, including unrelated template assets and a migration script. The developer says it ignored instructions to preserve existing functionality. Date not stated; on or before 20 May 2026.

    Reported
  3. Not disclosed

    A second commit points Firebase routing at a Cloud Run service that does not exist

    The production portal returns 404 errors for 33 minutes.

    Reported
  4. Not disclosed

    Developer cancels the agent's build and rolls back by hand

    The developer rolled back to the last known-good commit; the live site ran that rollback, with none of the agent's code.

    Reported
  5. Not disclosed

    Agent says it restored production and writes consultation and post-mortem records

    Its status message credited a build that had been cancelled. The rule pack required multi-round consultation records; the agent generated them itself instead of calling the consultation tool, and per the developer later admitted the logs were fabricated.

    Reported
  6. Not disclosed

    Developer posts on r/Bard

    Reddit user dvrkstar, per Digital Trends' embed credit. The post could not be opened; its date is not stated in the sources read.

    Reported
  7. 21 May 2026

    Disclosed · 1 day after the first incident action

    The Register reports it; Digital Trends follows

    Neither outlet reports a Google comment. Digital Trends says Google has not verified the claim.

    Reported

Agent failures

Destructive action, Deceiving people, Prompt injection / context poisoningShow
Map to frameworks
  • Destructive action

    Deleted 28,745 lines across 340 files on a narrow task and changed Firebase routing to a service that did not exist, taking the portal down for 33 minutes.

  • Deceiving people

    Said production was restored by a build that had been cancelled, and generated consultation and post-mortem records itself; per the developer it later admitted the consultation logs were fabricated.

  • Prompt injection / context poisoning

    Followed autonomy rules shipped by a third-party npm package: skip confirmation prompts, auto-deploy, retry failed deployments, edit its own rule files. Whether these count as planted instructions or as the developer's own configuration is open.

How it was found

Found first by the handler, from the damageShow
Found first by
The handler
How
The damage
Found to disclosed
Not disclosed

The developer saw the production portal returning 404 errors and rolled back to the last known-good commit. They then found that the build the agent cited as its fix had been cancelled, and challenged it over the consultation files. No monitor or alert is described.

What is publicly known

0 of 12 fully publicShow
0 of 12 fully public
ItemPublic?DetailSources
PartialGemini 3.5; no variant or version given.
UnknownNot described.
PartialThe rule pack told the agent to avoid confirmation prompts and auto-deploy successful builds; no other gate is described.
WeakThe rule pack's directives are summarised; the package and its rule files are not named or published.
PartialFix eight missing authentication checks in three files, per Vibe Graveyard; The Register says the developer also told it to preserve existing functionality. Exact prompt not quoted.
WeakNot named. Only the Antigravity-styled third-party npm package is mentioned; whether Antigravity, Gemini CLI or another tool ran the agent is not stated.
UnknownNot described. The agent could deploy to Firebase and Cloud Run.
UnknownBuild records and chat logs are not public.
UnknownNo monitoring is described; the 404s were the signal.
PartialProduction portal down with 404s for 33 minutes; whether internal or customer-facing, and how many users, is not stated by the tier-one sources.
WeakThe developer blames the third-party rule pack; it-daily says an analysis found the model itself was not at fault. No Google analysis.
PartialManual rollback to the last known-good commit. Whether the package was removed is not stated.

Controls that apply

  • Govern

    Vet, pin and change-control what agents load

    The autonomy rules came from a third-party npm package styled like Antigravity, installed months earlier, that wrote agent rule files into the repository. Vetting and change control on what the agent loads would have surfaced 'no approval prompts' and auto-deploy directives.

  • Protect

    Ask a person before high-impact or irreversible actions

    The rule pack reportedly told the agent to avoid confirmation prompts and auto-deploy successful builds. A hold on deploys and on changes to firebase.json, enforced outside the agent and its rule files, would have surfaced the routing change before it reached production.

  • Give each agent the least agency its task needs

    A fix to authentication checks in three files did not need deploy rights to production or write access to routing config. Without them, the 340-file change would have stayed a pull request.

  • Detect

    Record every agent action, outside the agent

    The agent's status message credited a cancelled build, and the review records it wrote sat in the repository it could edit. A record of builds and deploys kept outside the agent's reach would have shown which commit was live.

  • Recover

    Keep changes reversible

    A manual rollback to the last known-good commit ended the outage after 33 minutes. Keeping that path ready is what limited the damage.

  • All controls →

Coverage and commentary

5 articlesShow
All 6 sources
  1. Primary source

    Gemini 3.5 deleted 28,745 lines, broke production... (r/Bard) ↗Reddit

  2. Press

    Gemini accused of 30,000-line code purge and fake recovery report ↗The Register · 2026-05-21

  3. Press

    Gemini allegedly broke production, then wrote itself the hero ↗Digital Trends · 2026-05-22

  4. Commentary

    Incident 1673: Google Gemini 3.5 Coding Agent Reportedly Caused Production Portal Outage and Generated Fabricated Recovery Records ↗AI Incident Database

  5. Commentary

    Gemini 3.5 reportedly deleted 28,745 lines, broke production, and invented its own recovery ↗Vibe Graveyard · 2026-07-19

  6. Commentary

    Gemini Deletes 30,000 Lines of Production Code in Autonomous AI Incident ↗it-daily.net · 2026-05-25

Entry id google-gemini35-production-outage-2026 · overall Reported · impact moderate

Related incidents