Security alert: Why you should ditch Antigravity Cockpit ASAP

hi all. quick story time. i hit my Antigravity quota again (as usual). i wanted a dumb-simple way to track usage. so i installed the most popular “cockpit/quota” extension (1.6M+ downloads), logged in with Google, and moved on. then i got that tiny itch: “ok… what did i just authorize, and where is it storing auth?” so i went digging. what i found is simple and not debatable: this extension persists Google OAuth credentials to disk in plaintext JSON, including a refresh token, and it requests a very broad scope ( https://www.googleapis.com/auth/cloud-platform ). that combo is the whole problem. it’s the entire flow in one glance: login → token grabbed → written to plaintext JSON → anything running as you can read it → attacker can mint new access → “whatever your IAM allows” in GCP (Google Cloud Platform). what’s the actual risk Extensions aren’t evil. Antigravity is a fork of VS Code. extensions run in the Extension Host (Node). they can use IDE APIs and they can touch your filesystem