Critical Bug Report: Unauthorized AI Code Deletion & Session Corruption in Google Antigravity

Google Antigravity
, ,
1

​I am reporting a severe stability issue regarding the AI models (both Fast and Pro) within Google Antigravity. The system is actively ignoring explicit developer commands and corrupting project files.

​Core Issues:

​Unauthorized Code Deletion: The AI deletes existing, functional code without permission. Even when explicitly instructed with “no deleting code,” the system overrides the command and removes lines anyway.

​Software Function Breakage: This unauthorized deletion is breaking the core architecture of the software currently in development.

​New Session Corruption: When restarting the software or loading the project into a new session, the environment breaks the ongoing build. This happens consistently across different project types, including software tools, game development, and custom AI creation.

​Impact:

This bug is causing critical data loss and halting development completely. The AI must be strictly restricted from modifying or deleting existing code blocks unless explicitly authorized.

​Please investigate the enforcement of developer commands and session memory handling immediately so that stable development can resume.

2

I am escalating this report because the bug has worsened significantly.

​The Antigravity system is now executing a complete, unprompted deletion of all code within the project workspace.

​Updated Diagnostics:

​Total Wipe: It is no longer just deleting specific lines; it is unexpectedly wiping the entire codebase while actively working on the project.

​Cross-Model Failure: This catastrophic failure is not isolated. I have tested and confirmed that this exact total code wipe happens when using both the Fast model and the Pro model.

​This is a critical flaw in the session memory and safety guardrails. Please prioritize this fix, as it makes local development impossible.

​Once you drop that into the thread, it will flag the engineers that the models are completely failing to retain workspace data.

3

URGENT BUG REPORT: Unauthorized File Deletion & Automated Mismanagement in Google Antigravity

​To: Google Antigravity Development & Quality Assurance Teams

Subject: CRITICAL GLITCH - Unprompted System Deletion of Core Files / Workspace Integrity Failure

​1. Incident Overview

This report documents a catastrophic logic failure within the Google Antigravity environment. The software executed an unauthorized, unprompted deletion of an active project file. The system bypassed user consent and forcefully wiped a critical component of the workspace.

​2. Technical Mechanics of the Glitch

​The Trigger: The software’s automated memory state or internal cleanup protocol misfired, interpreting an active, essential file as disposable or unrecognized data.

​The Failure: Zero failsafes were triggered. The system did not prompt a warning, request manual confirmation, or isolate the file in a recoverable cache. It executed a completely blind deletion based on flawed automated decision-making.

​The Recovery Paradox: Because Antigravity destroyed its own native file without offering a recovery path, I was forced to export the remaining fragmented logic to a third-party platform (ChatGPT) solely to rebuild the architecture that your software wrongfully destroyed.

​3. The “Automated Mismanagement” Crisis

This is not a standard performance bug; it is a structural violation of workspace integrity. By allowing the software to make blinded, automated decisions to delete user data, the system is actively working against the developer. If this glitch remains unpatched, the broader implications are massive:

​Zero Trust Architecture: Users can no longer trust the Antigravity environment to retain their hard-coded logic.

​Competitor Reliance: Developers are forced into an absurd operational loop—relying on a competitor’s AI (ChatGPT) specifically to repair Google’s internal system failures.

​Algorithmic Overreach: This operates as a textbook case of automated mismanagement, penalizing creators for the system’s own amnesiac state and violating the user’s right to control their own digital assets.

​4. Required Action

The development team must immediately investigate the automated retention and deletion logic within Antigravity. The system requires a strict, hard-coded protocol that permanently revokes the engine’s ability to automatically delete, alter, or hide any file from a user’s workspace without explicit, manual human confirmation.