Users are reporting that the Antigravity desktop app suddenly shows an empty model selector or stays stuck on Loading models, often after agent failures or a short network outage. This frequently affects Apple Silicon Macs and coincides with Gemini capacity errors or regional instability.
Antigravity model list missing or stuck on Loading models on Apple Silicon
Multiple users on Apple Silicon M1 and M3 report that after earlier agent termination loops and capacity overload errors in Gemini CLI, the Antigravity app reopens with a prompt to choose a model but the list is empty or it hangs at Loading models.
Some users also note models appear on another machine while prompts cannot be sent. Others observed this right after their internet dropped briefly, after which the model list disappeared.
For persistent loader loops and blank panes, you can also review our focused reset guide here: stuck loading agent fixes.
Solution Overview
Aspect
Detail
Root Cause
Regional outage or capacity throttle on the backend plus a cached session or DNS path that keeps you pinned to a bad edge.
Primary Fix
Change your network path by tethering to mobile data or using a reputable VPN, then sign out and sign back in to force a fresh model manifest fetch.
Complexity
Easy
Estimated Time
5 to 10 minutes
Fix the empty model list now
Step-by-Step Solution
Step 1. Fully quit Antigravity
Close all Antigravity windows, then quit the app from the dock menu.
On macOS you can force close if needed:
Cmd + Q
Step 2. Change your network path
Tether your Mac to a phone hotspot on 4G or 5G, or switch to a different Wi Fi network.
If a hotspot is not possible, enable a reputable VPN to change egress and DNS.
Reopen Antigravity and check the model picker.
Users in the thread confirmed that switching internet providers or tethering immediately restored the model list. A live incident tracker also documented outages on this topic: PiunikaWeb report.
Step 3. Sign out and sign back in to refresh the session
In Antigravity, open the account menu.
Choose Sign out, then sign back in.
Open the model selector again.
If you are working inside Stitch and the project refuses to attach to Antigravity, see this fix: Stitch project not loading Antigravity.
Step 4. Flush DNS and retry
Some ISPs cache DNS aggressively. Flushing can move you off a bad edge.
Reconnect to your hotspot or VPN and reopen Antigravity.
Step 5. Clear app cache safely then relaunch
This helps when a stale manifest or token prevents the model list from populating.
Close Antigravity.
In Finder press:
Cmd + Shift + G
Navigate to the following folders and remove only Antigravity specific cache items if present. If a folder does not exist, skip it.
~/Library/Caches/
~/Library/Application Support/
Tip: Move suspect Antigravity cache folders to the Desktop first, then launch the app. If the model list returns, you can delete the moved folder.
Step 6. Restart your Mac
A clean restart clears process level socket and DNS state.
Restart macOS, connect to your alternate network, open Antigravity, and test the model list.
For deeper loader resets and agent panels that never finish, see our expanded checklist: more ways to unstick agent loading.
Step 7. Verify from another machine or user profile
Test Antigravity on a different Mac user profile or another computer on the same account.
If it works elsewhere, the issue is local to the first machine profile. Repeat Steps 4 and 5 there.
Step 8. Check for a service incident
If none of the above helps, the issue is likely a regional outage or throttle window. Try again in thirty to sixty minutes on the alternate network you used in Step 2.
Alternative Fixes and Workarounds
Use the web or CLI during an outage window
If the desktop app is down regionally, try Gemini in the browser or the CLI to confirm service health. If the CLI also returns capacity overload, wait and retry later.
Pin stable DNS
Set network DNS to public resolvers to avoid stale ISP paths, then revert after testing.
System Settings Network select your interface Details DNS add 8.8.8.8 and 1.1.1.1 apply and retry.
Update Antigravity to the latest build
Older builds can get stuck with expired tokens. Update the app, then repeat Steps 2 and 3.
For cases where Stitch is stuck connecting to Antigravity even when the model list works elsewhere, see this targeted playbook: fix Stitch not loading Antigravity.
Troubleshooting Tips
Confirm your plan is active and you have not hit a strict per minute or daily quota.
Check for aggressive firewall or DNS filtering on your router that can block model manifest endpoints.
If the issue started right after a short ISP outage, prefer a hotspot or VPN for a while, then return to your primary network later.
Try a new macOS user account to isolate profile level cache issues.
Keep a note of the exact time the issue occurred in case support requests logs.
Best Practices
Keep a trusted mobile hotspot or secondary network ready for quick failover during capacity events.
Sign out and back in periodically to refresh stale sessions.
Avoid force quitting during long running jobs to reduce cache corruption.
Update Antigravity promptly to pick up token handling and stability fixes.
Document a lightweight recovery runbook based on the steps above for your team.
Final Thought
The fastest path back to a working model list is to change your network path and refresh the session. If that does not resolve it, DNS flush and local cache cleanup usually clear stale routes until a regional incident subsides.
Read More: Antigravity stuck loading agent
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.
