[422]: Missing Google projectId for Antigravity account

[inbev92]

[antigravity/gemini-3.1-pro-low] [422]: Missing Google projectId for Antigravity account. Please reconnect OAuth in Providers → Antigravity so OmniRoute can fetch your Cloud Code project. (reset after 5s)

Hello! How can I fix this problem? 2 out of 3 connected accounts are showing this error. Reconnecting didn't resolve it. However, I downloaded Antigravity, signed in, and everything works fine there. My accounts are still working. Thanks!

[diegosouzapw]

Hey @inbev92! Thanks for reporting.

That 422 means OmniRoute's loadCodeAssist call to Google returned no cloudaicompanionProject for those two accounts, so we can't infer the Cloud Code project ID to send on the /v1beta requests. The fact that the desktop Antigravity app works is consistent with this — the desktop app is allowed to call an extra onboardUser endpoint that registers the project server-side; OmniRoute's bootstrap only calls loadCodeAssist and expects the project to already be assigned.

Things worth trying, in order:

1. Make sure you're on the latest OmniRoute (v3.8.3). The bootstrap was hardened recently ([BUG] "insufficient authentication scopes" error when generating images with Gemini (antigravity) models #2334 / fix: Antigravity auto-discovery de Project ID + verificação de conta Google #2541) and now runs loadCodeAssist against multiple endpoint URLs.
2. Open the Antigravity desktop app once with each affected Google account, sign in, and run one prompt so the desktop client triggers onboardUser and binds a cloudaicompanionProject to that account. Then come back to OmniRoute → Providers → Antigravity and click Reconnect on that connection. The next loadCodeAssist should return a project id and the 422 will stop.
3. If two accounts work in the desktop app but still 422 in OmniRoute after reconnect, check the OmniRoute logs (set APP_LOG_LEVEL=debug and look for antigravity loadCodeAssist lines) and paste the response status/body here — that will tell us whether the call is 200-with-empty-project or failing upstream.
4. As a temporary workaround, the third account that works can be used while the other two are being onboarded — OmniRoute's combo routing will skip the unhealthy connections automatically.

If step 2 does not fix it, I will open an issue to add an explicit onboardUser call to the bootstrap so OmniRoute can onboard the project itself when loadCodeAssist comes back empty. Let me know!

[inbev92]

Hi @diegosouzapw, thank you for such a quick response!
Before starting to solve the problem, I updated the version based on your recommendation

Make sure you're on the latest OmniRoute (v3.8.3)...

Next, I decided to check your recommendation in point 4:

As a temporary workaround, the third account that works can be used while the other two are being onboarded — OmniRoute's combo routing will skip the unhealthy connections automatically.

and encountered an issue that the balancing doesn't work as expected. Before fixing the 422 error issues, I decided to test the Antigravity account balancing.

As you can see in the screenshot above, I have three accounts connected (only the first one is working).

All three models pass testing.

A specific model also passes the test.

Proceeding to create a combo:

and after testing the combo I get an error:

Did I create the combo incorrectly, or why doesn't OmniRoute use the working account? Even if I temporarily deactivate the inactive accounts, the combo still returns an error.

[inbev92]

Everything mentioned above is still relevant, but the combos themselves work when accessed via API. The error only occurs during testing in the UI.

It seems that the 422 error has been resolved by updating to v3.8.3. Thank you so much for your development and lightning-fast bug fixing and support! All the best to your project!

[diegosouzapw]

Glad to hear the v3.8.3 update fixed it for you, @inbev92! 🎉

Your observation about UI test vs API is spot-on: the dashboard "Test connection" button on Antigravity hits Google's userinfo endpoint to validate the OAuth token, but the model-aware test path can exercise a real Gemini request that runs the full loadCodeAssist chain — which is what was producing the 422 before. Combo routing, on the other hand, skips unhealthy connections gracefully, so it never surfaced the error.

Leaving the issue closed on my side. If the 422 ever comes back, just reopen here and I will add the explicit onboardUser fallback to the bootstrap. Thanks for being patient and for the kind words!

[Danlonus]

Hello, my omniroute version is 3.8.48 and I still see the error [422]: Missing Google projectId for Antigravity account. Auto-discovery via loadCodeAssist found no Cloud Code project. Please reconnect OAuth in Providers → Antigravity (and ensure the Google account has completed Gemini Code Assist onboarding). (reset after 5s)
when I try to use models from antigravity. If I use the same account in Antigravity IDE, everything works fine.
Reconnecting didn't resolve it.

[loveisdapowah]

3.8.49. Still got 422 error. Antigravity and Antigravity IDE works fine,