Antigravity CLI vs Clawboo

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, at $20 a month for Google AI Pro, $100 and $200 for Ultra and $30 a seat for Enterprise Standard. Consumption is priced at Gemini Enterprise rates, and those rates were not read, so this is plan-level pricing (10). The pricing page lists a $0 individual plan that needs no subscription. None of the pages read asks for a payment method, but the account flow was not tested, so the point is taken from the page (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).

Clawboo 60

No payment protocol (0). Read with the self-hosted rule. Free under MIT with nothing to buy (20). No card and no Clawboo account (20). One npx command installs and starts it with no sign-up (20). Model costs belong to the providers the owner connects.

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. Interactions are collected until the user opts out, and the settings page does not state the default (10). The Default preset sandboxes terminal commands on macOS and Linux, hides ~/.ssh and .env, limits network access to approved domains and asks before MCP tools run, with allow rules by server and tool. The sandbox is labelled preview, the Turbo preset turns it off, and Windows uses the older model (18). Hooks run before and after tool calls and can block one, and the CLI shows a Reason line when a hook flags an action. 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, antigravity.google serves none, and no CLI advisory appears in the changelog. The advisory page was not reachable, so that part is unchecked (8).

Clawboo 70

Harness reading of the framework checklist, as for the other harnesses. 30 for what leaves the machine by default, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. The docs say Clawboo sends no telemetry and list the GitHub catalogue fetch, the npm version check, OpenRouter's public model list, Google Fonts and the GitHub star count, of which only the catalogue address can be changed (27). Clawboo Native shell commands are off by default and asked one at a time, and connector grants are per agent with approval on writes. Claude Code, Codex and Hermes run with their prompts and sandboxes off and no setting to change it, they can read Clawboo's database and key vault, and with no access token by default any local program can answer approval cards (8). Images in agent text don't load on their own, peer posts are marked as evidence, and a run that has read private data and untrusted content asks before any outbound connector call (11). An audit log of budget, breaker, approval, verification, tool-call and install events, with secrets masked (13). SECURITY.md with private reporting, CodeQL, Dependabot and npm provenance. No security.txt or bug bounty, OSV lists no advisory for clawboo, and the proxy advisory is on the docs with a workaround while its fix is unreleased (11).

Antigravity CLI 68

1.3.2 on 8 October 2026 (30). 47 numbered releases in the changelog from 1.1.2 (13 July) to 1.3.2 (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, version 0.1.21 released on 7 October 2026 under Apache-2.0, is a separate package and no SDK for the CLI itself was found (10). No public CI or dependency list for the CLI, since the source is not published (0).

Clawboo 51

0.5.0 was published to npm on 21 October 2026 (30). Two releases in the 90 days to 1 November 2026, 0.4.0 on 28 September and 0.5.0, below the three the line asks for (0). github.com was unreachable, so replies to issues, pull requests and Discussions are unchecked. The CI file cites issue #140 as fixed (3). One public npm package, current, with no entry in the official MCP registry for its four servers (10). CI, CodeQL, weekly Dependabot and SLSA provenance on 0.4.0 and 0.5.0, with @composio/client pinned to an alpha (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 against Google's release manifest before it installs (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 from this session, so the crash and regression line is unchecked (0). Version 1.3.2 is the latest, and version 1.2.10 changed headless exit codes for streamed model errors from 0 to 3 under a Fixed heading, with no breaking-change heading (8). Version 1.x, so stable under the rule (15).

Clawboo 52

Read as local software. The official npm package clawboo states Node.js 22.12 or newer, and the README says macOS, Linux and Windows are supported (20). ci.yml runs lint, typecheck, Vitest and a real-concurrency suite on Linux and platform suites on Windows and macOS, and publish.yml reruns build, lint, typecheck, tests and a clean-install boot before it publishes. 0.5.0 carries provenance from that workflow on main, so its checks passed at that commit, but run results on main couldn't be read (15). github.com was unreachable, so open crash and regression issues are unchecked. A known-issues page lists 25 entries with a status each, three of them fixed on main (5). Changesets write a changelog entry per release, and removals and the 0.2.0 database reset are called out, though breaking changes arrive in minor versions before 1.0 (12). Version 0.5.0, and SECURITY.md says pre-1.0 (0).

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, what each allows and when the sandbox applies (15). Presets, output formats, modes 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 in the repository (15).

Clawboo 83

Harness reading of the framework line, as for Paperclip. The REST API's 199 routes are documented per resource with parameters, bodies and responses, and the MCP tools reference gives typed arguments for every tool on the four servers, but no OpenAPI file was found (17). llms.txt, llms-full.txt and a Markdown copy of every page at .md on docs.claw.boo (10). The docs say what each part does and does not cover, with known issues, production defaults and a limits page that names the code line behind each number (17). Tool arguments are typed with required and optional fields and documented caps, such as 24 live subtasks per parent and limits lowered to 1,000, with free-text task bodies (12). curl examples on each API page, an events and errors reference, and the exact error strings each MCP tool returns (14). A dated changelog for every release with an Unreleased section, though API paths carry no version and every MCP server reports 0.1.0 (13).

Antigravity CLI 53

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 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 with that, 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 on 2 November 2026, but there is no written deprecation policy for the CLI (10). Enable Telemetry in the Account settings controls sharing of Interactions and can be turned off. The settings page describes the same key as anonymous usage statistics and crash reports, and its default is not stated (12).

Clawboo 58

MIT, Copyright 2026 Sanreds, with a third-party notices file (30). The docs list every file Clawboo writes, which copies of keys are encrypted and which are plain text, retention for stored tool results (7 days) and pending approvals (24 hours), and that prompts go only to connected providers. There is no privacy statement, and the website wasn't read (22). The 0.1.x line is deprecated on npm with a note in the changelog, and removals are dated in release notes, with no written deprecation policy or notice period (10). No telemetry, with the server's own outbound requests disclosed, though the npm update check has no setting (18).