Google Antigravity

@@ -4,7 +4,7 @@   "type": "app",   "title": "Google Antigravity",   "brief": "Google Antigravity in Adom Hydrogen: the editor extension, the agy CLI and a dock dashboard that installs both into your container.",-  "version": "0.2.0",+  "version": "0.2.1",   "description": "Try Google Antigravity inside your Adom workspace. The dock dashboard installs the Google Antigravity VS Code extension into Hydrogen's editor and the agy command line into your WSL2 or Lima container, opens the panel, and reports what is installed and signed in.",   "org": "adom",   "needs_sudo": false,

@@ -4,7 +4,7 @@   "type": "app",   "title": "Google Antigravity",   "brief": "Google Antigravity in Adom Hydrogen: the editor extension, the agy CLI and a dock dashboard that installs both into your container.",-  "version": "0.2.0",+  "version": "0.2.1",   "hero": {     "type": "image",     "path": "screenshots/hero.png"@@ -86,4 +86,4 @@     "hydrogen-widget.json",     "widgets/**"   ]-}\ No newline at end of file+}

@@ -32,6 +32,19 @@ Reach the frames with Hydrogen's control API: `POST /eval-in {target: "extension    - replay the captured path inside the remote container: `curl "http://localhost:<port><path>"`. A 302 to `https://antigravity.google/auth-success` means signed in; the panel reloads into the last conversation.    - The callback is one-shot: never probe it with curl before delivering the real code. A new Google account may first demand a phone verification on its first Antigravity sign-in. +## AI-driven sign-in (the user asks you to sign Antigravity in for them)++Typical prompt: "sign Antigravity in to Adom's shared account". Adom's shared account (Google AI Ultra, Gemini 4 Argon) has its login on the private page `adom/antigravity-team-account`: read it with `adom-wiki repo show adom/antigravity-team-account README.md` (only Adom members can) and never repeat the password in chat or in any public file.++1. `adom-antigravity status`; install what is missing (`adom-wiki pkg install adom/antigravity`, then `adom-antigravity install-extension` and one editor reload) and `adom-antigravity open`.+2. If the panel shows a signed-in conversation for another account, Sign Out first (Settings).+3. Click **Continue with Google** in the panel (`/eval-in` on `extensionView=true`). Close whatever browser tab the picker opened only if you opened it.+4. Read the live consent URL from the container logs (grep above) and open it in **pup** on the same desktop (`pup_open_window {url}`). In Google's chooser click **Use another account** (or the account if pup already knows it), type the email, Next, type the password with `pup_type`, Next, then confirm **Sign in** on the "Make sure that you downloaded this app from Google" page.+5. On the user's own machine the redirect to `http://localhost:<port>/auth/callback` reaches the container directly (WSL/Lima localhost forwarding) and the panel signs in by itself. If pup shows "localhost refused to connect", relay the callback as in the remote-machine recipe above.+6. If Google asks to verify it's you, tell the user to get the phone approval (for the shared account, John approves it) and wait on the page.+7. Pick the model (**Gemini 4 Argon**) in the chat box's model menu, and offer the **Antigravity usage** widget: `POST $ADOM_HD_CONTROL_URL/widgets/open {"id":"antigravity-usage"}`.+8. Close the pup window you opened.+ ## Quota and cost  Antigravity on a Google AI plan (Pro, Ultra) is not billed per token: usage draws down **plan quota**, shown only as **Weekly Limit Remaining** and **Five Hour Limit Remaining** percentages in Settings, Models. There is no history: the page shows the value now, nothing about past runs. To know what a job costs, read both percentages right before and right after it (and every few hours on long jobs, since the five-hour window refills) and report the drop. "Included in the plan" is not a cost answer.