Google Antigravity

Overview

Google Antigravity is Google’s agent-first software development platform: a family of products that lets developers (and non-developers) orchestrate AI agents that plan, write, run, test, and verify work across an editor, terminal, and browser. Official home: antigravity.google. Public preview launched November 18, 2025 alongside Gemini 3; the product is proprietary (not open source) and free to download for macOS, Windows, and Linux with plan-based rate limits.

Maker: Google. Primary job: move coding from “chat in a sidebar” to task-level agent orchestration—spawn agents, review verifiable Artifacts (plans, task lists, screenshots, browser recordings, walkthroughs), and iterate without reading every raw tool call. As of mid-2026 the surface includes:

• Antigravity (2.0 flagship app) — standalone command center for parallel local agents, projects, scheduled tasks; not tied only to an IDE window.
• Antigravity IDE — agentic IDE (VS Code–class fork lineage; community debate about Windsurf-related history) with Agent Manager / side panel, Tab completions, and deep codebase context.
• Antigravity CLI (agy) — terminal agent harness sharing the same runtime as the desktop products; Google steers former Gemini CLI users here.
• Antigravity SDK — programmatic access to the same agent harness (tools, MCP, skills, hooks, safety policy) for custom products and research-style loops.

Default intelligence is the Gemini family (e.g. Gemini 3.x Pro / Flash, Gemini 3.5 Flash called out in later product posts). Higher Google AI tiers unlock broader model access (community and press report third-party models such as Claude Sonnet/Opus variants and open GPT-OSS-class options on eligible plans—confirm current model list in Antigravity models docs). There is no public “bring your own API key” path for frontier models on the consumer Google AI billing path; capacity is quota- and credit-shaped, not raw BYOK.

Key features

• Agent Manager / multi-agent orchestration — Spawn and supervise multiple agent threads across workspaces (e.g. refactor in one thread while tests write in another). Manager surface is the differentiator versus linear sidebar chat in classic Copilot-style tools.
• Editor view + Manager surface — Hands-on IDE mode (Tab completions, inline agent) for synchronous work; Manager mode for asynchronous, multi-agent, multi-folder projects.
• Artifacts trail — Agents produce reviewable deliverables: implementation plans, task lists, walkthroughs, code diffs, screenshots, browser recordings. You can comment on artifacts (doc-style feedback) so agents incorporate notes without dumping you into opaque tool logs.
• Browser-in-the-loop — Integrated browser automation (Chrome debugging session / /browser patterns) so agents can implement UI, launch apps, and verify in a real browser—not only unit tests.
• Projects spanning folders — A project can include multiple folders (e.g. frontend + backend) with isolated agent settings, security presets, and MCP tool allow-lists per project.
• Security presets & permissions — Per-project controls for whether terminal/file actions require review, agent “always proceed” vs plan-first behavior, allowed paths/URLs, and which MCP tools the agent may call.
• MCP (Model Context Protocol) — Local and remote MCP servers; shared config under ~/.gemini/config/mcp_config.json across Antigravity 2.0, IDE, and CLI. One-click-style Google Cloud MCP integrations plus custom servers.
• Skills — Progressive-disclosure skill packages (SKILL.md + optional scripts/assets) at global (~/.gemini/config/skills/) or project (.agents/skills/) scope so agents load specialized instructions only when relevant.
• Plugins / hooks — Bundles of skills, rules, MCP, hooks, and sub-agents (CLI docs emphasize plugins as namespaced deployable units; Gemini CLI extensions have a migration story into Antigravity CLI).
• Scheduling — One-off and recurring scheduled agent tasks (UI Schedule panel and /schedule-style flows) for maintenance, reminders, or unattended agent work.
• CLI parity — agy CLI uses the same harness as desktop; conversations can be pulled into Antigravity 2.0; migration guides for Gemini CLI skills/MCP.
• SDK — Same runtime for embedding agents: built-in tools, custom Python callables, MCP, sub-agents, skills, declarative safety policy, lifecycle hooks, stateful multi-turn sessions.
• Unlimited Tab (per plan docs) — Official plans messaging highlights unlimited Tab completions and Command-style requests on eligible tiers, with agent/model usage rate-limited separately.
• Enterprise path — Teams via Gemini Enterprise Agent Platform / Google Cloud credentials and Cloud terms (enterprise use cases emphasize corporate data not used for training when on the Cloud path—verify current enterprise docs).

Pricing

Individuals do not buy a separate “Antigravity Pro” SKU in isolation. Live billing maps Antigravity quotas and model access to Google AI plans (Google One AI Pro / Ultra) plus optional AI credits for overages. Free/Individual download remains available with basic weekly rate limits. Always re-check antigravity.google/pricing and docs/plans—quotas have changed multiple times since launch.

Tier (typical individual path)	List price (USD/mo, approximate)	Antigravity capacity (per official plan messaging)
Individual / free	$0	Download free; baseline Gemini access; meaningful but limited quota refreshed on a weekly cadence; unlimited Tab/Command called out on marketing tiers
Google AI Pro	~$20	Entry paid quota; high “sprint” capacity with ~5-hour refresh until weekly hard cap; positioned for hobbyists/students and IDE-heavy (less agent-heavy) use
Google AI Ultra (mid tier, from May 2026)	~$100	~5× Pro token rate-limit multiplier for Antigravity (and Gemini app) per Google’s May 2026 plan post
Google AI Ultra (top tier)	~$200 (was ~$250, reduced May 2026)	~20× Pro multiplier; highest weekly limits; third-party model access called out for Ultra in models/plans docs; marketed as daily-driver for heavy agent use
AI credits / on-demand	Usage top-ups	Pro/Ultra can buy pay-as-you-go AI credits for Antigravity (and related products) after quota; limited-time bonus credit promos have appeared for Ultra subscribers
Enterprise / org	Contact / Cloud SKUs	Gemini Enterprise Agent Platform under Google Cloud terms; Workspace/GCP login paths for commercial data protections

How limits actually work (community + docs consensus): Plans describe a short-window “work pool” (often ~5 hours refresh for Pro/Ultra) plus a weekly baseline/hard cap. Hitting the weekly cap overrides the short refresh—you wait for the next weekly period or buy credits. Free users moved toward weekly-only refreshes after Pro/Ultra got priority. Exact token numbers are not published as fixed public tables the way some API products are; users reverse-engineer usage and regularly report large swings month-to-month.

Limits & gotchas

• Rate limits dominate the experience — Multi-agent + browser verification burns quota fast. Mid-task stalls when weekly caps hit are the #1 complaint on r/google_antigravity and Google AI forums.
• No transparent BYOK for core agent models on consumer path — Capacity is Google-plan shaped. If you need spend control via your own Anthropic/OpenAI keys in-editor, Cursor/Claude Code-style products fit better.
• Quota opacity — Docs speak in “generous / highest” language and multipliers; absolute token tables are incomplete. Plan FinOps around frustration buffers, not spreadsheet precision.
• Privacy / training on consumer accounts — Additional ToS and community analysis: interactions may be stored and used under Google consumer terms unless you are on Workspace/GCP enterprise paths with different protections. Telemetry toggles exist; “disable telemetry” is not a full enterprise DPA. Commercial-code builders should read enterprise use-case docs and legal review carefully.
• Security track record at launch — Within ~24 hours of release, researchers (Forbes/Mindgard; Embrace The Red; PromptArmor) demonstrated config/backdoor, prompt-injection, and browser-subagent data-exfil style issues. Google published “known issues” for VRP. Agent tools that run shell + browser are inherently high risk—use review policies, least-privilege MCP, and do not point agents at secrets without vault discipline.
• Account enforcement surprises — Reports of Ultra accounts restricted for heavy or wrapper-based usage even when users believed they stayed in quota (Techzine / Register / forum threads). Terms around automation wrappers are contested in community discussion.
• Product churn — May 2026 Antigravity 2.0 repositioned surfaces (standalone app vs IDE vs CLI). Some users called install-path collisions and UX resets a “bait and switch” (HN, independent blogs). Expect further Google-style product consolidation.
• Performance / heaviness — Electron-class IDE; community notes slow file indexing vs lean VS Code on large trees. Manager-first workflows can feel like “supervising interns” rather than pair-programming (XDA comparison framing).
• Fork lineage debate — Press notes debate whether the IDE is a pure VS Code fork or related to Windsurf’s VS Code fork. Practically: VS Code extension/keybinding migration is usually quick; exact OSS provenance is secondary to product behavior.
• Not a drop-in for every enterprise checklist — Independent enterprise comparisons (e.g. Augment Code write-ups) still prefer Cursor-class products for product-specific SOC 2 packaging, Privacy Mode narratives, and team governance maturity—even when Antigravity has an Organization/Cloud tier.

Community sentiment

Sentiment is polarized and quota-driven. Launch week (Nov 2025) Reddit/HN and reviews praised free Gemini-class access, multi-agent Manager UX, and Artifact review. Through 2026, dedicated subreddit r/google_antigravity became a support board for weekly quotas, Ultra users stuck at 100% limits, and “is there any reason to still use this?” threads. Large HN threads on prompt-injection exfil and the May 2026 “bait and switch” post drew hundreds of comments each.

Praise themes:

• Agent Manager multi-threading feels closer to orchestration than single-chat coding; good for parallel refactor + test + browser verify.
• Artifacts reduce “trust the black box” anxiety versus raw tool logs.
• Deep Gemini integration and Google ecosystem plugins/MCP; strong for Cloud Run / GCP-oriented builds when MCP is configured.
• Planning mode quality praised by some engineers vs Cursor on certain codebases (subreddit reviews).
• VS Code familiarity + free entry made early adoption easy.

Criticism themes:

• Quota cliff after launch generosity; Pro seen as inadequate for real agent loops; Ultra still not “unlimited.”
• Security vulnerabilities at launch and ongoing agent tool risks.
• Consumer training/privacy ambiguity versus enterprise Cloud terms.
• 2.0 product reshuffle and install UX friction for existing users.
• Heavy IDE performance; comparison pieces that prefer Cursor for daily 30-second edits and Claude Code for deep reasoning.

Who should use it

• Gemini / Google Cloud–centric developers who want one Google-native agent stack (IDE + CLI + SDK) and already pay Google AI Pro/Ultra or Cloud enterprise.
• Teams delegating long, multi-surface tasks (implement → run → browser verify) who value Artifacts and Manager oversight more than pure Tab speed.
• Individuals migrating off consumer Gemini Code Assist / Gemini CLI after the June 2026 consumer cutover.
• Builders prototyping agent products with the Antigravity SDK who want Google’s harness improvements without reinventing tools/MCP/hooks.
• Hobbyists and learners okay with free/Pro limits for exploration, tutorials, and light projects.

Who should not default here: shops that need hard ZDR/HIPAA-style guarantees on consumer paths; teams that require multi-model BYOK and predictable API burn; engineers who mainly want fast Tab + Composer-style daily editing (Cursor); deep single-agent terminal reasoning fans who already love Claude Code; anyone unwilling to babysit weekly quotas on agent-heavy work.

Alternatives

• Cursor — Mature multi-model AI IDE; stronger daily-driver consensus, Privacy Mode / SOC 2 packaging narrative, Composer pools. Prefer when reliability and model choice beat Google-native multi-agent theater.
• Claude Code — Anthropic’s interactive coding agent (CLI/IDE/web). Prefer deep reasoning, repo-scale agent loops, Anthropic billing—not Gemini quotas.
• GitHub Copilot — Broad IDE coverage and enterprise familiarity; less “Manager of many local agents,” more assist + agent features inside Microsoft’s stack.
• Windsurf — Agent-oriented VS Code–class editor (Cognition); competitor in agentic IDE positioning; relevant given historical fork discussions in the press.
• Replit — Cloud IDE + agent experiences when you want environment and hosting in one place.
• VS Code + extensions — Stay stock and bolt on Copilot/Claude/Gemini extensions if you refuse a full agent IDE switch.
• Google Jules / remaining Gemini Code Assist enterprise — Adjacent Google coding products; enterprise GCA may still fit “assist inside current IDE” without Antigravity.
• Aider / open terminal agents — Local/open workflows when you want control and your own keys without Google plan coupling.

See also VersusTools comparison: Antigravity vs Cursor.

Verdict

Google Antigravity is a real, shipping agent platform—not a demo slide. Its best version of itself is multi-agent orchestration with Artifacts and browser verification on Gemini, plus a shared harness across desktop, CLI, and SDK. For Google-stack developers and people who already live in Google AI Ultra, it can be a daily command center.

Its worst version of itself is an Electron IDE that looks free/cheap, then locks agent work behind opaque weekly caps, security landmines if you rubber-stamp tool use, and consumer data terms that make legal teams nervous. Independent reviews in 2026 consistently land on the same split: Antigravity for autonomous multi-surface Google-native agents when quota holds; Cursor (or Claude Code) for predictable daily production coding.

Bottom line: try the free download if you are Gemini-curious; treat Pro as a taste test; only standardize if measured Ultra/enterprise quota matches your agent volume—and keep a backup IDE when Google moves the rate-limit goalposts again.