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.