QUOTAS & SCHEDULING · ANTIGRAVITY TOOLS 5.0.0

Antigravity Manager Quotas, Rotation & Scheduling

Antigravity Manager shows remaining quota for each account and can route API requests to another available account. Start by checking the model’s short-term and weekly limits, then choose how you want Manager to switch accounts.

For Antigravity Tools 5.0.0 · Updated

START WITH THE LIMITING WINDOW

Why do the quota views show different percentages?

Each view answers a different question: how much remains in the 5-hour window, how much remains this week, or how much is available after both limits apply. For a model with both windows, the combined available percentage uses the lower value.

Examples for one model in one account. Dashboard totals combine accounts; Weighted also applies tier weights.
Reported quotaHow to read itWhat to do
5-hour: 80%
Weekly: 30%
The combined model value is 30%. The 5-hour view can still show 80%.Plan around the smaller weekly allowance. Waiting for the short window to reset leaves the weekly limit in place.
5-hour: 80%
Weekly: 0%
The weekly quota is exhausted. Manager also shows 0% in the model’s 5-hour view.Check the weekly reset time or use another account with access to this model.
5-hour: 0%
Weekly: 80%
The weekly view still shows 80%, while the combined value is 0% during the short-window cooldown.Wait for the 5-hour reset or switch to an eligible account.
Missing quota dataA missing reading can appear as 0% in a model view.Refresh the account and check any reported error before treating the quota as exhausted.

CHECK THE RIGHT ACCOUNT

Read quota and reset times

Refresh the account you intend to use, then inspect the requested model and both available quota windows.

  1. Identify the account. Check its email and the model you need. A pool-wide average can hide an exhausted account.
  2. Refresh its quota. Use the account’s refresh action; on the Dashboard, Refresh Quota refreshes the current account. Wait for completion and check the update time. If the refresh fails, the previous reading may be stale.
  3. Compare the views. The Dashboard offers Weighted, 5H Rolling and 7-Day Weekly. Inspect account or model details when you need the limit for a particular request. Free-tier account summaries show the weekly window.
  4. Read the reset time for the exhausted window. After that time passes, refresh again to retrieve the new allowance. Each account and window can have a different reset time.

Refreshing retrieves quota information. The upstream service controls when capacity becomes available, so repeatedly refreshing an exhausted account leaves you waiting for the same reset.

Quota remains, but the model fails

Check the exact model ID, account access and error message. A Gemini allowance may coexist with a restriction on a particular Gemini model; a Claude allowance has its own model requirements. Compare the model with the available models and routing settings. Follow account authorization troubleshooting for a verification request or a 403 response.

If access is valid and quota remains, check Quota Protection and the QoS status. Either can keep an account out of normal API selection.

WORK IN THE APP OR CLI

Choose an account with Best Accounts

Best Accounts recommends an account to switch into your selected Antigravity client: Classic, IDE or CLI.

  1. Refresh the accounts you want to compare, then open Dashboard → Best Accounts.
  2. Select Classic, IDE or CLI to match the client you are using.
  3. Choose the Gemini or Claude recommendation and use its switch action. Finish any restart or confirmation requested by the client.
  4. Check the active account in that client before continuing work. See switching between Antigravity accounts for the full procedure.

Why the fullest account may be missing

Recommendations exclude the account already active in the selected client, disabled accounts and accounts awaiting validation. In 5.0.0, Pro and Ultra accounts rank ahead of Free accounts; within those groups, the 5-hour quota determines the order. A reported weekly bucket at 5% or less removes that model category from the recommendations, even if its 5-hour value is high.

Manager also tries to offer different accounts for Gemini and Claude when alternatives exist. This can move one recommendation to the next suitable account.

Switch Classic automatically when quota runs low

For the standalone Classic client, open Settings → Account → Classic Auto Hot-Switch. Enable it, set a Trigger Threshold and choose Monitored Quota Pools. Changes save automatically. When the running Classic client’s account reaches or falls below the threshold in a monitored pool, Manager can switch it to a suitable replacement. Keep another account with enough quota available. Use the manual switch actions above for IDE and CLI.

Can the IDE use the entire pool?

A client switch changes the identity used by the selected Antigravity installation. API rotation applies to requests sent through Manager’s proxy. To use the API pool from a supported tool, start the local proxy and connect the tool to its endpoint.

ROUTE REQUESTS THROUGH THE POOL

Set up API account rotation

Open API Proxy → Account Rotation & Scheduling to control whether conversations reuse an account and how new work is distributed.

Start the proxy and confirm that your client uses its endpoint. Add usable accounts to the API account pool, then choose a Scheduling Mode:

  • Balance: keeps a conversation on its assigned account while that account remains usable. This is a practical starting point for interactive work with fallback accounts.
  • Cache First: also reuses conversation bindings. The interface includes Max Wait (sec), but 5.0.0 releases a rate-limited binding immediately. Allow for a switch to another account when a limit is reached.
  • Performance: skips conversation binding and evaluates available accounts for each request. Consecutive requests can still select the same account.

Account priority, requests already in progress, quota and health affect selection. Expect a busy or limited account to receive less work; equal traffic across every account would require different conditions.

Keep one account preferred

Enable Fixed Account Mode and select an account while the proxy is running. Manager tries that account first. It can fall back when the account is disabled, unavailable, rate-limited or quota-protected. A known zero quota also triggers fallback when an alternative has positive quota for the model; forced retries can move to another account.

Recheck the selection after restarting the proxy. If your task requires a particular identity, confirm the account that served the request using the headers below.

Run several terminals or conversations

Manager groups requests by conversation information supplied by the client. Several terminals can share one account, and an existing conversation can move after a limit or retry. A new terminal alone gives you no dedicated account assignment.

Spillover Account Cap limits the candidate accounts considered for new assignments. A value of 0 allows all available accounts; a positive value narrows the selection. Existing conversation bindings and fixed-account preference are handled separately. A low cap leaves fewer alternatives when several conversations are busy.

Use Clear Session Bindings when you want conversations to be assigned again on their next request. This clears the existing account associations and may reduce reuse of cached prompts. Clear Rate Limit Records clears local waiting records; upstream limits still apply to the next request.

See which account answered

For an OpenAI-compatible request, inspect the response headers: X-Account-Email identifies the serving account and X-Mapped-Model identifies the routed model. Error responses may omit them. If your client hides headers, find the request in Manager’s monitor.

Send a short message, follow up in the same conversation, then start a separate conversation. Compare the account on each response to see how your settings behave. For recording and interpreting those requests, use the request monitoring guide. Remove account emails, API keys and conversation content before sharing diagnostics.

SAVE CAPACITY FOR LATER

Keep a quota reserve

Quota Protection stops Manager from selecting an account for a monitored model group once the group falls below your threshold.

  1. Open Settings → Account → Quota Protection and turn on Enable Quota Protection.
  2. Set Reserved Quota Percentage and choose the groups under Monitored Models (Trigger Conditions).
  3. Changes save automatically. Refresh quota and check which groups become protected. Keep another account available if you want API requests to continue.

Enabling protection also turns on background quota refresh, so Manager can update protection as account readings change.

What a 20% threshold means

In 5.0.0, Manager compares the highest reported model percentage within each local group with your threshold. With a threshold of 20%, a group whose highest value is 19% becomes protected; a highest value of 20% remains eligible. If two variants show 10% and 30%, the group uses 30% for this decision.

A later quota update can restore the group once that value reaches the threshold again. The reserve applies to requests routed through Manager; direct use of the account elsewhere can still spend the remaining allowance.

Why another model ID can have the same protection

Several model IDs share one local protection group. Claude variants share claude, and Argon variants share gemini-4-argon. Image Flash and Image Pro use separate groups. Changing between variants inside a protected group keeps the same protection decision.

If an account is skipped unexpectedly, compare its refreshed model readings with the group and threshold you selected. Adjust the reserve only when you intend to make that capacity available to API work. With every eligible account protected, requests for that group can fail until capacity returns or the settings change.

OPTIONAL AUTOMATION

When to use weekly quota warmup

Warmup sends small generation requests to activate a fresh usage window. Those requests can consume quota.

Use warmup if you want fresh weekly windows to start automatically while Manager is running. Leave it off if you prefer an account’s first request to come from your own work.

Open Settings → Account → 7-Day Weekly Reset Warmup, enable the feature and review its model selection. Enabling it with an empty selection selects the available core models automatically. Changes save as you make them. Keep the proxy running for scheduled requests.

Automatic and manual warmup behave differently

  • Automatic: checks every five minutes for full weekly buckets around their reported reset. A full bucket without a reset timestamp can start an initial cycle. After a successful trigger, the same account, bucket and reset cycle has a six-day cooldown.
  • Manual, all accounts: refreshes quota and checks full models, with a four-hour history check to skip recent warmups.
  • Manual, one account: refreshes quota and can warm every model still at 100%. This action has no equivalent four-hour check, so repeated clicks can enqueue more requests.

These timings apply to 5.0.0. After triggering warmup, check its request outcome and let the quota refresh finish. “No warmup needed” can simply mean the account has no full models to warm. If warmup fails, check that the proxy is running and read the error before retrying.

To stop scheduled warmup, turn the feature off; the change saves automatically. Requests already sent can finish and retain their quota cost.

QUOTA LEFT, ACCOUNT SKIPPED

Check QoS cooldown and recovery

Manager’s quality-of-service checks can temporarily skip an account after unusually slow responses, even when its quota is full.

Read the badge next to the account to see where it is in the recovery process:

  • Suspected Throttled: Manager has detected abnormal response latency and favors healthy accounts for new work.
  • In QoS Cooldown: the account is temporarily isolated from normal selection. Check the remaining cooldown.
  • Probing Recovery: a background request is checking whether response performance has recovered.
  • On Probation: the account has passed a recovery probe and is being observed as it returns to use.

Retry an isolated account with Release

Use Release on the cooldown badge when you want to try the account again. It clears the local QoS state, accumulated penalty and rate-limit records for that account. Its quota and upstream access rules continue to apply.

Check the serving account on the next request and observe its response. If the same account remains slow, Manager may isolate it again. You can disable the account for proxy use while investigating.

What changes when Fixed Account Mode is enabled?

In 5.0.0, fixed-account selection can still choose an account in QoS cooldown because it uses different health checks. Turn off Fixed Account Mode when you want normal pool selection to avoid isolated accounts.

What if every account is unavailable?

A request needs an account that can serve its model. If all suitable accounts are exhausted, protected, disabled or otherwise unavailable, rotation can end in an error. Check the failing model’s windows and account status first. Then use 429 and 503 troubleshooting to decide whether to wait, restore access or change a local setting.

FOR ARGON USERS

Why the Argon quota can change after an update

Argon quota handling differs between these releases. Check your installed version when an Argon bar disappears or an account is skipped after an update.

5.0.0-beta.3
The 5.0.0-beta.3 release notes describe requiring a dedicated Argon quota group and removing fallback to general Gemini quota.
5.0.0 stable
The quota reader can fall back to general Gemini quota when a dedicated Argon group is missing. The interface can also display Argon from individual model entries. Check the account’s actual model access if the displayed quota and a request disagree. See the 5.0.0 quota handling.
5.0.1-beta.2
The 5.0.1-beta.2 release notes describe shared Gemini quota for Ultra accounts. Pro accounts still require a dedicated Argon group; Free accounts remain excluded under that release’s eligibility rules.

After updating, refresh the account and check its model list before changing rotation settings. Use the model guide for model IDs and mappings.

Choose your next step

WINDOWS DOWNLOAD

Archive password

Keep this password to open your Windows download if prompted.