[Antigravity IDE] UI Bug: "Proceed in Sandbox" reverts to "Always Proceed" after closing Settings (macOS)

Google Antigravity
1

Hi everyone,

I’ve encountered a persistent UI bug in Antigravity IDE on macOS (MacBook Pro) under Settings → General:

The Issue:

  1. Macro security mode is set to “Agent security mode: Sandboxed”.
  2. I manually change the dropdown “Terminal Command Auto Execution” from “Always Proceed” to “Proceed in Sandbox”.
  3. If I close the Settings tab and immediately reopen it, it might still show “Proceed in Sandbox”.
  4. However, after leaving Settings closed for 2–3 minutes (or interacting with the editor/agent so the webview unmounts), reopening Settings shows that the dropdown has automatically reverted back to “Always Proceed”.

What I observed during live testing:

While the Settings tab remains open with “Proceed in Sandbox” actively selected, the execution engine does enforce the sandbox correctly (it prompts the user with a modal review dialog when a command requests sandbox bypass). But as soon as the view unmounts or resets, the preference is lost and resets to the macro card default.

Is anyone else experiencing this settings amnesia on macOS? Has anyone found a way to persist this preference, or is relying on explicit Deny List rules the only reliable workaround for now?

*(Attached screenshot below)

Screenshot 2026-09-09 alle 20.19.05
Screenshot 2026-09-09 alle 20.19.051954×2382 340 KB

Screenshot 2026-09-09 alle 20.19.01
Screenshot 2026-09-09 alle 20.19.011954×2382 339 KB

2

Hi @Danigame376 ,

Thank you for reporting this issue.

Could you please try the following steps:

  1. Update the IDE: Download the latest installer from Google Antigravity - Releases (view release notes at Google Antigravity - Changelog).
  2. Reset Local State: Press Cmd+Shift+P $\rightarrow$ select Antigravity: Reset Onboarding to clear any stale or corrupted client-side settings cache.
  3. Workaround: You can configure explicit rules under Settings $\rightarrow$ General $\rightarrow$ Terminal Commands (Deny List / Allow List) to ensure sensitive commands always require manual confirmation."

If you observe the issue still persists, please reach out back to us.

3

Hi @Rebbanpalli_Naveen,

Thank you for the quick follow-up. I tested both recommended steps, but unfortunately the bug persists identically:

  1. IDE Version: Updated to the latest release on macOS (Apple Silicon).
  2. Local State Reset: Executed Cmd+Shift+P → Antigravity: Reset Onboarding, followed by a full IDE restart.

Root Cause Analysis & Behavior Observed:

  • The issue is not related to corrupted onboarding cache, but rather a state serialization bug in the Settings Webview component lifecycle:
    • While the Settings tab remains active and mounted in the DOM, selecting Proceed in Sandbox does take effect in the execution runtime (commands requesting sandbox bypass correctly trigger the modal approval dialog).
    • However, as soon as the Settings tab is closed or unmounted (e.g. after ~2 minutes of inactivity when the webview is garbage-collected), the change is never committed to persistent storage (state.vscdb / storage.json).
    • Upon reopening Settings, the select component remounts with the hardcoded fallback value (Always Proceed), causing state desynchronization.

Could you please escalate this to the IDE UI engineering team as an internal tracking ticket for settings persistence?

In the meantime, I am relying on explicit Deny List rules as suggested.