Google Antigravity
Personal Google account holders who want Google's agent-first IDE, app and CLI (`agy`); Google's named destination for Gemini CLI personal users and Jules users.
Personal Google account holders who want Google's agent-first IDE, app and CLI (`agy`); Google's named destination for Gemini CLI personal users and Jules users. Facts below were checked on 5 Nov 2026. They are not a FitScore unless this page shows one.
This description identifies the product. It is not a test result, a rank, or a FitScore.
Scores by job
- Coding agents79/100
Which coding agent should I use to fix bugs and add features in my repo?
TestedRank 5 · 5 Nov 2026 · agy 1.5.1 · Google AI Pro ($19.99/mo) via Google OAuth, signed in by Sarel (interaction data collection opted out)Provisional: one test project, tested 5 Nov 2026
- Output quality
- 4/5
- Reliability
- 4/5
- Cost and free tier
- 3/5
- Speed
- 5/5
- Setup friction
- 4/5
- Agent, API, and MCP support
- 5/5
- Privacy and data
- 3/5
Round 3, mean of per-task scores over T1h-T6 = 4.333, rounded
Round 3, mean of per-task scores over T1h-T6 = 4, rounded
Google AI Pro, $19.99/month, covered all 18 runs with no rate or usage limit message (Antigravity limits refresh every 5 hours with a weekly cap). The CLI reports tokens but not cost: 590k input tokens, 2.16M cache reads, 100k output and 33k thinking tokens across the 17 runs that returned JSON. 'Use AI Credits' is off by default, so nothing extra was billed.
Round 3, mean of per-task scores over T1h-T6 = 5, rounded
The official installer took 3 s with no account. The --skip-path flag in the docs was rejected, which was one snag. Sign-in is Google OAuth with a pasted code, which works without a local browser. It took about 2 min 15 s (11:22:33 to 11:24:48 SAST), after a first headless attempt timed out waiting 60 s for the code. The tool's own steps took ≤10 min with one snag = 4, using the same editorial rule as the Codex setup score. Counting from the 10:42 install to the first successful run would give 2.
Headless `agy -p --output-format json` (documented; it needs a prior sign-in). The MCP server was configured in the documented ~/.gemini/config/mcp_config.json. T6 passed 3/3 with no prompt; each run called `get_issue` for #14.
Hosts observed in the 18 task runs: - daily-cloudcode-pa.googleapis.com (model, 14.4 MB up) - aicode.googleapis.com - www.googleapis.com and oauth2.googleapis.com (auth) - lh3.googleusercontent.com (account avatar) - the auto-updater on run.app (2 runs) - play.googleapis.com: 37 connections and 5.3 MB uploaded, even though Sarel opted out of interaction data collection at sign-in. play.googleapis.com is not named in Antigravity's docs, so it is one unexplained destination = 3. Its 'Enable Telemetry' setting collects interactions 'for use in evaluating, developing, and improving Antigravity and models'. For the CLI, that choice is saved with the account.
Round 3, 5 Nov 2026, pack 0.3.0: 18 runs, 6 tasks, 3 runs each, zero human interventions. Google Antigravity CLI agy 1.5.1 passed 14/18. Model: the CLI default, Gemini 4 Argon (Medium), via Google AI Pro. The Antigravity series (11:32 to 12:30 SAST) overlapped the Cline series on the same machine.
What failed
- T4 was 0/3 under the same false-claim rule as OpenCode T4 run 1 in round 2. Run 1 never says to add tests when adding a command. Runs 2 and 3 claim that during runCli dispatch the helpers, including normalizeTitle, validate inputs and throw. normalizeTitle in src/title.ts never throws, and TodoStore calls it, not runCli. Quality 2 for each run. Treating those two claims as over-broad rather than false would make quality 5, reliability 4, and the FitScore 85.
- T3h run 1 hit the cap. The model stream stalled and the harness killed the run at 1549.9 s (limit 1500 s). The code left behind passed 50/50 hidden tests, but a cap hit scores quality 1. Runs 2 and 3 took 85 s and 110 s.