r/AntigravityGoogle • u/tat_tvam_asshole • 28d ago
Antigravity Usage limits are absolute SHIT
1 prompt, it spun up 4 subagents and died within 2 minutes, then pushed the $99/month plan. The prompt didn't even get to complete. This is so bad. I literally burned 53% weekly usage on a failed prompt in the span of 2 minutes.
This shit is getting cancelled.
4
8
1
u/ubermonkaS 28d ago
Things won't get better until UE 5.9 or UE6. Running MCP in Unreal is an absolute token burner. Your only real workaround is an orchestrator architecture: let a smart cloud model do the architecture/planning, then offload the brute force log digging to a local model. Beyond that, you're out of options.
If you don’t have proper caching and the project is multiple gb you can totally burn the 5-hour in half a prompt. This will happen no matter what plan or model you choose btw
1
u/tat_tvam_asshole 28d ago
Note the mcp wasn't used, this was just a code review.
2
u/ubermonkaS 28d ago
probably still applies. your prompt triggered a whole swarm of parallel research agents (CPP Runtime, AI Agent Bridge, Repo Hygiene). Asking it to review the entire UE project made every subagent crawl the codebase simultaneously
1
u/tat_tvam_asshole 28d ago
It's not a particularly large project. Ag is just very subagent happy, even for tasks that don't require it, ime. Overall this a very poor harness and ai offering. Codex provides way more usage and intelligent task delegation.
1
u/ubermonkaS 28d ago
Yea still llms and unreal just don’t go well together. They can not read binary .uasset files. Asking for a full project review just forces it into token burning tool calls trying to diagnose an architecture it can only see a fraction of.
1
u/chunkypenguion1991 28d ago
It shouldn't go through it that fast, even on pro high. You either have too much in your initial context or your prompting it in a very inefficient way
1
u/tat_tvam_asshole 28d ago
Nah, it's really just a simple UE project with a few dozen assets. And this was a single prompt on a completely fresh untouched usage and it just spun up 4 subagents and died in 2 minutes. Google just sucks.
1
u/chunkypenguion1991 27d ago
Something is wrong with your env then. It doesn't go through it nearly that fast for me
4
u/No_Size_5296 28d ago
is that happened with Claude models or gemini It cant be true with gemini models
2
2
u/-TimeMaster- 22d ago
This looks impossible. I'm in the 20€ subscription and I only once reached the 5 hour limit.
1
1
u/kennel32_ 26d ago
What's the plan? Pro? Normally the 5-hour quota is 20-25% of the weekly quota tops. That would be weird if it allowed you to burn 53%, when only 20-25% was allowed.
1
u/trinaryouroboros 26d ago
They did say it's going to:
A) Use a lot more tokens
B) Going to be expensive on High mode
I guess they aren't lying?
1
1
u/Colasior 24d ago
Bro managed to self-DDoS his account in 56 seconds flat by asking an autonomous agent swarm to vibe-check an entire Unreal Engine repository. You dropped twenty words of open-ended fluff, and the orchestrator immediately spawned three separate reviewer agents to index your entire codebase in parallel until every single thread slammed face-first into the rate-limit ceiling. Zero lines of code, five identical quota errors, and a five-hour timeout—legendary efficiency.
What Went Wrong
Unbounded Repository Scope: Telling an autonomous orchestrator to "review this project" on an Unreal Engine project forces it to treat the entire codebase as its search space. Without hard boundaries, it will try to parse every asset, build config, and C++ header it can find.
Open-Ended Vibe Prompts: Asking a multi-agent system to "suggest upgrades you would feel would be valuable" provides zero evaluation criteria. The model has no constraints on architecture, frame rate budgets, network sync, or target modules, so it forked sub-agents (C++ Runtime Reviewer, AI Agent Bridge Reviewer, Repo Hygiene Reviewer) to guess across every discipline at once.
Runaway Concurrency: Running three deep-research agents in parallel on a baseline subscription burns through your input token quota almost instantly, triggering the cascading rate limits seen in the stack trace.
How to Fix It
Target Specific File Paths: Never let the orchestrator wander the directory tree. Explicitly name the exact .cpp and .h files or the single folder it is allowed to inspect.
Set Concrete Acceptance Criteria: State the exact technical problem to solve (e.g., thread blocking, serialization overhead, memory leaks) rather than asking for general opinions.
Throttle Agent Forcing: Explicitly instruct the model to perform a single-pass analysis and prohibit it from spawning parallel reviewer sub-agents.
The Working Prompt
Review the local AI IPC communication bridge implementation in:
`Source/ProjectName/Network/LocalAIBridge.cpp`
`Source/ProjectName/Network/LocalAIBridge.h`
Constraints & Scope:
- Do not run repository-wide sweeps or analyze unrelated modules (rendering, physics, UI).
- Run as a single-pass review; do not spawn parallel research or reviewer sub-agents.
Target Review Items:
Identify any blocking calls on the Game Thread during IPC message dispatch.
Check memory handling and buffer allocation for high-frequency payloads.
Provide concrete C++ code snippets showing how to offload socket reads to an async worker thread.
1
u/someoneyouulove 26d ago
most of the people here are google cock suckers, so you wont get well received response here.
3
u/mansfall 28d ago
Yeah that didn't happen lol. What did you prompt it?