[BUG] Problem using Gemini 3.1 With Antigravity ERROR 400

Google Antigravity
, ,
1

Since Gemini 3.1 was released I am not able to use it with Antigravity. I have latest IDE release but when I use Gemini 3.1 I obtain always this error

Trajectory ID: 69065110-551e-4675-ac40-0fbee080…
Error: HTTP 400 Bad Request
Sherlog:
TraceID: 0xebb1dabb0ce…
Headers: {“Alt-Svc”:[“h3=“:443”; ma=2592000,h3-29=“:443”; ma=2592000”],“Content-Length”:[“576”],“Content-Type”:[“text/event-stream”],“Date”:[“Fri, 06 Mar 2026 14:03:51 GMT”],“Server”:[“ESF”],“Server-Timing”:[“gfet4t7; dur=461”],“Vary”:[“Origin”,“X-Origin”,“Referer”],“X-Cloudaicompanion-Trace-Id”:[“ebb1dabb0cee5372”],“X-Content-Type-Options”:[“nosniff”],“X-Frame-Options”:[“SAMEORIGIN”],“X-Xss-Protection”:[“0”]}

{
“error”: {
“code”: 400,
“message”: “* GenerateContentRequest.tools[26].function_declarations[0].parameters.properties[max_depth].enum: only allowed for STRING type\n* GenerateContentRequest.tools[26].function_declarations[0].parameters.properties[max_depth].enum[0]: cannot be empty\n* GenerateContentRequest.tools[26].function_declarations[0].parameters.properties[max_depth].enum[1]: cannot be empty\n* GenerateContentRequest.tools[26].function_declarations[0].parameters.properties[max_depth].enum[2]: cannot be empty\n”,
“status”: “INVALID_ARGUMENT”
}
}
If I use other models everything is ok

2

Hello @Pietro_Roversi, welcome to Google AI Forum!
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.

3

I have reported the bug also using feedback tool.
Thanks

4

I have updated Antigravity but I Ihave the same problem

5

Reading this post Antigravity broken: getting only "Agent execution terminated due to error." - #421 by dev_noersy I saw that the problem is present because Antigravity use this npm package [@a-bonus/google-docs-mcp@latest ]

Updating package using npm install -g @a-bonus/google-docs-mcp@latest
problem disappear for few seconds..but after one discussion situation is the same

6

What your version? 1.20.5?

7

Yes, but I had same problem event with the previous versions

8

Hi, are you still experiencing this issue?

I’m running into the same Gemini 3.1 / Antigravity 400 error. Did you ever find a reliable fix or workaround? Also, does the issue still occur with the newer versions of Antigravity

Thanks!