For most of the last few years, "AI-assisted coding" has meant one thing: an autocomplete that gets uncannily good at finishing your sentence. You type a comment, a suggestion appears, you accept it, you move on. Google Antigravity — the agentic development platform Google introduced in late 2025 — is built around a different premise. Instead of completing your code, it hands work off to autonomous agents that can plan a task, execute it across your editor, terminal, and browser, and verify the result before handing it back to you.
That shift, from a tool that finishes your sentences to a system that finishes your tasks, is the whole point of Antigravity. It also creates a practical problem this post is really about: Antigravity isn't one app. It's a family of surfaces — a desktop command centre, a CLI, a set of IDE extensions, and a Python SDK — and picking the wrong one for your workflow means fighting the tool instead of using it. Below is what "agent-first" actually means in Antigravity, a breakdown of each variant with links to grab each one, and a map of which one fits which job.
Understanding "Agent-First" Development
At the centre of Antigravity is a fairly simple mechanical idea: an agent doesn't just suggest text, it plans, executes, and verifies changes across whatever surfaces the job requires — editing files, running shell commands, and even driving a browser to confirm a UI change actually works. Google frames this around two complementary interfaces. The Editor View looks like a conventional AI-powered IDE, with tab completions, inline commands, and a side-panel agent for moments you want to stay hands-on. The Manager Surface flips that around: it's an agent-first "mission control" where you spawn, orchestrate, and observe multiple agents working asynchronously across different workspaces, rather than babysitting one conversation at a time.
What ties the two together is what Google calls Artefacts — task lists, implementation plans, screenshots, and browser recordings that agents produce as they work. Instead of scrolling through a wall of raw tool calls to figure out what an agent actually did, you review the artefact — a plan, a diff, a recording of a passing test — and leave comments directly on it if something needs to change. Google describes the platform around four tenets that fall out of this design: trust (surfacing verification results instead of raw noise), autonomy (agents working across editors, terminals, and browsers without constant prompting), feedback (corrections applied iteratively through comments on artefacts), and self-improvement (agents building on knowledge from past sessions and feedback).
This is why developers moving off a purely manual "prompt, copy, paste, test" loop tend to describe the change in terms of delegation rather than assistance: you're not typing faster, you're handing off entire units of work and checking the output.
Deep Dive: Choosing Your Antigravity Variant
Because agent-first work happens across so many surfaces, Google ships Antigravity as several distinct products rather than a single app. You can find every download in one place on the official Antigravity downloads page.
Antigravity 2.0
Antigravity 2.0 is the flagship desktop application — the "command center" for running multiple agents in parallel. It groups related work into Projects, lets you operate across several workspaces at once, and can automate routine tasks with scheduled messages so agents keep working in the background rather than only while you're watching. This is the same standalone app that's sometimes referred to simply as "the Antigravity IDE" — the Editor View and Manager Surface described above both live inside it; 2.0 is its current version, not a separate product line. Grab it for Windows, macOS, or Linux from the official downloads page.
Antigravity CLI
The CLI is the lightweight, terminal-first way into the same agent ecosystem. It's built for developers who live over SSH or in minimal command-line environments: you can run autonomous coding agents, execute shell commands directly, and manage background subagents entirely from the keyboard, without opening a windowed app. Install it straight from the official CLI installation docs (one-line install scripts for macOS, Linux, and Windows).
Antigravity for IDEs (Extensions)
Rather than pulling developers out of editors they already use, Google also ships official Antigravity extensions for Visual Studio Code, Visual Studio (in preview), the JetBrains suite (IntelliJ IDEA, PyCharm, WebStorm, GoLand, CLion, Rider), Zed (enterprise preview), and Xcode. Google describes these as lightweight, high-performance integrations rather than a full agent hub — useful for inspecting a specific code path, reviewing a compiler diagnostic, or making a localized fix, while still sharing conversations and context with the rest of the Antigravity ecosystem.
Antigravity SDK
For teams that want to build rather than just use, the Antigravity SDK is a Python toolkit for prototyping custom agents with minimal code. It's aimed at developers who want to iterate on their own agentic applications, automate specific software engineering tasks, and run evaluations against Google's Gemini models programmatically, rather than working through any of the surfaces above. Get it with pip install google-antigravity from PyPI, or browse the source on GitHub.
Use Case Mapping: Which One Do You Need?
- For terminal heavyweights and remote servers: Antigravity CLI.
- For in-editor enhancements without leaving your current setup: Antigravity for IDEs.
- For immersive, standalone coding sessions: Antigravity 2.0's Editor View.
- For high-level, multi-project orchestration and background automation: Antigravity 2.0's Manager Surface.
- For custom, programmatic agent-building: Antigravity SDK.
Conclusion
None of these surfaces is a strictly better version of another — they're built for different moments in a developer's day. The CLI meets you where remote and terminal-first work already happens; the IDE extensions meet you inside the editor you already use for quick, localised fixes; Antigravity 2.0 is where the actual multi-agent orchestration lives; and the SDK is for the smaller group of teams building their own agent tooling on top of Gemini. The productivity gain from Antigravity doesn't come from picking the "best" surface — it comes from matching the surface to the task in front of you, and from treating the agent as something you delegate to and verify, rather than something you write code alongside line by line.
A note on freshness: Antigravity is a genuinely new product line — Google introduced it in November 2025, with the 2.0 update following in 2026 — and pricing, IDE support, and feature availability are all still evolving quickly. It's worth checking the official Antigravity site (antigravity.google) before committing a team workflow to any one surface.
