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

Google Antigravity
1

I am reporting a bug where Antigravity still requests permission to run commands that are explicitly defined in the Allowed List, even with security settings set to maximum autonomy. I cannot attach images, so here are the exact details from my configuration:

The agent pauses execution to ask “Run command?” for the following command: Get-Content user-dashboard-build.log | Set-Content user-dashboard-build-utf8.log -Encoding utf8

My Configuration:

  1. Terminal Command Auto Execution: Set to Always Proceed

  2. Review Policy: Set to Always Proceed

  3. Secure Mode: Disabled

  4. My Allowed Command List explicitly includes:

    *

findstr

pnpm *

npm *

Get-Content

Get-Content *

Remove-Item *

findstr *

* *

pnpm build

pnpm build *

Copy-Item *

pnpm run build

Despite the wildcard * * and the specific Get-Content * allow rules, the agent still halts and requests manual approval for the Get-Content pipe command shown above.

Has anyone else experienced the agent ignoring the “Always Proceed” and “Allowed List” configurations?

2

100% all the time. makes it almost unusable.

3

Thank you for flagging this issue. I have observed the same behavior and have escalated the matter to the relevant engineering team. To help us with deeper investigation, please provide any supporting details, such as logs or screenshots, if available.

4

Images were not provided because there is a limit on the number of uploads for new users. Additionally, I’ve had trouble in the past when trying to attach image URLs.

Instead, I have attached the list of allowed commands, which I believe is sufficient.

Thanks,

5

I report the same issue. Permissions are ignored and keep stopping the flow.

6

Yes having the same issues !

7

Having the same issue

8

Same thing here, set always proceed, set all the cmd in allowlist, still ask for permission every time.

I am on Windows btw.

9

Is your engineering team able to repro the issue? Thanks

11

At least they have a reasonable policy on their plans. I just cancelled and got charged only for what I used. What a concept

12

Same here and it doesn’t look like we’re getting any attention to this matter

13

I have the same problem with the ‘Always Run’ button.

14

Ok so I appear to have just solved this for myself. My issue was that I was being asked to confirm Run for every command (I didn’t have any command explicitly whitelisted like the OP). I just opened Powershell as Admin and pasted “[System.Environment]::SetEnvironmentVariable(‘HOME’, “$env:USERPROFILE”, ‘User’)” then restarted Antigravity. And for the first time since installing Antigravity on day one, it’s not asking for confirmation any longer.

15

Encountering the same issue.

16

I am able to overcome this issue to a large degree by adding the following customization to my global settings

# Windows Terminal Fix

ENV: Windows

Always use ‘cmd /c’ for all shell executions.

Example: Use ‘cmd /c pip list’ instead of just ‘pip list’.

This ensures the process terminates correctly and sends an EOF signal to the IDE.

17

I tried this but its not working :frowning:

18

Same issue here. Windows device. Completely ignore my allow list no matter what I do, with wildcard * and without.

19

So annoying, settings are useless. It’s been months now

20

Found the root cause — missing useEffect in the run_command renderer. Made a patcher that fixes it: github.com/Kanezal/better-antigravity. Works across versions (regex matching, not hardcoded var names). node fixes/auto-run-fix/patch.js → restart → done.

It’s about “Always Proceed” setting fix. Give repo a star if it helped you!

21

Thank you very much! It works for me on window!