Antigravity CLI vs Conductor

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.

Conductor 0

No new sign-ups since 4 November, free users can't upgrade, and no price is shown. No protocol, no published price, no open free tier, no onboarding (0).

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.

Conductor 55

Harness reading. Each task gets a workspace, branch, terminal and diff, with pull requests and merges from the app, and an API for integrations; not re-read in detail (55).

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.

Conductor 25

Read as local software that is winding down. Installed from Conductor's own download, which stopped taking new users on 4 November 2026 (10). Closed source, so no public CI or issue tracker (0, 0). A dated changelog, newest 0.93.0 on 4 November (15). Version 0.93 (0). 10 + 0 + 0 + 15 + 0 = 25.

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.

Conductor 60

Harness reading. Docs for workspaces, review and merge, a Conductor API reference page linked from the docs (not read), and security and permissions pages (60).

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.

Conductor 58

0.93.0 on 4 November 2026 (30). Several dated releases in 90 days, per the changelog index (20). Discord, a subreddit and email for support (8). Closed app, no package or CI to read (0). 30 + 20 + 8 + 0 + 0 = 58. The local app gets new models and critical fixes only until early 2027.

Antigravity CLI 53

Framework reading (credentials and telemetry defaults, approvals and sandboxing, guardrails, audit, security programme), five lines. Credentials are a Google account sign-in kept in the operating system keyring, or a Gemini API key in settings.json. The README says using the CLI allows Google to collect Interactions until the user opts out (10). Since 1.3.5 on macOS and Linux and 1.4.4 on Windows 11 24H2 the default for personal accounts is Auto mode, which runs commands in the terminal sandbox, hides ~/.ssh, .env and, since 1.4.6, ~/.docker and ~/.kube, blocks network access outside approved domains, and has a separate agent review commands that leave the sandbox. Auto approves file edits and safe commands without asking, Turbo turns the sandbox off, and business accounts start in Default (18). Hooks run before and after tool calls and can block one, and since 1.4.11 a PreInvocation hook can stop a turn. No documented defence against prompt injection in fetched content was found (7). The CLI log records model resolution, and approvals show in the conversation, but no exportable audit log was found (10). google.com has a valid security.txt with reports to g.co/vulnz (per the 10 October check), antigravity.google serves none, no CLI advisory appears in the changelog, and NVD returns no CVE for Antigravity on 4 November. The repository's advisory page couldn't be read (8). 10+18+7+10+8 = 53.

Conductor 45

Closed app. Telemetry and data handling weren't read beyond the transition notice (10 of 30). A security and permissions page (10 of 20). No prompt-injection guidance found (5). No audit log found (5). SOC 2 Type II report at trust.conductor.build (15 of 20). 10 + 10 + 5 + 5 + 15 = 45.