Thanks,
This is a best solution at this time. But, it could be better if we get official fixed from the Google ![]()
@Abhijit_Pramanik Can we get your attention to this case, at least we got an update/timeline from your end to fix this things.
Thx
Thanks,
This is a best solution at this time. But, it could be better if we get official fixed from the Google ![]()
@Abhijit_Pramanik Can we get your attention to this case, at least we got an update/timeline from your end to fix this things.
Thx
100% same for me. Makes it almost unusable. I donât think it was like this before, though Iâm not sure.
There is already a fix: GitHub - Kanezal/better-antigravity: The repository was created to support Antigravity from the community.
come on this bug is allready there for 2 months. If you guys didnt see it
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.
Reporting this issue in Antigravity as well, even by trying to override the config, it doesnât work.
Installed this fix. It works brilliantly! A huge thank you! Problem fully fixed!
The Better Antigravity patch worked. I couldnât get the command to run in the terminal, so I asked Gemini to run it. It didnât ask for permission to the run the command, and after restarting Antigravity, it seems to be fixed.
If I recall correctly, about a year ago Windsurf had the same problem (at least on Mac). But Antigravity was forked after that patch, unfortunately. Itâs too bad Google and Windsurf arenât collaborating to make both products better.
in v1.20.6 this issue ignored again
same issue here!
this is such an annoying issue. I get that they be safeguards, but I must be able to override them. actually the program allows to override them through the commande allow list but IT DOES NOT WORK and I keep have to approve non stop breaking my workflow all the time
great thank you ! game changer until Google decides to fix itâŚ.
if youâre still facing the permission issue, 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.
Super helpful, thank you so much!!
This is such an egregious bug and so easy to fix Iâm starting to think not fixing it is intentional because they are trying to throttle use of the AI due to resource constraints in the datacentres or worried about legal liability if the agent wipes something out with a command the user didnât sign off on.
its not working with the 27 march update but I hope you that will be changed as its still very much needed!) thanks!
thet are not going to fix it bcause of this: Autonomous agents can easily get stuck in infinite loops (e.g., trying to fix a bug, failing, and trying again forever). Since Antigravity often runs on Googleâs cloud infrastructure, an unmonitored agent could rack up massive API costs or waste server processing power in minutes. The âRunâ button acts as a manual circuit breaker.
that is also why they removed the inbox
The Antigravity client has options that allows autonomy, though the client does not listen. I have to press âRunâ manually a hundred times daily, where it should sudo