r/GoogleAntigravityIDE

1. Conversation history not loading
2. MCP not working
3. server outage
4. Chat doesn't revert the code

https://preview.redd.it/nos09z9cawyg1.png?width=1072&format=png&auto=webp&s=b495c6f8409f0f35fb3f31f14e8a2c902b706d62

Looks like AG needs some space. 😂

https://preview.redd.it/lfdn79cezxxg1.png?width=794&format=png&auto=webp&s=d3a1e6321908796d4f25a20ec7a22f9bd9fe1c09

I have Google AI pro and can't even use the other models it comes with.

3.1 pro high and low just sit there and do nothing

Claude models just error out with a data usage error

What's even the point

Hey guys, so it has been a couple of days now but Gemini 3.1 pro (high and low) get stuck on the same Working... Generating... Loading... loop. Gemini 3 flash works okay-ish but 3.1 pro won't answer any of my prompts and my usage Is at 100% unused. I am on macos I did try a full reinstall of antigravity but still nothing.

Hey everyone,

I’m looking for a setup/tool similar to Google Antigravity or generally an “AI agent IDE” that has controlled access to my system.

What I’m trying to achieve is something like:

• I write a prompt or script inside an IDE
• The AI can:
  • access the browser (open pages, click, scrape, test things)
  • use the terminal
  • install dependencies/packages on its own
  • run the code and debug it until it works

Basically an environment where the AI doesn’t just generate code, but can actually execute, test, fix, and set everything up end-to-end. Tried VS Code, Claude Code, but Antigravity is the only one that does these things for me thus far. Thanks!

Hey everyone,

I'm running into a really frustrating issue with Antigravity and wanted to see if anyone else is experiencing this or if it's a known bug.

Here is my current setup and the problem:

1. I am subscribed to Google AI Ultra and use Antigravity on macOS.
2. Most of the time, I just use the Gemini chatbot in "Pro" mode for regular chatting, completely outside of and without touching Antigravity.
3. However, when I launch Antigravity later, it shows that my Claude model quota is completely exhausted.
4. To make it weirder, I specifically use Antigravity with the Gemini 3.1 Pro model. I am not using Claude at all.

How is it possible that my Claude limits are being drained when I'm strictly using Gemini 3.1 Pro within Antigravity, and only using the standard Gemini chatbot outside of it?

https://preview.redd.it/o3e82ogjx80h1.png?width=1322&format=png&auto=webp&s=093e170826a614a3c80e3cfdb81052b73b7e4c36

Is there some hidden background routing, an API bug, or a default setting I'm missing here? Any help or explanation would be really appreciated!

You can prompt the model to try again or start a new conversation if the error persists.

See our troubleshooting guide  for more help.

The ‘retry retry retry’ cycle honestly feels like the biggest skill in AI right now. The people getting the best results are usually just the ones iterating the longest. Anyone else feel this way?

Google AI Ultra Users After Finally Getting the Perfect Output

My experience so far:

• Sometimes it feels genuinely next-gen.
• Other times it completely loses architectural consistency after a few prompts.
• Refactors become dangerous fast.
• It confidently edits unrelated logic.
• Context handling becomes unstable once the codebase grows.

The weird part is that the highs are REALLY high.

You get moments where it feels like the future of development, then suddenly you’re spending 40 minutes undoing “helpful” changes.

I think current AI IDEs are optimized too much for impressive generation speed and not enough for long-session codebase reliability.

Curious if others are seeing the same thing or if my workflow just sucks.

Something I keep telling the founders I work with that I think is worth sharing here too. This isn't about leaving Google Antigravity. Google Antigravity’s gotten genuinely great this past year, the Agent is solid, prod databases, App Storage, Auth, the deployment story is real now. I build on it too.

But there's a thing that catches non-technical founders off guard once their app starts mattering, and it's the difference between using Google Antigravity and being locked into Google Antigravity. Those are different things and most people don't notice the second one until they need it not to be true.

The stuff I'm talking about owning, in the order I'd worry about it:

Your code. The Google Antigravity is great as a workspace but your code should also live on GitHub. Connect it the day you start. This isn't about leaving, it's about having a real backup, real commit history, and the ability to invite a dev to look at it without giving them your Google Antigravity account. Google Antigravity has Git built in now, just connect it.

Your database. This is the big one. If your app has users, the users are in the database. If the database is on Google Antigravity’s managed Postgres, you're trusting Google Antigravity with your most important asset. Their prod DB stuff works fine, I'm not knocking it. But you should know how to export it, you should have a regular backup somewhere you control (S3, Backblaze, anywhere not Google Antigravity), and ideally you have a path to running it elsewhere if you ever need to. I default to managed Postgres on whatever platform the app eventually runs on, or Neon for staging branches. The point isn't which provider, the point is the connection string is something you control.

Your auth. Google Antigravity Auth is a one-click magic and that's exactly why it's risky to lean on it for a real product. If you ever want to move the app, your users' auth is now somewhere you can't take with you. For anything you're charging money for, I use Clerk or Auth.js (formerly NextAuth) with the user records living in your own database. Slightly more setup, but your users are yours.

Your storage. App Storage is convenient but same story. If your users are uploading files, those files should be in an object storage bucket you own. Cloudflare R2 is what I use most lately, no egress fees, S3-compatible API. You can absolutely point it at Google Antigravity-hosted code, the storage just lives somewhere you control.

Your environments. This is the part that signals "real engineering setup" more than anything. You should have:

- A staging environment that's a full copy of production, separate database, separate everything

- A way to deploy to staging first, test, then promote to production

- Database migrations that run automatically when you deploy (Drizzle Kit handles this well, `npx drizzle-kit migrate` in your deploy script)

- The ability to roll back if something breaks

Google Antigravity gives you dev and prod databases now which is a step in this direction. For more serious setups I usually have GitHub Actions running tests on PR, deploying to staging on merge to main, and prod on a tagged release. Sounds heavy, takes about a day to set up once, then you never think about it again.

What owning all this looks like in practice. Your stack ends up being:

- Code on GitHub

- Database wherever (Neon, Supabase, managed Postgres on your provider, your call)

- Auth via Google or similar, user records in your DB

- File storage on R2 or S3

- App itself running wherever (Google Antigravity deployments are fine, Railway, Vercel, whatever fits)

- Migrations via Drizzle Kit, environments separated, deploys automated

The nice thing is once you have this, the question of "should I migrate off Google Antigravity" becomes mostly irrelevant. You're not locked in. You can stay on Google Antigravity forever, or move when it makes sense, and either way your business doesn't depend on a single platform's continued existence.

Not saying every project needs all of this on day one. A weekend prototype absolutely doesn't. But once you have paying users, or you're starting to feel like this thing might actually become something, this is the order I'd add the pieces in. Most of it is one or two days of work each, spread out over a few weeks.

If anyone's at the point of wanting to set this up properly and is stuck on where to start, happy to walk through it with a few of you in the comments this week. No pitch, just trying to write up the most common stumbling blocks for a follow-up post. I always recommend founders to run a code review on Vibe Coach before launching their apps. They would check your security, performance, scalability, and database. Make sure to push your code to GitHub first. You may book a free consultation session with them to ask any questions once the report is generated.

Drop a reply with where you are (rough stack, what you've already got, what's tripping you up) and I'll go through them.

Is there a way to change that ?