Antigravity learn hub
Key Highlights
Every tutorial, API walkthrough, concept primer, and access guide for the Antigravity browser collected in one place — organised by category so you can find the right depth for where you are in the learning curve.
The Antigravity learn hub is the starting point for anyone who wants to understand how the browser works, extend it with the API, or simply get through the sign-in and online-access setup without reading scattered release notes. The hub is organised into four categories: getting started, developer guides, concept explainers, and access references. Within each category the pages are ordered by typical reading sequence — although every page is also self-contained, so you can jump in at any level.
Antigravity is a dense product. It ships a Chromium browsing surface, an agent orchestrator, a code editor side-pane, a tool registration layer, and an artifact runtime — all in one desktop application. That breadth is useful once you know your way around, but it creates a steeper first-hour experience than a single-purpose tool. The learn hub exists to flatten that curve. Each page targets a specific question and links forward to the next logical stop.
Getting started
New to the browser? Start here. The getting-started walkthrough covers the eight-step path from downloading the installer to completing your first agent run. It explains what happens at each prompt, what the agent produces, and how to read the artifact timeline after the run finishes. The walkthrough is written for developers who have not used an agentic browser before and want a concrete first-run experience rather than an abstract feature overview.
After the getting-started page, the natural next stop is the login reference. Antigravity uses your Google account for identity, and the distinction between personal accounts and Workspace tenant accounts affects which features are available and which data boundaries apply. The login page explains the scopes the product requests, when token rotation happens, and how to sign out cleanly.
Developer guides
The API guide covers the programmatic surface for extending the agent runtime: endpoint catalogue, authentication, tool registration, webhooks, and example payloads. It is the right reference if you want to connect the browser to an internal service, script agent runs from the shell, or build a custom tool that appears in the agent's tool list.
The online-access guide explains the split between the web console and the desktop application. Some capabilities — artifact review, lightweight task launch — are available through a browser-based surface. Others require the desktop app. That page maps the feature matrix and covers thin-client mode and cloud-agent runs for teams that cannot install native apps on every machine.
Concept explainers
Several adjacent terms lead people to this reference site who are researching the product rather than using it. The concept pages cover: the "anti gravity AI" metaphor and how it maps to the canonical product; the "Google Antigravity" and "Antigravity Google" naming split and what each typically returns; the "gravity AI" disambiguation for the short-form search term; and the "Google Code" naming history for the legacy code-hosting service that predates this browser by over a decade.
These pages are deliberately lower-density on the brand name and higher-density on the compound term being disambiguated. If you landed on this site searching for one of those adjacent phrases, the dedicated concept page is the right read.
Access references
The access category covers download, install, and platform guides. The anti-gravity-download page explains the common space-separated spelling and points to the canonical installer. The anti-gravity-app page covers the desktop application form factor across Windows, macOS, and Linux, and the Chrome-extension bridge for teams still running Chrome profiles. The anti-gravity-download and anti-gravity-app pages overlap slightly by design — different searchers land on different spellings and both need to reach the same install outcome.
Learn hub category map
| Category | Pages | Estimated time to read |
|---|---|---|
| Getting started | Getting Started, Login | 12–18 min |
| Developer guides | API, Online access | 15–22 min |
| Concept explainers | Anti gravity AI, Google Antigravity, Antigravity Google, Gravity AI, Google Code | 20–30 min |
| Access references | Download, App, Anti gravity download, Anti gravity app | 10–15 min |
| Legal | Privacy policy | 5 min |
The table above is a reading-time estimate, not a requirement. Most engineers spend fifteen minutes in the getting-started walkthrough, bookmark the API page for later, and then check the online-access guide only when they hit the first thin-client scenario. That is a perfectly sensible path.
For a policy-level view on AI agent tools in developer workflows, the OECD AI Policy Observatory publishes governance frameworks that some teams use alongside their internal review of agentic browser adoption.
Jump to a learn-hub section
Learn hub — frequently asked questions
Common questions about navigating the Antigravity documentation and what each section covers.
-
What does the Antigravity learn hub cover?
The learn hub organises every reference article on this site into four categories: getting-started walkthroughs, API and developer guides, concept explainers for adjacent search terms, and access guides covering sign-in, online mode, and platform availability. Each article is self-contained but also links to the natural next stop in the reading sequence.
-
Is there a recommended reading order for engineers who are new to the browser?
Start with the Getting Started page, which covers installation through to a first completed agent run. Then read the login reference to understand identity scopes and the Workspace-versus-personal distinction. After that, the API and online-access guides are useful in any order depending on whether your immediate need is programmatic access or thin-client setup.
-
How often are learn-hub pages updated?
Pages are revised whenever the product ships a change that affects the documented workflow. Release notes link back to the affected learn-hub pages so you can identify what changed without reading the full changelog. The dateModified value in each page's schema reflects the last substantive edit.
-
Why are concept explainer pages included alongside technical guides?
Several adjacent search terms — "anti gravity AI," "gravity AI," "Google Code," "google antigravity" — regularly return this site in search results. Those searchers often arrive without a clear map of how the product relates to the term they searched. The concept pages serve that audience without diluting the technical content on the getting-started and API pages.
-
Where do I go if the learn hub does not cover my question?
The docs centre has broader coverage, including the release notes archive, the security model, and the engineering team page. The contact page is available for questions not covered by any reference article on the site. Antigravity support is email-first — no phone line.
Popular Antigravity topics
The most-visited pages across the Antigravity reference site — tap to navigate directly.