[Bug] Antigravity still ask permission even command is already on allowed list

Google Antigravity
44

they dont fix this now. just ask an ai why they dont fix it. its to manage cost and dont have so much restrain on their servers

45

I wanted to collect some resources in a central place. In addition to this thread, there’s at least eight others on this issue

  1. Always Run doesn't always run
  2. Always Proceed" Terminal Command Setting Has No Effect
  3. Auto approvement is broken
  4. Auto Approve Broken
  5. "Always Proceed" is not working for "Terminal Command Auto Execution" setting
  6. [Bug] "Always Proceed" Terminal Auto Execution does not auto-execute commands
  7. Bug: Agent ignores default IDE shell (PowerShell 7) and Terminal Auto-Execute "Always Proceed" setting is broken
  8. Auto execution set to “always proceed” does not behave as expected

There are at least 19 extensions fixing this problem

Extension Name Download Count
YoloMode — Auto Accept for Antigravity 288144
Antigravity Auto Accept 266412
Antigravity Auto Run Pro 192055
Antigravity Auto-Accept 154821
Toolkit for Antigravity 88321
TRUEAUTOACCEPT (Official CDP Engine) 12000
Auto Accept Agent FREE 8912
Antigravity-AutoAccept (Zero-Config) 6433
Antigravity Plus 6300
Antigravity Auto Accept Super 5502
Antigravity Automation (REST/WebSocket SDK) 4211
Auto Click Antigravity (UI Automation) 3889
Antigravity Dashboard: Quota & Toolkit 3104
Antigravity Auto Accept Quack 1440
Antigravity Monitor 1112
Antigravity Pro (100 Feature Power Suite) 985
Anti Tools 712
Better Antigravity 450

This bug is incredibly trivial to fix. @Kanezal laid out exactly the issue:

Root cause: The run_command step renderer has an onChange handler that auto-confirms when you switch the dropdown, but there’s no useEffect that checks the saved policy at mount time.

// What exists (only fires on dropdown CHANGE):
onChange = useCallback(_ => {
    setPolicy(_), _ === EAGER && confirm(true)
}, [])

// What's MISSING (should fire on mount):
useEffect(() => {
    if (policy === EAGER && !secureMode) confirm(true)
}, [])

I started using Antigravity first (it’s why I bought a Google AI subscription), but given things like this issue not getting fixed, and other things, like a lack of a way to monitor your usage/quota, which has at least 18 different extensions to fix

Extension Name Download Count
Toolkit for Antigravity 88321
Antigravity Quota 88321
Antigravity Quota Watch 72104
Antigravity AI Quota & Usage Tracker 65982
Antigravity Quota Simple 42118
Antigravity Token Visualizer 38754
Antigravity Observer 21556
Antigravity HUD (Predictive Burn Rate) 15331
Antigravity Usage (Brutalist Dashboard) 11402
Antigravity Quota (AGQ) 9877
Altimeter (Token Observability) 7120
Antigravity Plus 6300
Antigravity Quota Monitor 4218
Antigravity Dashboard: Quota & Toolkit 3104
Antigravity Cockpit 1420
Antigravity Monitor 1112
Anti Tools 712

I’m just not feeling very confident in the future of this product. I hope I’m wrong.

2 Likes
46

2 months later and this hasnt been fixed. Typical

1 Like
47

Hello everyone!
Thank you for bringing the issue to our attention. Our engineering team is currently investigating the matter, and we appreciate your patience as we work toward a resolution.

48

Am I crazy? Or did 1.22.2 fix this?

49

yes they fixed it and now is my last day. i am moving to cursor

1 Like
50

Hello,

Thank you for your patience. The reported issue should now be resolved. Please let us know if you encounter any further difficulties.