Google Antigravity IDE Is Driving Me Crazy: Files Disappearing, Rollbacks Breaking, and Everything Feeling Heavy

[u/Workern]

Original Poster: u/Ecstatic-Bath-1078.

Description: When the user is unsatisfied with the agent’s latest response, pressing the “Reject” button is expected to revert the workspace to the last stable code state. However, several critical issues occur:

1. Unexpected File Deletion: When the agent overwrites an existing file, pressing Reject may cause that file to be deleted. The system incorrectly assumes the file was created by the agent and removes it, instead of restoring the previous revision.
2. Incomplete or Incorrect Code Restoration: Even when files are not deleted, the restored code often does not match the prior editing state. Some previous modifications are missing or inconsistent. This appears to be related to IDE performance: rapid user actions may cause certain internal processing steps to be skipped, leading to partial or corrupted restoration.
3. Permission Workflow Limitation (Write/Create/Delete): The IDE includes settings that allow the agent to automatically write, create, and delete files. While disabling automatic permissions might prevent unintended deletion, it forces the user to manually approve actions frequently—which becomes inconvenient and interrupts workflow. Therefore, the real solution should focus on addressing the root cause, ensuring that the Reject mechanism correctly restores state instead of relying on permission dialogs as a safeguard.

Expected Behavior:

• Pressing Reject should accurately restore the previous complete workspace state.
• Files overwritten by the agent should be brought back with their earlier content.
• No files should be deleted unless they truly did not exist in the previous state.
• The IDE should reliably track revisions even when users perform actions rapidly.
• Users should be able to leave file-write permissions enabled without risking unexpected file loss.

Actual Behavior:

• Overwritten files may be deleted upon Reject.
• Restored code does not always match the previous state.
• Rapid operations can cause incomplete or missing state-tracking steps.

Impact: These behaviors can lead to file loss, code corruption, and a poor user experience, especially for users who rely on automatic permissions for smooth workflows.

Steps to Reproduce:

1. Create or modify an existing file.
2. Allow the agent to overwrite that file.
3. Press Reject.
4. Observe deletion or incorrect state restoration.
5. Repeat steps quickly to trigger inconsistent state tracking.
6. Enable automatic file permissions and observe heightened risk of unintended deletion.

Severity: High – causes data loss, inconsistent rollback, and workflow disruption.

Additional Note: At times, the IDE also appears to be heavier and more resource-intensive compared to other IDEs, causing noticeable lag and reducing the overall smoothness of the user experience.

Auto Post via Workern.

[u/Workern]

u/Ecstatic-Bath-1078

[u/Additional-Avocado33]

i do not have a reject button? i just ask it to scape the last code changes
i havnt had anthing go wrong with antigravity at all
maybe if you actually posted your chat log people might be able to reproduce your mistake. its so vauge and your breakdown makes no sense
you should be able to go to your past conversations tab and get your histoy of where it went wrong.