v3.0.7

Requests that hang or wait too long

• A request now stops with a clear error if Antigravity hasn't started answering within 10 minutes, counted across every retry, server and account switch. Before, a silent server could keep a request "Thinking" for over an hour with several accounts. Once the answer starts, the limit no longer applies, so long answers aren't cut off. The limit is fixed for now and may be tuned in a later release. (#23)
• max_rate_limit_wait_seconds now limits the total time a request waits while every account is rate-limited or over its soft quota, not each individual wait. When that time runs out, the request ends with the usual "no account available" error. 0 still means no limit. (#21)

Error messages

• Error messages no longer include the full list of tools, which could make a single error hundreds of thousands of characters long and overflow another model's context. They now list at most the first 20 tool names. With debug logging on, the full request still goes only to the debug log. (#18)
• Error messages no longer show your Google project ID. It's masked, the same way the debug log masks it.

Vault

• When an approved vault gives OpenCode or Pi no accounts, the /antigravity menu and the request error now say why, and what to do:
  • if the vault hasn't granted this host access, they show the command to grant it;
  • if access is granted but reaches no sign-in, they show ck auth reclassify --from-registry, then ck auth status.
    An older vault that can't tell keeps the general message.

OpenCode 2 sidebar

• The OpenCode 2 sidebar now shows quota the same way the OpenCode 1 sidebar does: Gemini and Other models instead of Gm and NG, one line per window, the reset time on the right, "reset since last check" when a window has reset since the last reading, and the reading's age once per account. The /antigravity menu uses the same names.
• The OpenCode 2 sidebar's route line (which account and model served the request) now stays on one line in a narrow sidebar, as it already did on OpenCode 1.

Setup

• First-time setup of a new account store is faster and safer. It does far fewer disk writes, and an interrupted first setup now leaves either no store or a complete one, never a half-finished one.
• setup fails at once with a clear message when pi install can't start, for example when npm isn't installed, instead of waiting.

Pi

• Pi's lock on its own login file now stays held during slow disk writes, so a slow disk can no longer cause the vault switch to be refused.