Antigravity CLI vs Traycer

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.

Traycer 65

Local software. Builds for macOS, Linux and Windows, and package-manager publishing workflows (20). test.yml, CodeQL, OpenSSF Scorecard and secret scanning run 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). Host 1.5.3 (15). 20 + 15 + 0 + 15 + 15 = 65.

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.

Traycer 65

Harness reading. Mintlify docs, a protocol package and a CLI (65).

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.

Traycer 65

Harness reading. Model switching within an agent, agent-to-agent loops, a CLI and cross-device sync (65).

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.

Traycer 42

Harness reading. Code is processed in memory and not used for training, but Privacy Mode is opt-in for individuals, prompts may be logged with it off, and Sentry and PostHog 'may be enabled in release builds' (10 of 30). No approval model described in the README (8 of 20). No prompt-injection guidance (5). No audit log found (5). SECURITY.md, CodeQL, Scorecard and secret scanning (14 of 20). 10 + 8 + 5 + 5 + 14 = 42.

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.

Traycer 75

Commits on 6 November 2026 and host 1.5.3 (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 apps and CLI packages (15). CI with tests (10). 30 + 20 + 0 + 15 + 10 = 75.

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.

Traycer 60

MIT (30). README privacy section and a linked privacy policy (not read) (18 of 30). CHANGELOG.md, no deprecation policy (10). Analytics described as 'may be enabled', with no opt-out given in the README (8 of 20). 30 + 18 + 10 + 8 = 66.