More than an account switcher
Antigravity Tools began with a simple attraction: keep several AI accounts in one desktop app and switch the active one without manually moving credentials. The current project is much broader. Its Rust and Tauri application tracks account quota, recommends an account, rotates around rate limits, maps model names, and runs a local gateway that accepts OpenAI, Anthropic, and Gemini-shaped requests. Claude Code, OpenCode, Cherry Studio, and other clients can point at that gateway instead of talking directly to one provider.
The distinction matters. This is not merely a tidy launcher for official API keys. The README says it converts Google and Anthropic web sessions into standardized interfaces. That can be useful for an individual with existing access and uneven quotas, but it also puts the project between a fast-changing client protocol and tools that expect stable public APIs. Much of the impressive engineering is devoted to absorbing that mismatch.
The routing features solve real annoyances
The account dashboard is the clearest reason to install it. Users can add accounts through OAuth, import tokens or JSON backups, inspect remaining quota, spot 403 failures, and switch the active identity. The proxy scheduler can skip unavailable accounts, preserve a conversation on one account, rotate after rate limits, and prioritize accounts according to subscription tier and reset timing. That is considerably more useful than round-robin routing when quotas recover on different schedules.
Protocol conversion is equally ambitious. The gateway exposes /v1/chat/completions for OpenAI-style clients, /v1/messages for Anthropic clients, and a Gemini-compatible path for Google's SDKs. Model mappings can group or redirect names, including regular-expression rules. Background requests from coding tools can be sent to cheaper models, while image requests can map OpenAI size values to the project's supported image path. Version 4.5.6 also tightened its Responses API translation, including tool-call output and mixed content handling.
There are good operational touches. The proxy defaults to the loopback address, the web console can use a password separate from the client API key, and account data is stored locally. Docker images support x86-64 and ARM64, with a browser console and a persistent data directory. Desktop packages cover Windows, macOS, and common Linux formats. The project is trying to be usable, not just technically possible.
Setup is quick until trust enters the picture
A desktop trial can take only a few minutes. The README offers shell and PowerShell installers, a Homebrew cask, DMG, MSI, ZIP, DEB, RPM, and AppImage packages. A server installation is one Docker command with port 8045, an API key, an optional web password, and a mounted configuration directory. Recommended memory is 1 GB, with 256 MB presented as the minimum.
Those instructions hide decisions that responsible users still need to make. Piping a remote script into a shell is convenient, but cautious users should inspect it or download a specific release. Every connected account adds a valuable OAuth credential. A remotely reachable Docker deployment needs TLS or a trusted private network, a strong separate admin password, controlled API-key distribution, and backups that are protected like credentials. The fallback behavior uses the API key for web login if no distinct password is set, so accepting defaults without understanding them is a mistake.
macOS packaging is the most visible rough edge. The README tells users to remove Apple's quarantine attribute when the app is reported as damaged. Open issue #3287 goes further: its reporter found an ad hoc signature, no notarization, and a strict signature verification failure in the 4.5.2 DMG. Homebrew can automate the workaround, but a security-conscious organization should not treat bypassing platform checks as routine installation. Windows issue #3281 reports a Defender detection. That report alone does not establish malware or a false positive, but it creates investigation work for managed fleets.
Compatibility is a moving target
The project releases at a striking pace because its translation layer keeps meeting new edge cases. The August 15, 2026 v4.5.6 release fixed Responses API formatting, tool configuration for Google's internal endpoint, mixed tool-call errors, file-based credentials for headless sessions, and tray icons. That responsiveness is encouraging. It also shows why version pinning and a test client are necessary.
Issue #3300 illustrates the risk. A combination of Gemini 3.x, custom function declarations, and Google Search produced 400 responses in Claude Code and OpenCode because naming conventions and the upstream internal endpoint did not accept the mixed tool configuration. Other current reports cover location restrictions, 429 or 503 responses, settings that do not survive a restart, and UI lockups. Some failures originate upstream, but users experience the gateway as one system and still have to diagnose which layer broke.
The repository was pushed on August 15, the same day as its latest release, and issues were being updated that day. Health is not the concern. Scale is: GitHub reported 1,793 open issues and pull requests, a daunting combined queue even for a project with active maintainers and more than 30,000 stars. Expect noisy support channels and search existing reports before assuming a failure is new.
Licensing and the sensible buying decision
The README labels the code CC BY-NC-SA 4.0, while GitHub reports no recognized software license identifier. That Creative Commons license restricts commercial use and requires adapted material to be shared under the same terms. Businesses should get legal guidance or permission rather than assuming that visible source means unrestricted commercial software.
Antigravity Tools earns a trial for a technical individual who needs quota-aware account switching and a local bridge for coding assistants. Few alternatives combine the polished account dashboard, desktop app, Docker mode, and three client protocol shapes in one package. It is much harder to recommend for company infrastructure. The license, unsigned macOS path, antivirus report, session-conversion model, and constant upstream compatibility work all create obligations beyond running a container. Treat it as an actively maintained power tool: pin releases, protect credentials, test upgrades, and keep an official API path available when reliability matters.