Antigravity CLI vs Paseo

Antigravity CLI 30

Harness reading of the published rubric. No payment protocol in the docs, the pricing page or the plans page (0). Plan prices are public without a login, with a $0 individual plan and Gemini Enterprise Standard or Plus from $30 a seat a month, and Google AI Pro at $20 and Ultra at $100 or $200 a month per Google's 19 May 2026 post. Overages draw on AI credits at Gemini Enterprise consumption rates, which were not read, so this is plan-level pricing (10). The pricing page lists the $0 plan as needing no subscription, and none of the pages read asks for a payment method, but the account flow was not tested (20). Sign-in is a browser flow with a Google account, or a Gemini API key set by hand, and the CLI won't start unauthenticated (0). 0+10+20+0 = 30.

Paseo 60

Free self-hosted software with nothing to buy, so 0 for a protocol and 20 each for public pricing, a free tier and onboarding with no sign-up, 60.

Antigravity CLI 78

Framework reading. No published JSON Schema for settings.json, mcp_config.json or hooks.json was found, although the docs type each key (10). llms.txt at antigravity.google/llms.txt, and every docs page has a Markdown copy (10). Pages say when to use each permission preset and execution mode, what each allows and when the sandbox applies (15). Presets, modes, output formats, status values and effort levels are enumerated (13). The headless page documents the output envelope, the status values and exit codes, with a jq example (15). A dated changelog on the docs site and versioned release notes and tags in the repository (15). 10+10+15+13+15+15 = 78.

Paseo 65

Harness reading. Public docs, a CLI and plugin examples in the repository (65).

Antigravity CLI 55

Closed source, with clear terms. The binary is under the Google Antigravity Additional Terms, the Universal Terms and the Privacy Policy (15). The terms say Interactions are recorded while the Service runs and used to evaluate, develop and improve Google and Alphabet products and machine learning, that Google employees and contractors may review them, and that the user can ask for deletion by email. The README and settings page agree, but no retention period appears in the pages read (15). Dated notices exist for the Gemini CLI transition and for the removal of Claude Sonnet 4.6, Claude Opus 4.6 and GPT-OSS 120B, now set for 18 November 2026, and since 1.3.0 the CLI shows announcement cards for deprecations, but there is no written deprecation policy for the CLI (10). The README says collection is on by using the CLI with an opt-out at any time, and Enable Telemetry in /config turns it off and is always off for business accounts. The settings page no longer calls it anonymous usage statistics, but it doesn't state the default and its CLI line says only "usage data" (16, judgement call). 15+15+10+16 = 56.

Paseo 68

Apache 2.0 for everything but third-party components (30). No telemetry and agents run on your machine (22 of 30). CHANGELOG.md, no deprecation policy (10). States no telemetry (20). 30 + 22 + 10 + 20 = 82.

Antigravity CLI 78

Framework reading, adapted to a harness driven by a pipeline. MCP tools can be allowed or refused by server and tool, and a 20,000-token budget for user rules stops large rule sets from crowding out skills and MCP tools (16). No turn or spend cap appears in the flag reference, and --print-timeout sets a wall-clock limit only, with no limit by default (10). The JSON envelope carries a status field and token usage, and since 1.4.11 a finished_reason field says why a turn ended early (16). Exit codes are documented, but a tool soft-denied in headless mode still exits 0 (14). --continue and --conversation resume earlier runs (14). A Python SDK on PyPI, which is a separate package, and no second SDK language for the CLI (8). 16+10+16+14+14+8 = 78.

Paseo 70

Harness reading. A self-hosted daemon that agents can use to create worktrees, launch other agents and talk to them, scriptable from the CLI (70).

Antigravity CLI 43

Local-package reading. An official installer for macOS, Linux and Windows, with an Android build for Termux, that checks a SHA-512 checksum from Google's release manifest before it installs (install.sh re-read on 4 November) (20). No public CI or test suite, since the repository holds no source and no workflows, only issue templates (0). Open issues and pull requests could not be read, so the crash and regression line is unchecked (0). Behaviour changes ship in patch releases as Changed or Improved bullets with no breaking-change heading, such as 1.4.6 (23 October) closing ~/.docker and ~/.kube to sandboxed commands, and 1.2.10's exit-code change (8). Version 1.x, so stable under the rule (15). 20+0+0+8+15 = 43.

Paseo 50

Local software. Desktop builds, an Android APK, a Docker image and a Nix package (20). ci.yml on the repository; pass state not read (15). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). CHANGELOG.md (15). Version 0.15.3 (0). 20 + 15 + 0 + 15 + 0 = 50.

Antigravity CLI 68

1.4.12 on 30 October 2026, marked Latest in the docs changelog, 5 days before this check (30). 56 tagged releases from 1.1.11 (6 August) to 1.4.12, each with a changelog entry; 1.5.0 is tagged and in the repository changelog on 4 November but not yet in the docs changelog, so it isn't counted (20). Responsiveness rests on a public changelog, a community forum linked from the terms and the GitHub repository, but no replies could be read (8). The google-antigravity Python SDK is a separate package and no SDK for the CLI itself was found; PyPI couldn't be read on 4 November, so the line rests on the 10 October reading (10). No public CI or dependency list for the CLI, since the source is not published (0). 30+20+8+10+0 = 68.

Paseo 75

v0.15.3 and commits on 7 November 2026 (30). More than three releases in 90 days (20). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). Current builds (15). CI on push (10). 30 + 20 + 0 + 15 + 10 = 75.