app
Google Antigravity
Public Made by Adomby adom
Google Antigravity in Adom Hydrogen: the editor extension, the agy CLI and a dock dashboard that installs both into your container.
← Commit history
antigravity-account: read quota from the hub (RetrieveUserQuotaSummary) without opening Settings
1 file changed
+2−2
skills/antigravity-account/SKILL.md+2−2@@ -1,7 +1,7 @@ --- name: antigravity-account description: >- Sign Google Antigravity in and out inside Hydrogen, on this machine or a remote one; read its plan and quota (Models & Usage: weekly and five-hour limits) and per-call token usage; and drive the side-bar chat from scripts (find the hub frame, paste a prompt, send, approve permission prompts, unstick queued messages). Read before any sign-in, account switch, quota or cost question, or automation of the Antigravity panel. Trigger words: antigravity sign in, antigravity log in, antigravity login, sign out of antigravity, switch antigravity account, antigravity account, continue with google antigravity, antigravity quota, antigravity usage, weekly limit, five hour limit, antigravity cost, antigravity tokens, how much of my plan, drive antigravity chat, antigravity panel automation, antigravity queued message, send now.+ Sign Google Antigravity in and out inside Hydrogen, on this machine or a remote one; read its plan and quota (Models & Usage: weekly and five-hour limits) and per-call token usage; and drive the side-bar chat from scripts (find the hub frame, paste a prompt, send, approve permission prompts, unstick queued messages). Read before any sign-in, account switch, quota or cost question, or automation of the Antigravity panel. Trigger words: antigravity sign in, antigravity log in, antigravity login, sign out of antigravity, switch antigravity account, antigravity account, continue with google antigravity, antigravity quota, antigravity usage, weekly limit, five hour limit, antigravity cost, antigravity tokens, RetrieveUserQuotaSummary, antigravity remaining quota, how much of my plan, drive antigravity chat, antigravity panel automation, antigravity queued message, send now. --- # Antigravity account, quota and panel automation@@ -54,7 +54,7 @@ Hydrogen's own entry point is the VS Code AI menu (**+** in the toolbar, `title` ## 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.+Antigravity on a Google AI plan (Pro, Ultra) is not billed per token: usage draws down **plan quota**, shown as **Weekly Limit Remaining** and **Five Hour Limit Remaining** percentages in Settings, Models. Read the same numbers without opening Settings (no editor tab, nothing on screen): ask the running hub `agy --hub` for `RetrieveUserQuotaSummary`. Its port and CSRF token are on its command line (`ps -eo args`); `POST http://127.0.0.1:<port>/exa.language_server_pb.LanguageServerService/RetrieveUserQuotaSummary` with header `x-codeium-csrf-token: <token>` and body `{}` returns `response.groups[].buckets[]` with `window` (`weekly`, `5h`), `remainingFraction` and `resetTime`, one group for Gemini and one for the Claude and GPT models. `GetUserStatus` on the same service gives the signed-in email and tier; `GetLoadCodeAssist` the plan name. On another machine run it through Adom Bridge `wsl_exec`. The ready-made script for every AI is in the `hydrogen-ai-agents` skill, section Quota. 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. Per-call token usage IS recorded locally. Each conversation DB has a `gen_metadata` table, one protobuf row per model call. Field 1.4 is the usage record; as decoded on 2026-10-16 (undocumented, consistent across thousands of calls): 1.4.1 = model id, 1.4.2 = fresh input tokens, 1.4.3 = output tokens, 1.4.5 = cached input tokens. Field 1.19 is the model name (for example `gemini-4-argon`). Sum them per conversation for a job's token count.