v3.0.6

Upgrading on OpenCode 2

If you use local Antigravity accounts on OpenCode 2, sign in once after upgrading: run opencode auth login, choose Google, then Google (antigravity-auth pool, browser), and select that connection. Earlier versions served every Google request for an Antigravity model from the account pool, whatever Google credential the connection held. From this release, the plugin serves only requests made through its own pool or vault connection. Until you sign in this way, requests go to Google with your existing Google connection, so Antigravity models may fail or be charged to that connection.

Vault users on OpenCode 2 don't need to do anything: connections made with Use approved Antigravity vault keep working. OpenCode 1 and Pi are unaffected.

Guided setup

• New setup command: npx @cortexkit/opencode-antigravity-auth setup. It finds your installed OpenCode 1, OpenCode 2 and Pi hosts, registers the plugin, and sets up either local Google sign-in or an approved Claustrum vault. Quit every OpenCode and Pi process first; setup checks and refuses while one is running.
• setup --dry-run shows the plan without changing any file.
• For OpenCode 2, setup prints the opencode auth login step instead of signing in for you.
• Pressing Escape or Ctrl-C at "Connect these hosts to the Claustrum vault?" now cancels setup without changing anything.

OpenCode 2

• Requests made with your own Google API key or native Google login now reach Google untouched, including session titles.
• Selected Gemini thinking variants now apply. Without a selection, models use their default level.
• Requests for a retired model are refused with a clear message, even when no account source is available.
• A response stream that fails after a long pause, or while the plugin is shutting down, now reports its error instead of ending as if it had finished.
• Pool requests with a custom Google base URL now stop with a clear message asking you to remove the custom baseURL.

Google addresses

• Requests to a custom Google address that only contains Google's host name, such as a proxy path, are no longer taken over. To use the plugin, keep the Google provider on Google's own address.

OpenCode 1 sidebar and quota

• Quota rows fit the narrow sidebar: one line per window, plain group names (Gemini, Other models), and the reset time on the right. Nothing wraps.
• Reset times show two units, such as 2h29m or 3d23h.
• A window that has reset since the last reading shows "reset since last check" instead of an outdated percentage.
• The reading's age appears once per account.
• In vault mode, a stuck background quota check no longer stops all later checks. Each check now has a time limit, and a check that fails or saves nothing logs one line saying why.

Accounts and sign-in

• antigravity-auth login now saves accounts to an account store that was already initialized or migrated, instead of failing.
• When the sign-in port 51121 is already in use, sign-in fails at once with the port error and no longer reports a second timeout error minutes later.
• Vault enrollment works on Windows. It no longer fails on the vault folder's permissions.
• Vault messages use plainer wording and name the shared folder when the vault token can't be saved.

Gemini CLI path removed

Google stopped serving Gemini CLI to consumer accounts (free, Google AI Pro and Ultra) on June 18, 2026. The plugin no longer has a separate Gemini CLI request path. Requests handled by the plugin use Antigravity only.

• Gemini requests no longer use the Gemini CLI headers or its separate quota pool, and never fall back between the two pools.
• The /antigravity Routing section no longer has the "Gemini CLI headers first" and "Fall back to the other header style on quota" switches. It now shows which account selection strategy is in effect (hybrid, sticky or round-robin), and where to change it: account_selection_strategy in antigravity.json. In vault mode, it says that accounts come from the vault.
• The cli_first, quota_fallback, quota_style_fallback and operator.routing settings are removed. If your antigravity.json still contains them, they are ignored and every other setting keeps working. Saved account data from earlier versions loads as before.
• Antigravity's own fallback from its daily server to its production server is unchanged, as are account rotation, cooldowns, soft quota protection and the quota kill switch.

Sidebar state file

• The sidebar writer leaves a newer-format state file untouched instead of replacing it with an older format. Processes running versions before 3.0.6 still need restarting to gain this protection.