You are hitting an HTTP 500 Internal Server Error in Antigravity for one Google Workspace user after a primary email rename. Other accounts in the same environment work, which strongly indicates an identity and token mapping issue for that specific user.
HTTP 500 only for one Workspace user after primary email rename in Antigravity
The issue presents as an immediate failure when sending prompts from Antigravity in VS Code. It only affects a single Workspace account that recently had its primary email changed. Other personal accounts and a different Workspace account succeed in the same environment, model, and prompt.
Observed environment and error
- Antigravity 1.20.5 with VSCode OSS 1.107.0 on Windows 10 x64
- Model Gemini 3 Flash
- Prompt list files
Server response captured in the Antigravity debug panel
Trajectory ID: 3c5f3b6c-c3a5-4051-bd4c-b34a428....
Trace ID: 0x83dbb94a1a4b...
Error: HTTP 500 Internal Server Error
Headers:
{
"Alt-Svc": ["h3=":443"; ma=2592000,h3-29=":443"; ma=2592000"],
"Content-Type": ["text/event-stream"],
"Date": ["Tue, 10 Mar 2026 00:28:34 GMT"],
"X-Cloudaicompanion-Trace-Id": ["83dbb94a1a4bed17"]
}
Response Body:
{
"error": {
"code": 500,
"message": "Internal error encountered.",
"status": "INTERNAL"
}
}Solution Overview
| Aspect | Detail |
|---|---|
| Root Cause | Stale OAuth grants and service entitlements cached against the user identity before the primary email rename, causing backend identity mismatch and a server side 500 on event stream creation |
| Primary Fix | Revoke third party access for the affected user at both user and admin levels, then fully sign out and reauthenticate the user in Antigravity with Gemini service confirmed on |
| Complexity | Easy |
| Estimated Time | 15 to 30 minutes |
For a related Antigravity version note, see this short v1.20.5 error handling explainer.
Fix HTTP 500 by resetting grants and reauthenticating the renamed Workspace user
Step by Step Solution
Step 1 Confirm Gemini services and licenses for the user in Admin Console
- Open Admin Console as a super admin
- Apps then Additional Google services then ensure Gemini Apps is set to On for the user’s organizational unit
- Check the user profile Licenses and confirm their plan allows Gemini access in your region
- If the user’s primary email was changed recently, add the old address as an alias temporarily to help entitlement reconciliation
Step 2 Remove stale third party OAuth grants from the user account
- Visit https://myaccount.google.com/permissions while signed in as the affected user
- Under Third party apps with account access remove Antigravity and any Google AI Studio or related entries so that fresh tokens will be issued on next sign in
Step 3 Reset app access at the admin level for a clean re grant
- In Admin Console open Security then Access and data control then API controls then App access control
- Search for Antigravity and Google AI Studio entries and remove any domain wide grants or restrictions that might be binding to the pre rename identity
- Save and wait a couple of minutes for propagation
Step 4 Fully sign out and clear the Antigravity session in VS Code
- In VS Code open the Antigravity side panel and sign out of the Google account that is shown
- Close all VS Code windows then reopen VS Code
- Reopen the Antigravity panel and sign in with the renamed Workspace email only in the browser that opens
- Ensure no other Google accounts are selected during sign in to avoid session mixing
Step 5 Test with a simple prompt on Gemini 3 Flash
- In Antigravity pick Gemini 3 Flash
- Send a small prompt for example list files
- Confirm the response streams without a 500
If you prefer to keep working while you resolve admin settings, you can also install Claude Code inside Antigravity as a temporary companion.
Alternative Fixes and Workarounds
Assign a higher tier license briefly then revert
- Temporarily assign Business Plus or a Gemini add on to the user
- Wait several minutes then test in Antigravity
- If it works consistently, revert to the intended license and retest to force entitlement refresh
Ensure the old address is kept as an alias for a period
- Add the pre rename email as an alias on the user
- Wait for directory propagation then retry authentication and prompting
Wait for directory propagation after rename
- Renames can take time to propagate across all Google identity backends
- If the above steps do not help, wait several hours then repeat the revoke and reauth steps
Use a different signed in browser profile for the reauth
- Launch the sign in flow from a clean browser profile with no other accounts present
For a broader tooling perspective, this short comparison between Claude Code and Antigravity can help you decide on a backup editor experience if your Workspace policies are still updating.
Troubleshooting Tips
- If you still see HTTP 500 collect the X Cloudaicompanion Trace Id from the headers and note the Date then share it with Google support
- Confirm the user is not blocked by Admin API controls or context aware access rules
- Verify the user can reach https endpoints for AI services without a network proxy injecting headers
- Switch models between Gemini 3 Flash and other available variants to rule out a model specific backend issue
- Check the Antigravity output panel for any silent truncation issues and review this brief note on error message truncation in v1.20.5
Best Practices
- After changing a user primary email always revoke third party app access and reauthenticate critical tools
- Keep the old address as an alias for at least a short time to allow downstream systems to reconcile identities
- Maintain a post rename checklist for admins covering licenses, service status, API controls, and app grants
- Use separate browser profiles for each Workspace account when authenticating developer tools
Final Thought
This error is almost always resolved by clearing stale grants and reauthenticating the renamed user once services and licenses are confirmed. Do the revoke at both user and admin levels then sign in fresh and your prompts should run normally again.