v3.0.0

Upgrade first

This is a major upgrade for existing local-account setups.

• OpenCode: before the upgrade, set top-level "auto_update": false in the effective antigravity.json, and make sure project configuration does not re-enable it. The 2.2.1 updater can advance even pinned installs across major versions. Stop every OpenCode and Antigravity process before migrating an existing account pool. Use the 3.0.0 CLI, then restart the upgraded hosts only after migration completes:

  npx @cortexkit/opencode-antigravity-auth@3.0.0 migrate --offline

  Confirm that all processes and background timers have stopped when prompted. Fresh installations without an existing pool do not need this migration. Do not run old and new plugin builds against the same pool at the same time.

  An auto-updated, unmigrated installation refuses requests until migration completes: “Antigravity accounts require offline migration. Stop OpenCode, then run npx @cortexkit/opencode-antigravity-auth@3.0.0 migrate --offline.”

• Pi: update google-antigravity/... model selections to google/... and run /login google for local OAuth. Existing google-antigravity credential entries are not moved or overwritten automatically. Pi's native login file is separate from the OpenCode account pool; Pi-only users do not run the OpenCode migration command.

OpenCode 1 and 2 in one package

• @cortexkit/opencode-antigravity-auth now provides both server and TUI integration for OpenCode 1.x and OpenCode 2. There is no separate OpenCode 2 package to install.
• Supported host ranges are OpenCode 1.17.13 or later in 1.x, or 2.0.22 or later.
• Account, quota, routing and vault actions use the single /antigravity menu.
• Reloading OpenCode 1 authentication keeps already-admitted response streams alive. Final shutdown blocks new work and cancels outstanding I/O.

Claustrum vault accounts

• Connect an approved Claustrum vault through /antigravity, keeping the same google/ model names in OpenCode and Pi.
• Vault mode uses fresh vault credentials for requests and leaves local accounts dormant. An empty or unavailable vault reports a failure instead of falling back to local credentials.
• Local account-writing actions are hidden while vault mode is active. Disconnect the vault to return to local account management.
• Pi preserves the previous native Google login during vault mode and restores it on disconnect only while the slot still belongs to that enrollment.

Local accounts, quotas and errors

• Local OpenCode accounts use a lease-backed store with credential-attributed updates and crash-recoverable migration and replacement.
• Quota displays consistently show % left, reported windows and valid reset countdowns. Stale readings show their age; source changes do not make old readings appear fresh.
• Transport and streaming failures remain native host errors. Selected credentials are masked in returned HTTP/SSE diagnostics, headers and stream-cancellation failures, including JSON-escaped error responses. Successful model and tool content remains unchanged.

Downgrading after migration

Downgrade is supported only after a successful offline rollback, not by reinstalling an older package over the migrated store.

1. Disconnect vault mode through /antigravity before downgrading.

2. Stop every OpenCode and Antigravity process and background timer.

3. Use the 3.0.0 CLI, before installing the older build:

   npx @cortexkit/opencode-antigravity-auth@3.0.0 rollback --offline

4. Wait for rollback to complete, then install and start the older build. Restore its model selections and local host login if needed.

Rollback exports the store's current credentials to the legacy account file. Do not restore an old account-file backup over it. Account-store rollback does not undo Pi provider-name changes or host-managed vault activation records.

Full Changelog: v2.2.1...v3.0.0