One of the first things I tried after noticing unusual quota behavior was to invalidate all existing sessions.
I performed the following actions:
- Changed my Google Account password.
- Revoked Antigravity access from Google Account → Third-party apps & services.
- Verified that the password change and access revocation had completed successfully.
However, I could not find any way to remotely terminate all existing Antigravity sessions.
Steps to Reproduce
- Sign in to Antigravity using a Google AI Pro account.
- Keep Antigravity running or previously authenticated.
- Change the Google Account password.
- Remove Antigravity from Google Account → Third-party apps & services (revoke all access).
- Verify that the password has been changed and the application authorization has been revoked.
- Observe that there is still no option to remotely sign out or invalidate all existing Antigravity sessions.
Why this matters
From a security perspective, users generally expect that changing their Google Account password and revoking application access will invalidate active sessions.
If Antigravity intentionally behaves differently, it would be helpful to have official documentation explaining:
- whether active sessions are expected to survive a password change,
- how authentication tokens are managed,
- and whether there is an official method to force logout on every device.