The app, the people, and these guides
About Antigravity Manager and This Site
Antigravity Tools is the account manager and API proxy published in the Antigravity-Manager repository. Its creator commissioned this website to help you install the app, connect your clients, and solve common problems.
Updated
Manage accounts and connect AI clients through a local API proxy.
Application source, releases, and community development on GitHub.
Commissioned by the app’s creator. The app and this site are independent of Google.
01 / People and source
Who makes Antigravity Tools?
lbjlaq owns the Antigravity-Manager repository, where the app is developed with community contributors. The project’s v5.0.0 README credits lbjlaq, jeikl, and cubelikeplayDaniel; the contributor list and commit history show the wider development work.
The name Antigravity Tools appears in the application, while Antigravity-Manager identifies its repository. Use that repository’s Releases page to trace a download to its version and source. Our download page helps you choose the package for your operating system.
Google operates its own Antigravity products and model services. This project’s software and guides are developed independently. Before connecting an account, review the security guide for credential storage, access controls, and account risks.
02 / This website
Why did the app’s creator commission this site?
This site brings installation, configuration, and troubleshooting instructions together around the tasks people use Antigravity Tools for.
- Setup guides take you from installation and accounts to connecting an IDE or API client.
- Troubleshooting starts with the symptom you see and helps you choose a useful next check.
- The API and configuration reference explains endpoints, credentials, and settings.
- Updates and compatibility helps you compare releases and prepare a backup before changing versions.
Application code, release packages, and development discussions live in the GitHub project. The guides link to those sources so you can check the version behind an instruction.
03 / License and attribution
What license applies to the application?
The application’s v5.0.0 LICENSE specifies Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International, abbreviated CC BY-NC-SA 4.0.
When sharing or adapting covered project material, the main conditions include:
- Attribution: keep the required credits and notices, link to the license, and identify changes you made.
- NonCommercial: the license grants reuse for noncommercial purposes. Obtain the necessary permission before using covered material outside that grant.
- ShareAlike: shared adaptations must use a license allowed by the ShareAlike terms.
Read the Creative Commons summary and full legal terms for the conditions, exceptions, and scope. Check the LICENSE included with the version you plan to reuse.
The project README credits Antigravity Team. Preserve the relevant project and file-level notices when distributing material. Dependencies and assets may carry their own licenses; access to Google services remains subject to those services’ terms.
04 / How the material is prepared
Who writes and checks the guides?
An AI assistant drafts and revises these guides using the project’s documentation, source code, release notes, and reported user problems. Technical checks compare the instructions with the named application version and, where practical, exercise them in an isolated test environment.
The checks include request formats, authentication, configuration persistence, and backup restoration. They use synthetic data and local test credentials. For example, the v5.0.0 access checks found that disabling a user token still allowed access to the model-list endpoint; the security guide explains the tested deletion method for revoking it.
The backup guide draws on restoration tests with a synthetic profile and database integrity checks. Actual Google sign-in, account eligibility, and recovery of your own conversations require checks in your environment.
Before applying an instruction, match its version, operating system, and deployment type to your installation. Use the linked source when a setting or screen differs, and keep a backup before changes that affect stored data.
05 / Help and feedback
Where can I ask a question or flag an error?
Use the project’s GitHub Discussions for community questions and Issues for reproducible application bugs. Search existing threads first so you can add a useful comparison to an ongoing discussion.
Keep API keys, OAuth tokens, account exports, and private conversation content out of public posts. Share a small, redacted example. GitHub threads are public community channels; response times depend on contributor availability.
06 / Dates and versions
How should I use a guide’s update date?
Read the date together with the application version named in the instructions. A recent article can cover a stable release while a preview changes the same feature.
This page was revised on November 2, 2026. Its license and contributor references point to v5.0.0, while the project links lead to current development and discussion. Use the updates guide to compare releases before changing your installation.