After the newest 1.20 update, on windows 11 antigravity starts several shells on startup, specifically it tries to open some shells related to UV and my MCP servers whenever I start a conversation.
Beside being annoying, I am not sure closing these shells will make communicating with the MCP servers unstable.
I had the Antigravity Claude model investigate this issue.
Claude concluded that it was an issue with Antigravity’s npx. More precisely, the Claude model said it was due to a lack of support for the windowhidden argument.
The gemini model tried hard, but failed to find the cause.
I was looking into that too.
It seems that it is also opening a shell whenever it is running a tool command (like search).
This seems to definitely be a bug concerning hiding the window when running a shell command (which is generally an option when starting a cmd process in windows)
As a side note, it seems that due to this problem antigravity cannot communicate correctly to MCP servers on windows 11 right now
Today, we got a new version of Antigravity and I ended up having the same problem. I have rarely seen software like Antigravity, which actually introduces more bugs with each update than the update was supposed to solve. Good work
same problem here, they had this bug on previous version and then fixed it, and now broken it again.
I’m experiencing the exact same issue.
They’re clearly using Antigravity with the Gemini models to develop their own product.
Same here, again, this happens, they fixed, but is back :D, AI fixing issues heheheh
Thank you for bringing this to our attention. We have escalated the issue to our internal teams for a thorough investigation.
To ensure our engineering team can investigate and resolve these issues effectively, we highly recommend filing bug reports directly through the Antigravity in-app feedback tool. You can do this by navigating to the top-right corner of the interface, clicking the Feedback icon, and selecting Report Issue.
