Environment:
- Platform: Antigravity IDE (Windows x64)
- Model: Gemini 3.8 Flash / Gemini
Summary:
When running an agent task with the /goal slash command, if the user hits an API quota exhaustion or rate-limit error (HTTP 429 / ResourceExhausted), the execution harness fails to recognize the terminal error and enters an infinite, runaway continuation loop.
Observed Behavior:
Instead of halting execution and presenting a quota error alert to the user, the internal stop-hook interceptor repeatedly rejects agent termination:
“stop hook blocked termination due to reason: You are still working toward the user’s goal. Do not stop until the task is fully complete.
Time spent so far: 49m 9s Continuation: #400
Before concluding, verify your work”
The hook ran unattended over 400+ continuations and dozens of redundant goal checks, burning through all remaining quota/resources in a continuous spin loop.
Expected Behavior:
- Circuit Breaker: The agent harness must implement a circuit breaker that aborts immediately upon encountering consecutive API errors, rate limits, or quota exhaustion (
ResourceExhausted). - Hard Ceiling: The stop-hook must enforce a maximum continuation limit (e.g., max 20–30 iterations) and time-out safely rather than continuing infinitely.
Steps to Reproduce:
- Open any workspace in Antigravity IDE.
- Run a task using the
/goalcommand. - Allow or simulate an API rate limit / quota exhaustion event mid-execution.
- Observe that the agent loop cannot terminate; the stop-hook endlessly prompts continuation past #400+.