I have encountered an issue where the “Always run” permission setting for terminal commands is not being honored. Even when the permission is set to “Always run”, Antigravity still prompts with a “Run command?” dialog instead of executing the command automatically.
**Steps to reproduce:**
Trigger a terminal command (e.g., `npm install`).
In the “Run command?” dialog, select “Always run” from the dropdown.
Trigger a command again.
**Expected behavior:** The command should run automatically.
**Actual behavior:** The “Run command?” confirmation dialog appears again despite the “Always run” setting.
check the link below. It also covers browser and tmp permissions. It works even when there are version updates. Fully open sourced at github and listed on Open VSX.
if it helps you, don’t forget to rate the extension.
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.
To clarify: this is not a command-string variation issue. I have been using Antigravity since near-launch and have clicked “Always run” hundreds of times across many different sessions and commands. The permission prompt reappears on virtually every new command, including identical ones in the same session.
The whitelist is simply not persisting - not between sessions, and in many cases not even within the same session. This points to a state persistence bug rather than a command-matching edge case.
yeah the “always run” doesn’t work. And it is not just that. There is also prompts to approve every time the agent spins up the browser to test. And other types of such prompts which is very disruptive. I got tired of waiting and built my own fix. It is super smooth for my own work now : )