Hi Antigravity team,
First — thank you for the unban announcement and the new remediation pathway. That was the right call and I appreciate the transparency.
I’d like to raise a use case that I think affects more users than just me, and propose a feature or policy path forward.
My situation
I’m a developer based in Ukraine. The war has made professional mental health support largely inaccessible — financially and logistically. As a developer, I did what made sense: I built a personal self-help assistant for stress management and reflection. It’s not a product. It has zero users besides me.
For this assistant, I had been using Claude Sonnet/Opus via a separate Anthropic subscription — those models work particularly well for open-ended reflective conversations. But given the financial pressures of living through a war, I was looking for a more affordable option and wanted to evaluate Gemini as an alternative. Antigravity’s subscription seemed ideal.
The problem: this assistant requires custom agent logic — tool use, MCP integrations, file read/write. The official Antigravity IDE doesn’t provide a way to define and run user-controlled agents with these capabilities outside of a development project context. That’s why I turned to opencode, which led to the ToS ban.
I understand why the ban policy exists, and I’m not challenging it. But I want to raise a real gap.
The gap
Antigravity markets itself as a platform for agents. But right now, the only supported workflow is: agent helps you build software. There’s no supported path for a developer who wants to use the same models and subscription to build and run a personal agent for their own life — not as a product, not as a service, just for themselves.
The Gemini API would technically support this, but it’s out of reach financially for many users in my situation. The Antigravity subscription is the only affordable entry point.
What I’m asking for
One of the following would solve this:
- A “Personal Agent” mode — allow users to define and run custom agents (with tool use / MCP / file access) within the Antigravity subscription, outside of a development project context
- Official opencode / third-party CLI support — a whitelist or certification path for open-source CLIs that respect rate limits and ToS
- Clarity on the roadmap — are any of these planned? Even knowing it’s coming in 6 months would help me plan
I’m happy to stay within official tooling — I just need a path forward that’s actually viable.
Thanks for reading. I suspect I’m not the only developer who would benefit from this.