Google account management, quota tracking and a local API gateway for Antigravity
English | 简体中文
Antigravity Manager is a desktop application for managing the Google accounts used by Antigravity clients (including Classic, Antigravity IDE and agy CLI). View model quota in real time, switch client accounts seamlessly, and connect AI coding tools like Claude Code, Codex and OpenCode through a high-performance local API gateway.
- Download and install
- Nix / NixOS
- First use
- Features
- Screenshots
- Data and account risks
- Troubleshooting and feedback
- Development and documentation
- Contributing
- License
- Disclaimer
Download an installer for your operating system and processor architecture from GitHub Releases. Available files and release notes on that page are authoritative for each version.
| Platform | Architectures | Packages |
|---|---|---|
| Windows | x64, ARM64 | NSIS setup (-nsis.exe); MSI also available for x64 |
| macOS | Apple Silicon (arm64), Intel (x64) |
DMG installers; ZIP standalone archives |
| Linux | x64, ARM64 | AppImage, DEB, RPM packages |
Note
- Architecture names: Choose
arm64oraarch64for ARM64, andx64,amd64orx86_64for x64 according to the asset name. - Windows: Executables ending in
-nsis.exeidentify standard NSIS installers. Keep the same installer family when updating an existing installation. - macOS: Move the application to
/Applicationsbefore opening it. - Linux: Select the package appropriate for your distribution; running AppImage requires a supported runtime environment.
- Desktop packages include their application runtime. Node.js and pnpm are required only for source development.
- Arch Linux: The community AUR package can be installed with
yay -S antigravity-manager-bin. Its version and availability are maintained separately from GitHub Releases.
With Nix flakes enabled, run the application directly on Linux x64 or ARM64:
nix run github:Draculabo/AntigravityManagerFor a persistent NixOS installation, add the flake input:
inputs.antigravity-manager.url = "github:Draculabo/AntigravityManager";Then apply its overlay in a NixOS module with inputs available:
{ inputs, pkgs, ... }: {
nixpkgs.overlays = [ inputs.antigravity-manager.overlays.default ];
nixpkgs.config.allowUnfree = true;
environment.systemPackages = [ pkgs.antigravity-manager ];
}For Home Manager, use home.packages and configure the overlay and unfree policy on its owning nixpkgs instance. The flake pins a release and may lag behind the latest assets. See Nix integration for details and development-shell configuration.
- Open Manager and add a Google account through browser authorization. To discover existing local accounts, use Import from this computer, review the preview, and confirm the accounts to import.
- Refresh quota and inspect the available models, remaining quota and reset times. Model access depends on the account and upstream service. Gemini and Claude entries describe models available through those Google accounts.
- Select the intended Antigravity client target: Antigravity (Classic), Antigravity IDE or agy CLI. Save work in a desktop client before switching; switching can close and relaunch it.
- Switch to the selected account, then verify the signed-in identity in the official client. Complete any official first-use setup or terms confirmation shown there.
- Enable automatic switching if desired. Client switching and account selection for proxy requests have separate policies.
See the account and quota guide for automatic switching, quota windows and optional weekly warmup.
- Add a usable Google account and refresh its quota.
- Open API Proxy, review the account risks, and confirm the warning when starting the service for the first time.
- Use the tool configuration cards for Claude Code, Codex or OpenCode. Select an available model and review settings before applying them. For another API client, use the gateway address and API key shown in Manager.
- Reopen the configured tool and send a small request. Confirm the request and result in Traffic Monitor; saved configuration alone does not establish that the connection works.
Tool configuration changes local client settings. Read the configuration and recovery guide for backup, removal and restoration behavior.
| Area | What Manager provides |
|---|---|
| Google account pool | Browser authorization, local account discovery, account status, batch actions and JSON import/export |
| Quota views | Five-hour, weekly or combined views; model visibility controls, sorting and manual or periodic refresh |
| Client account switching | Manual switching for Classic, IDE and agy CLI, with optional automatic switching based on account quota and rate limits |
| Local API gateway | OpenAI Chat Completions and Responses, Anthropic Messages and native Gemini interfaces, with model routing and streaming |
| Coding tool setup | Configure Claude Code, Codex and OpenCode connections, with tool-specific backup and recovery |
| Backups and identity profiles | Local account snapshots and restoration, plus optional client identity-profile management |
| Diagnostics | Traffic inspection, error details, diagnostic references for supported operations and a user-reviewed GitHub report flow |
| Desktop controls | System tray, quota notifications, appearance settings, compact account layouts and English, Chinese and Russian UI |
Note
- Protocol compatibility depends on the requested feature, model and upstream behavior. See the gateway reference for supported paths and limitations.
- Weekly warmup is optional and off by default. It sends real model requests and can consume quota or AI credits. See its behavior and limits before enabling it.
Expand each section to view the screens by feature. Long pages are captured in sections for readability. Record totals include local app activity from the demo instance; the model request list is empty.
API proxy: service, tools, models, records and examples
Service status and basic configuration
Complete Claude Code, Codex and OpenCode controls
Model mapping
Request and reasoning history retention
OpenAI protocol examples in cURL and Python
Anthropic protocol examples in cURL and Python
Traffic monitor
Model requests and filters (no model requests)
Settings: general, models and proxy
Appearance, account refresh and startup
Client cache and application information
Privacy options and notification thresholds
Model visibility
Auto-switch models and weekly quota warmup
Local service and upstream proxy settings
CLI command output
Command line help and stopped-service output
Warning
Cloud-account OAuth tokens are stored as plaintext JSON in the local SQLite database. Anyone who can read that database can read the tokens. Full account exports and backups can also contain tokens and proxy credentials. Protect the profile directory and backups, and never attach them to public issues.
Other credential stores retain their own OS keyring or encrypted-storage policies. See security and data boundaries for the full policy, migration behavior and diagnostic privacy.
Warning
Reverse-proxy use can violate provider terms and lead to account restrictions or suspension. Use only accounts you can afford to lose. Manager does not guarantee account safety, model availability or uninterrupted access.
The first desktop proxy start requires acknowledgment of the risk warning. Cancelling or closing that dialog leaves the service stopped. Protect the proxy API key and review network access before allowing other devices to connect.
Confirm the downloaded package matches the OS and CPU architecture, and record the application version and exact error. For source builds, follow the development prerequisites. For packaged applications, include installer type and whether the failure occurs during installation or launch when reporting it.
Open Details on the error notification when available. Keep the diagnostic reference and note the target client, platform and action that failed. Check network/proxy settings and any official-client setup still awaiting confirmation. Back up the profile before resetting application data.
On macOS, distinguish an application launch warning from an OAuth save failure or a client-switch failure. These involve different steps; capture the exact error before changing credentials or application signing.
Check that the gateway is running, the account can access the selected model, and the tool uses the displayed endpoint and key. Environment variables, command-line options or direct-login plugins can override saved settings. Inspect Traffic Monitor and the tool configuration guide.
Use Report to GitHub from an error notification when available. Manager copies environment information and redacted error details, then opens the issue template. Review the copied report before pasting and submitting it. Otherwise, open GitHub Issues and include reproduction steps, version, OS, architecture and any diagnostic reference.
Exclude tokens, API keys, account databases, private prompts and unreviewed logs from public reports.
Source development requires Node.js 24.22.0, pnpm 10.34.6 and the native build prerequisites for your platform. Use the checked-in pnpm lockfile:
git clone https://github.com/Draculabo/AntigravityManager.git
cd AntigravityManager
pnpm install --frozen-lockfile
pnpm startSee Development for builds, local Git checks and platform requirements, and Architecture for desktop and standalone CLI/core operation. Use Testing to choose validation, and the script guide to locate acceptance tools.
| Reference | Contents |
|---|---|
| Documentation index | Cross-cutting guides and documentation ownership |
| Feature module index | Guides grouped by the responsible feature |
| Architecture | Electron, renderer, standalone core and module boundaries |
| Accounts and quota | Account management, quota views, automatic switching and warmup |
| Proxy gateway | Protocol compatibility, coding tools and traffic debugging |
| Security | Credentials, backups, diagnostics and trust boundaries |
Read CONTRIBUTING.md before opening a change. Contributions follow the Contributor Covenant.
CC BY-NC-SA 4.0. Commercial use is prohibited.
Warning
For Educational Purposes Only
This project is intended solely for educational and research purposes. It is provided "as-is" without any warranty. Commercial use is strictly prohibited.
By using this software, you agree that you will not use it for any commercial purposes, and you are solely responsible for ensuring your use complies with all applicable laws and regulations. The authors and contributors are not responsible for any misuse or damages arising from the use of this software.
If this project helps you, please give it a ⭐ Star!