v3.0.14

Changed

• Vault files, the signature cache and debug logs move out of OpenCode's config folder. OpenCode watches that folder, so the plugin's vault lock files caused constant reloads and CPU use in vault mode (#51). On the first start of 3.0.14, the vault files move once to ~/.local/state/cortexkit/antigravity-auth/opencode/ ($XDG_STATE_HOME if set; the same place on Windows). Your vault enrollment carries over, so you don't need to enroll again. The signature cache is rebuilt there, and new debug logs go there; old logs stay where they were and can be deleted.
  • Close every OpenCode before upgrading. While an older version of the plugin is still running, the move waits and the vault files stay where they are.
  • The account store stays in OpenCode's config folder for now. Moving it is planned for a later release.
  • If the move can't finish, for example because the old and new folders hold different vault files, the plugin serves no accounts and the error names both paths and what to do. It never falls back to local accounts on its own.
  • Going back to an older version: close every OpenCode, move the vault files back into antigravity-auth-vault/ in OpenCode's config folder, then delete layout.json from the new folder. Until then, an older version stays in vault mode and refuses requests. See Where the files live.
• OPENCODE_ANTIGRAVITY_LOG_DIR now works. It sets the debug log folder and takes precedence over log_dir.

Fixed

• Tool schemas that allow null work on Gemini. A field typed ["string", "null"] lost its type and Gemini rejected the request. It's now sent as the type with nullable: true (#44, thanks to @mv2sa in #45).
• Building from a folder named antigravity, plugin, hooks or rpc works. The build's check on the sidebar code no longer matched folder names above the project (#46, thanks to @mv2sa in #47).
• Setup on Windows: a file lock that disappears while another process waits for it no longer makes setup fail.
• The empty-response error now says "1 attempt" instead of "1 attempts".