mirror of
https://github.com/NikkeTryHard/zerogravity.git
synced 2026-04-25 07:05:58 +03:00
[GH-ISSUE #10] Antigravity detection fails on Windows #9
Labels
No labels
bug
enhancement
enhancement
notice
pull-request
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/zerogravity#9
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @david-courtis on GitHub (Feb 19, 2026).
Original GitHub issue: https://github.com/NikkeTryHard/zerogravity/issues/10
What do you want?
Please implement either proper antigravity detection, google auth, or let us specify our antigravity directory to retrieve refresh token.
Use Case
Token refresh capability
Alternatives Considered
N/A
@NikkeTryHard commented on GitHub (Feb 19, 2026):
please use docker version in the meantime while i reverse engineer the windows version. sorry for the inconvenience
@david-courtis commented on GitHub (Feb 19, 2026):
@NikkeTryHard Antigravity detection does not work in the docker version either. I have antigravity installed and am logged in in windows. Here is what I get:
@NikkeTryHard commented on GitHub (Feb 19, 2026):
Hey! So I dug into this — here's what's going on:
The "Could not find Antigravity install" warning is cosmetic. The proxy falls back to hardcoded versions and works fine without detecting the install. That's not the real problem.
The actual issue is the OAuth token. When you run the proxy in Docker on a Windows host, it can't see your Windows Antigravity config. The token lives in
%APPDATA%\Antigravity\User\globalStorage\state.vscdbon your Windows machine, but the Docker container is Linux and doesn't know about that path.Workaround for Docker on Windows:
Volume-mount your Antigravity config into the container:
Or just pass the token directly:
You can grab the token from Antigravity's dev tools (Help → Toggle Developer Tools → Application → Local Storage).
As for implementing a proper Google auth flow — that's unfortunately not feasible. Antigravity uses a custom Electron-based OAuth dance with Google's servers, and reverse-engineering the full client credentials + auth flow would be a massive rabbit hole that could break at any time.
I'll update the Docker docs to make the volume mount approach clearer. Sorry for the friction 🙏
@david-courtis commented on GitHub (Feb 19, 2026):
Thank you very much for explaining. After configuring, the proxy still had me pass through an auth token in order to work for the first time. I got it working by posting a valid oauth token to the endpoint /v1/token. Not sure if it is using my state.vscdb for successful refresh.
Can you view these logs and verify that the Oauth token is indeed being automatically refreshed?
Thank you 🙏
@NikkeTryHard commented on GitHub (Feb 19, 2026):
use docker in the meantime