Summary
Would you consider adding Antigravity as a supported client in Tokscale?
Motivation
Tokscale already supports several local AI coding clients such as Claude Code, Codex CLI, Gemini CLI, OpenClaw, and OpenCode. Antigravity is becoming part of the same workflow for some users, especially for quota monitoring and recent usage visibility.
What seems available locally
From local Antigravity installs on macOS, there appear to be usable data sources under:
~/Library/Application Support/Antigravity/logs/**/window*/exthost/google.antigravity/Antigravity.log~/Library/Application Support/Antigravity/User/globalStorage/storage.json
The most reliable signal I found so far is quota-related log output such as:
RESOURCE_EXHAUSTED (code 429)Your quota will reset after ...- model names in the same log lines
So even if exact token accounting is not available at first, Antigravity could still be valuable in Tokscale as:
- quota-only support
- best-effort recent usage support
- a client entry in
clients / --light output with explicit precision labeling
Suggested scope for MVP
- detect local Antigravity installations
- parse quota exhaustion / reset windows from logs
- show provider/model + reset timer in CLI/TUI
- mark the source as
quota-only or best-effort so it does not imply exact token accounting
If this direction makes sense, I would be happy to help validate sample logs or test an early adapter.
Summary
Would you consider adding Antigravity as a supported client in Tokscale?
Motivation
Tokscale already supports several local AI coding clients such as Claude Code, Codex CLI, Gemini CLI, OpenClaw, and OpenCode. Antigravity is becoming part of the same workflow for some users, especially for quota monitoring and recent usage visibility.
What seems available locally
From local Antigravity installs on macOS, there appear to be usable data sources under:
~/Library/Application Support/Antigravity/logs/**/window*/exthost/google.antigravity/Antigravity.log~/Library/Application Support/Antigravity/User/globalStorage/storage.jsonThe most reliable signal I found so far is quota-related log output such as:
RESOURCE_EXHAUSTED (code 429)Your quota will reset after ...So even if exact token accounting is not available at first, Antigravity could still be valuable in Tokscale as:
clients/--lightoutput with explicit precision labelingSuggested scope for MVP
quota-onlyorbest-effortso it does not imply exact token accountingIf this direction makes sense, I would be happy to help validate sample logs or test an early adapter.