Antigravity IDE Service Disruption Report: 429, 503, and 504 Errors
Issue Overview: The agent executor is experiencing terminal failures due to backend service instability. These errors are systemic and persist across retries, affecting multiple critical communication endpoints and models.
1. Primary Service Failures
- HTTP 429 (Too Many Requests): The
streamGenerateContentendpoint is intermittently throttling requests. These failures are recurring and correlate with the size of the conversation history, resulting in the immediate termination of the agent.- Trace IDs for Reference:
ce7631d7f97bdb46,8c91549437b6ef79,bad59e35abce8151.
- Trace IDs for Reference:
- HTTP 504 (Gateway Timeout) & 503 (Service Unavailable): The IDE is failing to connect to the feature-management service at
antigravity-unleash.goog. This has caused the system to enter an escalating back-off loop, effectively disabling agent functionality.
2. General Technical Regressions
The logs indicate several internal error patterns that suggest recent changes to the backend API or model behavior:
- Schema Mismatches: Repeated
argument order was not respectederrors during tool calls (specifically for fields likeTargetFileandTaskName), indicating a validation discrepancy between the client and server. - Token Limit Exceeded: Checkpoint summaries are frequently exceeding the 8192 token limit and being truncated, which likely causes loss of context for the agent.
- Malformed Payloads: Internal JSON parsing failures and “failed to mend json” errors point to inconsistent model outputs that the IDE cannot parse.
- Protocol Errors: The agent is incorrectly attempting to use
file:///protocols for local file operations, resulting in unsupported protocol scheme errors.
Conclusion:
The concurrent appearance of 429, 503, and 504 errors across different services confirms a server-side degradation. This is consistent with wider reports of service instability from other users and is not related to specific project configurations.