Head to head · Agent harnesses · October 2026 research run

Antigravity CLI vs Click

Antigravity CLI scores 56.6 (C) on agent readiness against Click's 48.6 (D), and leads in 5 of 7 scored categories. Click leads on schema & documentation. Both do agent harnesses.

Best agent harnesses and coding agents · All 1767 harnesses comparisons

Which one, for what

Antigravity CLI C

Best for Developers on Google AI plans or Gemini Enterprise who want a terminal agent with a sandbox on by default and access to several model families, depending on plan.

Ahead on

  • Reliability, 43 against 35
  • Security & auth, 53 against 41
  • Payments & pricing, 45 against 15
  • Maintenance & community, 68 against 25
  • Transparency & trust, 55 against 44

Watch for

Closed source. The repository holds the README, changelog and examples, with no source and no licence file

Click D

Best for Product teams that want to embed an agent per customer, ticket or document without running the loop, sandbox or browser themselves, with any model.

Ahead on

  • Schema & documentation, 84 against 78

Also in its favour

  • A hosted endpoint, with nothing to install
  • No incidents deducted, where Antigravity CLI loses 3 points for them

Watch for

No status page, SLA or public changelog found

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Antigravity CLI +43

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.

Click 25

Closed service with no dated changelog. The newest first-hand date is API version 2026-10-19, 30 days before this check, read as within 90 days rather than within 30 since nothing says what shipped then (20). No dated release entries to count (0). Support is by email to the founder, per the terms. No public changelog, issue tracker or community channel was found (5 of 15). No official SDK (0). No public package or CI to check (0). 20 + 0 + 5 + 0 + 0 = 25.

Payments & pricing Antigravity CLI +30

Antigravity CLI 45

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. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Click 15

No x402, MPP or L402. The only 402 is card_verification_required (0). Plan prices are public, Free at $0 and Pro at $199 a month with stated allowances, but no per-unit price (15). The Free plan exists, but writes return 402 until a card is verified in the dashboard (0). A person signs up in a browser, verifies a card and creates the key (0). 0 + 15 + 0 + 0 = 15.

Security & auth Antigravity CLI +12

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.

Click 41

Platform API keys are revocable, but each has full access to its tenant, including key management. The MCP server's OAuth tokens through WorkOS carry scopes for the MCP endpoint only (20 of 30). Tool grants limit each agent to named tools, and sessions can override grants, but approvals are left to the customer's application and no read-only key was found (8 of 20). Agents read web pages, browser content and MCP results. The docs tell users to keep secrets out of messages and keep MCP tools from returning stored secrets, but give no prompt-injection guidance (3 of 15). Every top-level and nested tool call is recorded and listed per session, and webhook deliveries can be listed (10 of 15). No security.txt (404), disclosure policy or certification found (0). 20 + 8 + 3 + 10 + 0 = 41.

Transparency & trust Antigravity CLI +11

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.

Click 44

Closed service under terms based on the Common Paper Cloud Service Agreement 2.1, dated 12 October 2026, under Delaware law (15 of 30). The privacy statement lists what is collected, names PostHog with session replay for the website and dashboard, and says staff may access service content for support and to improve the service. Retention is "as long as reasonably needed" with no periods. The docs say Click-created sandboxes are deleted with their session (10 of 30). No deprecation policy. The terms promise 30 days' notice of price changes (3 of 20). Providers are described by category, with PostHog the only one named, and processing in the United States and other countries (5 of 20). 15 + 10 + 3 + 5 = 33.

Reliability Antigravity CLI +8

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.

Click 35

Hosted lines, for the HTTP API. No status page is linked from the site or the docs (0), so no incident history could be read (5). Concurrent session limits are published per plan (2 on Free, 50 on Pro) with body size limits of 16 MiB, but no request rate limits were found (8 of 15). 429 concurrency_limit_exceeded and the 503 codes are documented, the conventions say to retry 503 after a short wait, and request_id makes submissions safe to retry. No Retry-After header is documented (12 of 15). No SLA in the terms, which leave usage limits to Click's discretion (0). The API carries no beta or preview label (10). 0 + 5 + 8 + 12 + 0 + 10 = 35.

Schema & documentation Click +6

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.

Click 84

A public OpenAPI 3.2 document at useclick.ai/reference/openapi.yaml, API version 2026-10-19, rendered in full in llms-full.txt with 49 operations (25). llms.txt, llms-full.txt and a Markdown page per operation (10). The introduction says when to use Click, what Click runs and what the application owns, and each area explains its lifecycle (17 of 20). Typed schemas with 557 required-field markers in llms-full.txt and enumerated statuses, and string and body limits stated (12 of 15). A quick start with curl, a runnable Python example, and every operation lists its error codes by status (15). Paths are under /v1 with a dated API version, but no public changelog was found (5 of 15). 25 + 10 + 17 + 12 + 15 + 5 = 84.

Score by category

CategoryWeightAntigravity CLIClickEdge
Reliability16%4335Antigravity CLI +8
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7884Click +6
Agent ergonomics13%7879Click +1
Security & auth14%5341Antigravity CLI +12
Payments & pricing10%4515Antigravity CLI +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6825Antigravity CLI +43
Transparency & trust7%5544Antigravity CLI +11
Negative events≤15-30
TotalC 56.6/100D 48.6/100

Facts side by side

FactAntigravity CLIClick
KindAgent harnessHTTP API
VendorGoogleClick AI Labs, Inc.
Hosted endpointno (local only)https://api.useclick.ai/v1
TransportsHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceProprietary. The repository holds the README, changelog and examples, with no source and no licence file. Use is under the Google Antigravity Additional Terms of Service, the Google Terms of Service and the Privacy PolicyProprietary hosted service under Click's Terms of Service, based on the Common Paper Cloud Service Agreement 2.1
Tools exposednone23
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-302026-10-19
Terms last updatedno date given2026-10-12
Privacy policy last updated2026-10-012026-10-12
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text

How the scores have moved

Verdicts

Antigravity CLI

Google's terminal agent, a closed-source binary whose default Auto mode runs commands in a terminal sandbox on macOS, Linux and Windows 11, with documented headless JSON output. Interactions are collected for Google product improvement unless users opt out, a headless run exits 0 when a tool is denied, and 1.4.7 fixed a cross-user token flaw without an advisory.

Click

Click's API is described by a public OpenAPI 3.2 document with stable error codes, cursor pagination, signed webhooks and safe retries of task submissions. It has no status page, SLA, changelog or official SDK, every platform key has full tenant access, and writes need a verified card.

Before you call either

Antigravity CLI

  1. Read the status and finished_reason fields from --output-format json and read stderr too. A tool refused for lack of approval still exits 0
  2. Pre-approve each shell command and tool a headless run needs with action(target) rules under permissions.allow in ~/.gemini/antigravity-cli/settings.json, because headless runs cannot ask
  3. Export GEMINI_API_KEY after setting modelProvider to gemini. The CLI won't start when the key is missing, and setting the variable alone has no effect
  4. Turn off Enable Telemetry in /config before running on private repositories if Interactions should not be used for product improvement
  5. Grant sandbox access to ~/.docker or ~/.kube explicitly since 1.4.6 if a task needs Docker or Kubernetes credentials

Click

  1. Send a unique request_id with each submission and reuse it when you retry, so a task doesn't run twice
  2. Branch on error.code, not the message. Retry 503 codes after a short wait
  3. If you get 429 concurrency_limit_exceeded, put an idle session in standby to free its slot
  4. Read a submission until it is done, cancelled or failed, then fetch the answer entry it names
  5. Grant each agent only the tools it needs. Approvals and budgets are left to your application

Questions

Which is better for AI agents, Antigravity CLI or Click?

Antigravity CLI scores 56.6 (C) on agent readiness against Click's 48.6 (D), and leads in 5 of 7 scored categories. Click leads on schema & documentation.

Can an agent call Antigravity CLI and Click without installing anything?

No hosted endpoint is listed for Antigravity CLI. Click has a hosted endpoint at https://api.useclick.ai/v1.

Other comparisons with Antigravity CLI or Click

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.