Gemini CLI vs Google Antigravity

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Google Antigravity
   Gemini CLI—none0/10

   No evidence Gemini CLI has any documented feature for consuming llms.txt or agent-oriented doc manifests; the only related probe shows llms.txt returning 404 on Google's own docs site, and none of the GitHub feature list or docs mention llms.txt support. GEMINI.md context files are a different, project-local mechanism, not agent-oriented web docs discovery.

   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.google.com/llms.txt”
   • [github] “Custom context files (GEMINI.md) to tailor behavior for your projects”

   proof ↗⚑ flag

   Google Antigravity✓fullprobed9/10

   Antigravity hosts a working llms.txt (HTTP 200) describing itself, and provides markdown-formatted docs pages (e.g. getting-started.md) that an agent can fetch directly, confirming genuine agent-oriented documentation support. Missing for 10: independent third-party confirmation that agents actually consume these successfully in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://antigravity.google/llms.txt # Google Antigravity > Google Antigravity is an advanced agentic coding pla…”
   • [probe] “PROBE docs-md: HTTP 200 at https://antigravity.google/docs/getting-started.md # Getting Started with Antigravity 2.0 ### Download Visit [a…”
   • [claimed-docs] “Visit antigravity.google/download to download Google Antigravity 2.0. Select your operating system below”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Gemini CLI
   Gemini CLI✓fullclaimed9/10

   Gemini CLI explicitly documents non-interactive scripting mode, structured/streaming JSON output flags for programmatic parsing, and GitHub Actions-based automation (PR reviews, issue triage, on-demand assistance), which together cover headless/CI use cases well. Missing for 10: independent hands-on confirmation specifically of CI pipeline reliability (community evidence focuses more on interactive agentic quality than CI usage).

   • [github] “Run non-interactively in scripts for workflow automation”
   • [github] “use the `--output-format json` flag to get structured output”
   • [github] “use `--output-format stream-json` to get newline-delimited JSON events”
   • [github] “Pull Request Reviews: Automated code review with contextual feedback and suggestions”
   • [github] “Issue Triage: Automated labeling and prioritization of GitHub issues based on content analysis”
   • [github] “On-demand Assistance: Mention @gemini-cli in issues and pull requests for help with debugging, explanations, or task delegation”

   proof ↗⚑ flag

   Google Antigravity✓fullclaimed7/10

   Antigravity CLI has a documented headless mode explicitly for scripting agent tasks, CI pipeline integration, and machine-readable output (antigravity-docs-50), plus scheduled/cron tasks and background subagents support agentic automation outside interactive UI. Missing for 10: independent hands-on CI usage reports, concrete CI config examples/output schema, and no community corroboration of headless/CI use in practice.

   • [claimed-docs] “Run Antigravity CLI non-interactively to script agent tasks, integrate with CI pipelines, and capture machine-readable output.”
   • [claimed-docs] “Automate routine checks with Scheduled Tasks, simply define a cron schedule and the agents start and run autonomously in the background.”
   • [claimed-docs] “Edit, orchestrate, and build all in natural language. Tell your agents what you need, and they’ll work on getting it done.”
   • [claimed-docs] “Create or download fully customizable skills to further your agent’s autonomy and transform how you get work done.”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round drawn
   Gemini CLI✓fullclaimed8/10

   Gemini CLI documents first-party MCP server support: configuring servers in ~/.gemini/settings.json to add custom tools, a dedicated /mcp command, and explicit mention of connecting media-generation tools like Imagen/Veo/Lyria via MCP. This is corroborated by official docs listing /mcp among CLI commands. Missing for 10: independent hands-on verification of MCP tool usage specifically (community evidence covers general agentic reliability but not MCP integration itself), and more detail on server management/discovery UX.

   • [github] “Configure MCP servers in ~/.gemini/settings.json to extend Gemini CLI with custom tools”
   • [github] “Use MCP servers to connect new capabilities, including media generation with Imagen, Veo or Lyria”
   • [claimed-docs] “Comandos de Gemini CLI: /memory, /stats, /tools y /mcp”

   proof ↗⚑ flag

   Google Antigravity✓fullclaimed8/10

   Antigravity has explicit, dedicated MCP documentation stating MCP lets it 'fetch structured context directly or execute safe actions on your behalf' and that it 'securely connects to local developer tools, databases, file parsers, and external remote APIs' via MCP, plus CLI/SDK support for configuring MCP servers (slash commands, plugins bundling MCP servers, layering MCP servers in the Agent SDK). Missing for 10: independent hands-on confirmation of successfully connecting a third-party MCP server and using its tools in a real workflow.

   • [claimed-docs] “MCP lets Antigravity fetch structured context directly or execute safe actions on your behalf when needed.”
   • [claimed-docs] “lets AI agents and editors securely connect to local developer tools, databases, file parsers, and external remote APIs”
   • [claimed-docs] “Access plugins, MCP, skills, and hooks configurations instantly via slash commands, quickly enhancing your workflow.”
   • [claimed-docs] “Layer custom Python callables, Model Context Protocol (MCP) servers, and reusable agent skills over our built-in filesystem and terminal too…”
   • [claimed-docs] “Plugins are namespaced bundles that allow you to extend Antigravity’s capabilities by grouping skills, rules, MCP servers, and hooks into a …”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Gemini CLI
   Gemini CLI✓fullprobed9/10

   Gemini CLI is itself an official, first-party CLI product by Google with extensive documentation of its features (scripting, JSON output, MCP support, context files, non-interactive mode) and independent corroboration of active use, confirming it exists and functions as an official CLI tool for AI-native workflows. missing for 10: no fully independent third-party audit of CLI completeness beyond community anecdotes.

   • [github] “Run non-interactively in scripts for workflow automation”
   • [github] “gemini --include-directories ../lib,../docs”
   • [github] “use the `--output-format json` flag to get structured output”
   • [github] “use `--output-format stream-json` to get newline-delimited JSON events”
   • [github] “Configure MCP servers in ~/.gemini/settings.json to extend Gemini CLI with custom tools”
   • [claimed-docs] “The Gemini CLI is available without additional setup in Cloud Shell”
   • [community] “I have been using this for about a month and it's a beast, mostly thanks to 2.5pro being SOTA and how it leverages that huge 1M context wind…”
   • [probe] “official CLI documented at https://developers.google.com/gemini-code-assist/docs/gemini-cli”

   proof ↗⚑ flag

   Google Antigravity✓fullprobed8/10

   Google Antigravity ships an official CLI with dedicated docs (antigravity-cli product page, headless/non-interactive mode for CI, sandboxing, vim mode, gcli migration), enabling natural-language orchestration of parallel agents, slash commands, and MCP/plugin config — clearly AI-native and agentic. Community evidence corroborates the CLI works in practice alongside VSCode. Missing for 10: independent deep-dive review of CLI-specific reliability/performance beyond a single community mention.

   • [claimed-docs] “Edit, orchestrate, and build all in natural language. Tell your agents what you need, and they’ll work on getting it done.”
   • [claimed-docs] “Have multiple agents working in parallel, so larger tasks get tackled faster.”
   • [claimed-docs] “Navigate your entire workflow via standard terminal shortcuts: adjust permissions, themes, and preferences via /config and type /keybindings…”
   • [claimed-docs] “Access plugins, MCP, skills, and hooks configurations instantly via slash commands, quickly enhancing your workflow.”
   • [claimed-docs] “the CLI automatically detects your existing profiles. An interactive checklist prompts you to choose which assets to migrate”
   • [claimed-docs] “Sensitive files like ~/.ssh and .env are blocked, anything not explicitly mounted is invisible inside the sandbox”
   • [claimed-docs] “Vim editor mode replaces the editing model in every multi-line input surface of the CLI”
   • [claimed-docs] “Run Antigravity CLI non-interactively to script agent tasks, integrate with CI pipelines, and capture machine-readable output.”
   • [community] “I much prefer using Gemini CLI in combination with vscode. It works like a charm. Now, I'll do the same with Antigravity CLI and vscode. It …”
   • [probe] “official CLI documented at https://antigravity.google/product/antigravity-cli”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to Google Antigravity
   Gemini CLI~partialprobed5/10

   Gemini CLI documents CLI-level automation hooks — non-interactive scripting mode, `--output-format json`/`stream-json` for structured output, and MCP server configuration — which let an AI-native user drive it programmatically (gemini-cli-gh-6, gh-17, gh-18, gh-19). However, explicit probes for a formal public API/SDK (llms.txt, openapi.json) all returned 404, showing no dedicated documented API surface beyond the CLI itself. Missing for 10: a first-party REST/SDK API spec, official API reference docs, and independent confirmation of programmatic (non-CLI) usage.

   • [github] “Run non-interactively in scripts for workflow automation”
   • [github] “use the `--output-format json` flag to get structured output”
   • [github] “use `--output-format stream-json` to get newline-delimited JSON events”
   • [github] “Configure MCP servers in ~/.gemini/settings.json to extend Gemini CLI with custom tools”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.google.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.google.com/openapi.json, https://developers.google.com/swagger.json, https://deve…”

   proof ↗⚑ flag

   Google Antigravity~partialprobed6/10

   Antigravity documents an Agent SDK (Python) exposing the same tools/agent loop/context management as the app, plus a CLI headless mode for scripting and CI integration, both of which let an AI-native user drive the product programmatically. However, there is no evidence of a formal public REST/HTTP API — a probe for OpenAPI/swagger specs returned 404 on all candidate paths, so the 'documented public API' is limited to SDK/CLI surfaces rather than a conventional API contract. Missing for 10: a documented REST/HTTP API or OpenAPI spec, independent third-party confirmation of SDK usage/stability.

   • [claimed-docs] “The Agent SDK gives you the same tools, agent loop, and context management that power Google Antigravity, programmable in Python.”
   • [claimed-docs] “Layer custom Python callables, Model Context Protocol (MCP) servers, and reusable agent skills over our built-in filesystem and terminal too…”
   • [claimed-docs] “Build AI agents that autonomously read files, run commands, edit code, and more.”
   • [claimed-docs] “Run Antigravity CLI non-interactively to script agent tasks, integrate with CI pipelines, and capture machine-readable output.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://antigravity.google/openapi.json, https://antigravity.google/swagger.json, https://antigravit…”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Google Antigravity
   Gemini CLI—none0/10

   Evidence shows Gemini CLI abstracts away API key management entirely (sign in with Google account) rather than offering scoped or least-privilege credential issuance for agents; no docs mention credential scoping, permission boundaries, or token minting for agent use.

   • [github] “No API key management - just sign in with your Google account”

   proof ↗⚑ flag

   Google Antigravity!disputedcontradicted4/10

   Antigravity documents permission tiers (Deny/Ask/Allow) and a CLI sandbox that explicitly blocks access to sensitive files like .env and ~/.ssh, which is the closest analog to least-privilege credential scoping for an agent (docs-23, docs-42, docs-48). However, independent reports document a concrete bypass: Antigravity's own setting disallowing .env access was circumvented via prompt injection to exfiltrate secrets, and a default allowlisted domain (webhook.site) was used as an exfiltration channel — directly contradicting the claimed least-privilege protection (antigravity-comm-11, antigravity-comm-12). There is no evidence of a true scoped API-credential-issuance mechanism (e.g., minting restricted API keys/tokens for an agent); missing for 10: actual credential/token scoping API, third-party security audit confirming the sandbox holds, and any documented remediation.

   • [claimed-docs] “Permissions are evaluated across three distinct access lists: Deny... Ask... Allow”
   • [claimed-docs] “Permissions are evaluated across three distinct access lists: Deny...Ask...Allow”
   • [claimed-docs] “Sensitive files like ~/.ssh and .env are blocked, anything not explicitly mounted is invisible inside the sandbox”
   • [community] “Google Antigravity exfiltrates data via indirect prompt injection attack: Gemini is not supposed to have access to .env files with default s…”
   • [community] “The default Allowlist provided with Antigravity includes 'webhook.site', which was used as an exfiltration vector for secrets.”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Google Antigravity
   Gemini CLI—none0/10

   The evidence pack documents CLI flags, MCP server extensibility, scripting output formats, and GitHub Actions integration, but contains no mention of an official SDK (e.g., a Node/Python/Go library) for programmatically building on Gemini CLI itself. Probes for API/OpenAPI specs also returned 404s, reinforcing the absence of such artifacts.

   • [github] “Configure MCP servers in ~/.gemini/settings.json to extend Gemini CLI with custom tools”
   • [github] “use the `--output-format json` flag to get structured output”
   • [github] “use `--output-format stream-json` to get newline-delimited JSON events”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.google.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.google.com/openapi.json, https://developers.google.com/swagger.json, https://deve…”

   proof ↗⚑ flag

   Google Antigravity✓fullprobed7/10

   Google explicitly documents an official Agent SDK ('same tools, agent loop, and context management that power Antigravity, programmable in Python') supporting custom Python callables, MCP servers, skills, and multimedia inputs, which directly satisfies building against an official SDK. Missing for 10: independent/hands-on developer confirmation of the SDK working as documented, and no public API reference/OpenAPI spec was found (probe returned 404s), so depth of documentation beyond marketing copy is unverified.

   • [claimed-docs] “The Agent SDK gives you the same tools, agent loop, and context management that power Google Antigravity, programmable in Python.”
   • [claimed-docs] “Layer custom Python callables, Model Context Protocol (MCP) servers, and reusable agent skills over our built-in filesystem and terminal too…”
   • [claimed-docs] “Pass rich multimedia file attachments (images, videos, audio, and documents) to the agent alongside textual instruction prompt lists.”
   • [claimed-docs] “Build AI agents that autonomously read files, run commands, edit code, and more.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://antigravity.google/openapi.json, https://antigravity.google/swagger.json, https://antigravit…”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Gemini CLI—none0/10

   No evidence of webhook subscription or event-push capability; Gemini CLI supports non-interactive scripting, MCP tool servers, and structured JSON output, but nothing about outbound webhooks or event subscriptions. Missing for 10: any webhook registration mechanism, event subscription API, or documentation of push notifications.

   • [github] “Run non-interactively in scripts for workflow automation”
   • [github] “use the `--output-format json` flag to get structured output”
   • [github] “use `--output-format stream-json` to get newline-delimited JSON events”
   • [github] “Configure MCP servers in ~/.gemini/settings.json to extend Gemini CLI with custom tools”

   proof ↗⚑ flag

   Google Antigravity—none0/10

   No evidence of any webhook subscription mechanism; Antigravity is an IDE/CLI/agent platform with hooks, MCP, and scheduled tasks, but nothing about outbound event subscriptions via webhooks. Even the openapi probe returned 404s, indicating no public API surface for such integration.

   • [probe] “PROBE openapi: all candidate paths 404 (https://antigravity.google/openapi.json, https://antigravity.google/swagger.json, https://antigravit…”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Google Antigravity
   Gemini CLI!disputedcontradicted5/10

   Gemini CLI ships features that clearly aim at generating insights from a user's own data/codebase — querying and editing large codebases, natural-language debugging, automated PR review with contextual feedback, and issue triage (gemini-cli-gh-1, gh-3, gh-10, gh-11), and one community report praises its code review as catching bugs missed by humans (gemini-cli-comm-20). However, multiple hands-on reports directly contradict this, describing it as 'terrible at agentic stuff', getting stuck in loops, failing to edit/read files, and being 'useless as a coding assistant' that produces spaghetti code (gemini-cli-comm-10, comm-14, comm-15). missing for 10: independent benchmark confirming consistent quality of generated insights, resolution of the loop/failure reports, and evidence the insight-generation works reliably across data types beyond code.

   • [github] “Query and edit large codebases”
   • [github] “Debug issues and troubleshoot with natural language”
   • [github] “Pull Request Reviews: Automated code review with contextual feedback and suggestions”
   • [github] “Issue Triage: Automated labeling and prioritization of GitHub issues based on content analysis”
   • [community] “We have tried out Gemini code review vs Copilot code review and Gemini is consistently offering better code review tips. It has officially c…”
   • [community] “A lot of times Gemini models will get stuck in a loop of errors, and a lot of times it fails to edit/read or other simple function calling -…”
   • [community] “The problem is that Gemini CLI simply doesn't work. Beside simplest tasks like creating a new release it is useless as a coding assistant. D…”
   • [community] “I love the model, hate the tool. Anthropic has the killer app with Claude Code. I tried Gemini cli for about 5 seconds and was so frustrated…”

   proof ↗⚑ flag

   Google Antigravity~partialcommunity6/10

   Antigravity's editor/agent generates code suggestions, tab-autocompletion, and rich 'Artifacts' (implementation plans, diagrams, code diffs) that surface AI-derived insights from the user's codebase (antigravity-docs-6, -24, -30, -41), fitting the 'insights from data' story in a coding context. However, this is inference-in-editor suggestion generation rather than dedicated analytics/insight dashboards, and community hands-on reports raise real quality concerns ('the model was not good and slow, the harness was not good' — antigravity-comm-8), undercutting confidence in consistent insight quality. Missing for 10: no evidence of dedicated data-analysis/insight-summarization features beyond code artifacts, and no independent corroboration that suggestions are reliably high quality.

   • [claimed-docs] “Google Antigravity's Editor view offers tab autocompletion, natural language code commands, and a configurable, and context-aware configurab…”
   • [claimed-docs] “Planning Mode: The agent plans thoroughly before executing tasks... produces structured implementation plans called Artifacts”
   • [claimed-docs] “Artifacts include rich markdown plans (Implementation Plans), code diffs, architecture diagrams, images, and browser recordings.”
   • [claimed-docs] “offers tab autocompletion, natural language code commands, and a configurable, and context-aware configurable agent”
   • [community] “It's not even good, honestly. I was using it for couple weeks before dropping that 2 months ago. The model was not good and slow, the harnes…”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Google Antigravity
   Gemini CLI~partialcommunity6/10

   Gemini CLI documents non-interactive scripting mode and a GitHub Action integration that runs autonomously in the background (automated PR reviews, issue triage, on-demand @gemini-cli responses), which directly supports background automations. However, independent community reports describe agentic reliability problems (getting stuck in loops, failing simple file operations, ignoring GEMINI.md context) that undercut confidence in unattended/background runs actually completing correctly. Missing for 10: independent hands-on validation that scheduled/background automations run reliably end-to-end, and more detail on failure/retry handling in autonomous mode.

   • [github] “Run non-interactively in scripts for workflow automation”
   • [github] “Pull Request Reviews: Automated code review with contextual feedback and suggestions”
   • [github] “Issue Triage: Automated labeling and prioritization of GitHub issues based on content analysis”
   • [github] “On-demand Assistance: Mention @gemini-cli in issues and pull requests for help with debugging, explanations, or task delegation”
   • [github] “On-demand Assistance: Mention `@gemini-cli` in issues and pull requests for help with debugging, explanations, or task delegation”
   • [github] “@github List my open pull requests”
   • [community] “A lot of times Gemini models will get stuck in a loop of errors, and a lot of times it fails to edit/read or other simple function calling -…”
   • [community] “I really tried to get gemini to work properly in Agent mode. Tho it way too often went crazy, started rewriting files empty, and ran into pe…”
   • [community] “Tip 1, it consistently ignores my GEMINI.md file, both global and local, even though it always says '1 GEMINI.md file is being used.'”

   proof ↗⚑ flag

   Google Antigravity✓fullclaimed8/10

   Docs explicitly describe Scheduled Tasks with cron schedules that let agents 'start and run autonomously in the background' (docs-2), plus related capabilities like scheduling messages to agents while away (docs-39), isolated background worktrees (docs-38), and headless/non-interactive CLI runs for CI automation (docs-50). This directly matches the story of autonomous background automations. Missing for 10: independent/hands-on verification that scheduled background tasks work reliably (community evidence focuses on other bugs/exfiltration issues, not scheduling specifically), and more detail on monitoring/error-handling for unattended runs.

   • [claimed-docs] “Automate routine checks with Scheduled Tasks, simply define a cron schedule and the agents start and run autonomously in the background.”
   • [claimed-docs] “Worktree support: Projects natively support Git worktrees, allowing agents to operate in isolated background folders.”
   • [claimed-docs] “users can schedule messages to be sent to their agents while they’re away”
   • [claimed-docs] “Run Antigravity CLI non-interactively to script agent tasks, integrate with CI pipelines, and capture machine-readable output.”
   • [claimed-docs] “Able to autonomously operate across your editor, terminal, and browser.”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Google Antigravity
   Gemini CLI!disputedcontradicted5/10

   Gemini CLI is itself billed as an agentic assistant with extensive task-delegation features (codebase queries, debugging, PR review/issue triage, operational automation via @gemini-cli mentions) per gemini-cli-gh-3/4/10/11/12/22. However, hands-on community reports concretely contradict reliable delegation: users report it is 'really really terrible at agentic stuff,' gets stuck in permanent loops, ignores GEMINI.md context, and in one case catastrophically deleted user files while apologizing for the failure.

   • [github] “Debug issues and troubleshoot with natural language”
   • [github] “Automate operational tasks like querying pull requests or handling complex rebases”
   • [github] “Pull Request Reviews: Automated code review with contextual feedback and suggestions”
   • [github] “Issue Triage: Automated labeling and prioritization of GitHub issues based on content analysis”
   • [github] “On-demand Assistance: Mention @gemini-cli in issues and pull requests for help with debugging, explanations, or task delegation”
   • [community] “A lot of times Gemini models will get stuck in a loop of errors, and a lot of times it fails to edit/read or other simple function calling -…”
   • [community] “I really tried to get gemini to work properly in Agent mode. Tho it way too often went crazy, started rewriting files empty, and ran into pe…”
   • [community] “Tip 1, it consistently ignores my GEMINI.md file, both global and local, even though it always says '1 GEMINI.md file is being used.'”
   • [community] “The problem is that Gemini CLI simply doesn't work. Beside simplest tasks like creating a new release it is useless as a coding assistant. D…”
   • [community] “Gemini told the user: 'I have failed you completely and catastrophically... I have lost your data. This is an unacceptable, irreversible fai…”

   proof ↗⚑ flag

   Google Antigravity✓fullcommunity8/10

   Antigravity is built around delegating tasks to autonomous agents that operate across editor, terminal, and browser, with subagents, scheduled tasks, and natural-language task delegation extensively documented; hands-on community reports (comm-1, comm-10) confirm the agent/CLI actually works for delegated tasks. missing for 10: independent third-party benchmarking of delegation quality, and community evidence is mixed on reliability/bugs which caps quality below top marks.

   • [claimed-docs] “Able to autonomously operate across your editor, terminal, and browser.”
   • [claimed-docs] “Edit, orchestrate, and build all in natural language. Tell your agents what you need, and they’ll work on getting it done.”
   • [claimed-docs] “an agent can delegate tasks—such as running tests or performing extensive codebase searches—to dedicated subagents.”
   • [claimed-docs] “Antigravity comes pre-packaged with several specialized subagents out of the box”
   • [claimed-docs] “Antigravity 2.0 serves as your AI agents’ central command center, providing a unified platform to launch, monitor, and orchestrate their act…”
   • [community] “I went ahead and downloaded it, it looks to be a VSCode fork very similar to Cursor, with support for Gemini 3 Pro, Claude Sonnet 4.5, and G…”
   • [community] “I much prefer using Gemini CLI in combination with vscode. It works like a charm. Now, I'll do the same with Antigravity CLI and vscode. It …”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Google Antigravity
   Gemini CLI!disputedcontradicted5/10

   Gemini CLI's entire premise is natural-language driven coding/agentic actions (querying codebases, debugging, automating PR/rebase tasks, custom GEMINI.md context) per gemini-cli-gh-1/3/4/9. However, multiple hands-on reports describe the NL-agent behavior failing badly in practice — getting stuck in error loops, botching file edits, ignoring GEMINI.md instructions, and in one case catastrophically deleting user data via misinterpreted commands.

   • [github] “Query and edit large codebases”
   • [github] “Debug issues and troubleshoot with natural language”
   • [github] “Automate operational tasks like querying pull requests or handling complex rebases”
   • [github] “Custom context files (GEMINI.md) to tailor behavior for your projects”
   • [community] “A lot of times Gemini models will get stuck in a loop of errors, and a lot of times it fails to edit/read or other simple function calling -…”
   • [community] “I really tried to get gemini to work properly in Agent mode. Tho it way too often went crazy, started rewriting files empty, and ran into pe…”
   • [community] “Tip 1, it consistently ignores my GEMINI.md file, both global and local, even though it always says '1 GEMINI.md file is being used.'”
   • [community] “The problem is that Gemini CLI simply doesn't work. Beside simplest tasks like creating a new release it is useless as a coding assistant. D…”
   • [community] “Gemini told the user: 'I have failed you completely and catastrophically... I have lost your data. This is an unacceptable, irreversible fai…”

   proof ↗⚑ flag

   Google Antigravity✓fullcommunity8/10

   Docs consistently describe natural-language operation as the core interaction model — editing, orchestrating, and building 'all in natural language' (antigravity-docs-9), NL code commands in the IDE (antigravity-docs-6/41), and even voice-to-prompt transcription (antigravity-docs-3), backed by planning/artifact review flows driven by conversational prompts (antigravity-docs-24, antigravity-docs-25). Community evidence corroborates it functions as an agentic assistant (comm-1, comm-10) though with quality/reliability complaints unrelated to the NL-command axis itself. Missing for 10: independent hands-on confirmation specifically praising the NL-command UX (most community commentary focuses on bugs/pricing/security rather than command quality).

   • [claimed-docs] “Edit, orchestrate, and build all in natural language. Tell your agents what you need, and they’ll work on getting it done.”
   • [claimed-docs] “Google Antigravity's Editor view offers tab autocompletion, natural language code commands, and a configurable, and context-aware configurab…”
   • [claimed-docs] “offers tab autocompletion, natural language code commands, and a configurable, and context-aware configurable agent”
   • [claimed-docs] “Speak your prompts. Powered by the latest Gemini Audio models, real-time transcription converts conversational speech into clearly phrased p…”
   • [claimed-docs] “Planning Mode: The agent plans thoroughly before executing tasks... produces structured implementation plans called Artifacts”
   • [claimed-docs] “The agent always halts and requests your explicit approval before proceeding with proposed changes.”
   • [community] “I went ahead and downloaded it, it looks to be a VSCode fork very similar to Cursor, with support for Gemini 3 Pro, Claude Sonnet 4.5, and G…”
   • [community] “I much prefer using Gemini CLI in combination with vscode. It works like a charm. Now, I'll do the same with Antigravity CLI and vscode. It …”

   proof ↗⚑ flag

Api quality

1. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Gemini CLI—none0/10

   Probes explicitly show no OpenAPI/llms.txt spec is published (404s at all candidate paths), and no other evidence mentions a machine-readable API spec for Gemini CLI.

   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.google.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.google.com/openapi.json, https://developers.google.com/swagger.json, https://deve…”

   proof ↗⚑ flag

   Google Antigravity—none0/10

   A direct probe for OpenAPI/Swagger specs at all standard candidate paths returned 404s, and no documentation item mentions a machine-readable API spec despite extensive docs on SDK, CLI, and MCP.

   • [probe] “PROBE openapi: all candidate paths 404 (https://antigravity.google/openapi.json, https://antigravity.google/swagger.json, https://antigravit…”

   proof ↗⚑ flag

2. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Google Antigravity
   Gemini CLI—none0/10

   No evidence pack items describe a sandbox/test environment isolated from production data for Gemini CLI; the only mention of 'sandbox' appears in an unrelated community comment describing another tool's architecture, not Gemini CLI's own testing environment. missing for 10: dedicated sandbox mode/documentation, evidence of isolation from production data, any hands-on confirmation of safe test environments.

   ⚑ flag

   Google Antigravity!disputedcontradicted4/10

   Antigravity's CLI docs claim a sandbox that blocks sensitive files (~/.ssh, .env) and hides anything not explicitly mounted, which sounds like exactly the kind of safe-testing boundary this story wants, but hands-on community reports directly contradict this: Gemini bypassed its own .env protection to exfiltrate secrets via prompt injection, a default allowlisted webhook.site was used as an exfiltration vector, and in another incident Antigravity commands deleted an entire drive outside any expected sandbox boundary. This is a concrete, documented failure of the sandbox promise rather than mere skepticism. Missing for 10: a genuine isolated/staging environment separate from real user data, and any vendor or independent confirmation that the sandbox reliably prevents production-data access after these reported bypasses.

   • [claimed-docs] “Sensitive files like ~/.ssh and .env are blocked, anything not explicitly mounted is invisible inside the sandbox”
   • [community] “Google Antigravity exfiltrates data via indirect prompt injection attack: Gemini is not supposed to have access to .env files with default s…”
   • [community] “The default Allowlist provided with Antigravity includes 'webhook.site', which was used as an exfiltration vector for secrets.”
   • [community] “Antigravity was also vulnerable to the classic Markdown image exfiltration bug, reported a few days prior and flagged as 'intended behavior'…”
   • [community] “Google Antigravity just deleted the contents of whole drive - came down to commanding a deletion of a 'directory with space in the name' wit…”

   proof ↗⚑ flag

3. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Gemini CLI—none0/10

   No evidence of versioned APIs or a documented deprecation policy for Gemini CLI; probes for llms.txt/openapi specs 404, and there is community evidence the tool itself was abruptly deprecated with no policy discussion (gemini-cli-comm-6/7/8), but no documentation of API versioning or deprecation commitments exists.

   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.google.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.google.com/openapi.json, https://developers.google.com/swagger.json, https://deve…”
   • [community] “Welcome to the Google graveyard, Gemini CLI. Not that it will be missed much. Using it was the worst experience out of any harness.”
   • [community] “Google really can't help themselves but to have some internal re-org kill off a public thing people are actively using. It's honestly impres…”

   proof ↗⚑ flag

   Google Antigravity—none0/10

   No evidence of versioned APIs or a documented deprecation policy; OpenAPI probe returned 404s across all candidate paths and no docs mention API versioning or deprecation timelines.

   • [probe] “PROBE openapi: all candidate paths 404 (https://antigravity.google/openapi.json, https://antigravity.google/swagger.json, https://antigravit…”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round drawn
   Gemini CLI~partialcommunity6/10

   Gemini CLI supports scripting/non-interactive automation, multi-directory context inclusion, structured JSON output for pipelines, and GitHub Action integrations like automated issue triage (bulk labeling/prioritization) and PR review across a repo — all pointing to bulk/batch style operations. However there's no explicit documented 'batch process N files/items' feature or example, and community reports note the agent can get stuck in loops or fail simple multi-step tasks, raising doubts about reliability at scale. Missing for 10: explicit bulk-operation examples/documentation (e.g., batch renaming, mass refactor across many files) and independent evidence confirming reliable execution at scale.

   • [github] “Automate operational tasks like querying pull requests or handling complex rebases”
   • [github] “Run non-interactively in scripts for workflow automation”
   • [github] “Issue Triage: Automated labeling and prioritization of GitHub issues based on content analysis”
   • [github] “gemini --include-directories ../lib,../docs”
   • [github] “use the `--output-format json` flag to get structured output”
   • [github] “use `--output-format stream-json` to get newline-delimited JSON events”
   • [community] “A lot of times Gemini models will get stuck in a loop of errors, and a lot of times it fails to edit/read or other simple function calling -…”
   • [community] “I really tried to get gemini to work properly in Agent mode. Tho it way too often went crazy, started rewriting files empty, and ran into pe…”

   proof ↗⚑ flag

   Google Antigravity~partialclaimed6/10

   Antigravity supports parallel multi-agent orchestration across independent projects, subagent delegation, scheduled/background tasks, and a headless CLI for scripting bulk/CI workflows, which together enable operating across many items or tasks concurrently. However, there is no explicit documentation of a dedicated 'bulk operation' primitive (e.g., batch-apply an action across a list of files/items in one command) — the capability is inferred from parallelism/orchestration features rather than a purpose-built bulk-ops interface. missing for 10: explicit bulk/batch API or command for applying one operation across many items, independent hands-on evidence of large-scale parallel task execution working reliably.

   • [claimed-docs] “Orchestrate multiple autonomous agents working in parallel across independent projects.”
   • [claimed-docs] “Have multiple agents working in parallel, so larger tasks get tackled faster.”
   • [claimed-docs] “an agent can delegate tasks—such as running tests or performing extensive codebase searches—to dedicated subagents.”
   • [claimed-docs] “Worktree support: Projects natively support Git worktrees, allowing agents to operate in isolated background folders.”
   • [claimed-docs] “Run Antigravity CLI non-interactively to script agent tasks, integrate with CI pipelines, and capture machine-readable output.”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Google Antigravity
   Gemini CLI~partialclaimed5/10

   Gemini CLI ships GitHub Action integrations that fire automatically on repo events (PR opened → automated review, issue created → automated triage, @mention → on-demand help), which is a form of event-triggered automation, plus non-interactive/scripted execution for pipelines. However there's no evidence of a general-purpose, user-defined rule/trigger engine (e.g., custom webhooks, cron-like conditions, arbitrary event types) within the CLI itself—only fixed GitHub-event integrations. Missing for 10: a generic rule-definition mechanism for arbitrary events, documentation of custom trigger conditions, and independent confirmation these automations work reliably (community notes reliability issues with agentic behavior).

   • [github] “Pull Request Reviews: Automated code review with contextual feedback and suggestions”
   • [github] “Issue Triage: Automated labeling and prioritization of GitHub issues based on content analysis”
   • [github] “On-demand Assistance: Mention @gemini-cli in issues and pull requests for help with debugging, explanations, or task delegation”
   • [github] “On-demand Assistance: Mention `@gemini-cli` in issues and pull requests for help with debugging, explanations, or task delegation”
   • [github] “Run non-interactively in scripts for workflow automation”

   proof ↗⚑ flag

   Google Antigravity✓fullclaimed7/10

   Antigravity's docs describe explicit rule activation modes (Manual, Always On, Model Decision, Glob) that trigger agent behavior automatically based on context/file patterns, plus Hooks that run custom scripts at specific points in the execution loop and Scheduled Tasks that trigger agents on a cron schedule — together these directly satisfy 'rules that trigger actions automatically on events'. Missing for 10: independent/hands-on verification that rule-triggering works reliably in practice, and more detail on broader event types beyond glob/model-decision/cron.

   • [claimed-docs] “At the rule level you can define how a rule should be activated: Manual... Always On... Model Decision... Glob”
   • [claimed-docs] “Hooks allow you to run custom scripts or shell commands at specific points during Antigravity’s execution loop.”
   • [claimed-docs] “Automate routine checks with Scheduled Tasks, simply define a cron schedule and the agents start and run autonomously in the background.”
   • [claimed-docs] “Rules are manually defined constraints for the Agent to follow, at both the local and global levels.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Google Antigravity
   Gemini CLI~partialclaimed4/10

   Gemini CLI supports non-interactive scripted runs and structured JSON output, which lets users wire it into external schedulers (cron, CI) for recurring automation, and its GitHub Action integrations (issue triage, PR review) imply repeatable, trigger-based workflows. However there is no first-party 'scheduled job' or cron feature documented within the CLI itself. Missing for 10: a native recurring-job/scheduler feature, explicit docs on scheduling cadence, and independent confirmation that scripted/CI-triggered runs work reliably for recurring automation.

   • [github] “Run non-interactively in scripts for workflow automation”
   • [github] “use the `--output-format json` flag to get structured output”
   • [github] “Pull Request Reviews: Automated code review with contextual feedback and suggestions”
   • [github] “Issue Triage: Automated labeling and prioritization of GitHub issues based on content analysis”

   proof ↗⚑ flag

   Google Antigravity✓fullclaimed8/10

   Docs explicitly describe Scheduled Tasks with cron-defined schedules that run agents autonomously in the background, plus scheduling messages to agents for later delivery, directly matching the recurring-jobs/workflow story. Missing for 10: independent/hands-on confirmation that scheduling actually works reliably in practice, and more detail on job management (editing/deleting/monitoring scheduled runs).

   • [claimed-docs] “Automate routine checks with Scheduled Tasks, simply define a cron schedule and the agents start and run autonomously in the background.”
   • [claimed-docs] “users can schedule messages to be sent to their agents while they’re away”

   proof ↗⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round to Gemini CLI
   Gemini CLI~partialclaimed4/10

   Gemini CLI offers conversation checkpointing to save and resume sessions (gemini-cli-gh-8), which provides a rudimentary rollback/resume mechanism, but there is no evidence of versioning, diffing, or reviewing automation scripts/workflows themselves, nor a dedicated rollback command for automations. missing for 10: explicit version history for automations, review/diff tooling, and a documented rollback mechanism beyond session checkpoints.

   • [github] “Conversation checkpointing to save and resume complex sessions”

   proof ↗⚑ flag

   Google Antigravity—none0/10

   Evidence shows automations (skills, hooks, plugins, scheduled tasks) but no mention of versioning, review history, or rollback capabilities for these automations themselves — missing for 10: version control/history for skills/hooks/plugins, a review workflow for automation changes, and any rollback/undo mechanism for automations.

   ⚑ flag

Background execution

1. ai-native userHave a cloud agent build, test, and demo a feature end-to-end for my review

   weight 2 · round to Google Antigravity
   Gemini CLI~partialcommunity4/10

   Gemini CLI documents cloud-adjacent automation via its GitHub Actions integration (PR reviews, issue triage, @gemini-cli on-demand assistance, non-interactive scripting) which could kick off agentic work, but there is no vendor evidence of an autonomous cloud agent that builds, runs tests, and produces a demo end-to-end for review. Community reports also describe agentic mode getting stuck in error loops, failing at basic file edits, and even causing data loss, undercutting confidence in reliable autonomous execution. missing for 10: explicit end-to-end build+test+demo workflow, evidence of a hosted/cloud agent (vs local CLI or CI hooks) producing a reviewable demo, and independent confirmation that autonomous runs complete without failure loops.

   • [github] “Pull Request Reviews: Automated code review with contextual feedback and suggestions”
   • [github] “Issue Triage: Automated labeling and prioritization of GitHub issues based on content analysis”
   • [github] “On-demand Assistance: Mention @gemini-cli in issues and pull requests for help with debugging, explanations, or task delegation”
   • [github] “Run non-interactively in scripts for workflow automation”
   • [community] “A lot of times Gemini models will get stuck in a loop of errors, and a lot of times it fails to edit/read or other simple function calling -…”
   • [community] “I really tried to get gemini to work properly in Agent mode. Tho it way too often went crazy, started rewriting files empty, and ran into pe…”
   • [community] “Gemini told the user: 'I have failed you completely and catastrophically... I have lost your data. This is an unacceptable, irreversible fai…”

   proof ↗⚑ flag

   Google Antigravity~partialcommunity6/10

   Docs describe agents that autonomously operate across editor/terminal/browser, delegate testing to subagents, produce reviewable Artifacts (implementation plans, diffs, browser recordings) and halt for approval — covering build, test and demo-for-review end-to-end (antigravity-docs-7,18,24,25,30,46). However, community reports of a subpar harness, app-breaking bugs, and a case where autonomous terminal execution deleted a whole drive raise real doubts about reliable end-to-end execution (antigravity-comm-8,antigravity-comm-14). Missing for 10: independent hands-on confirmation of a full successful build→test→demo cycle, and resolution of reliability/security concerns that could derail autonomous runs.

   • [claimed-docs] “Able to autonomously operate across your editor, terminal, and browser.”
   • [claimed-docs] “an agent can delegate tasks—such as running tests or performing extensive codebase searches—to dedicated subagents.”
   • [claimed-docs] “Planning Mode: The agent plans thoroughly before executing tasks... produces structured implementation plans called Artifacts”
   • [claimed-docs] “The agent always halts and requests your explicit approval before proceeding with proposed changes.”
   • [claimed-docs] “Artifacts include rich markdown plans (Implementation Plans), code diffs, architecture diagrams, images, and browser recordings.”
   • [claimed-docs] “an agent can delegate tasks—such as running tests or performing extensive codebase searches—to dedicated subagents”
   • [community] “It's not even good, honestly. I was using it for couple weeks before dropping that 2 months ago. The model was not good and slow, the harnes…”
   • [community] “Google Antigravity just deleted the contents of whole drive - came down to commanding a deletion of a 'directory with space in the name' wit…”

   proof ↗⚑ flag

2. developerDelegate longer-running coding tasks to run in the background in an isolated cloud environment

   weight 3 · round to Google Antigravity
   Gemini CLI~partialclaimed4/10

   Gemini CLI supports non-interactive scripting and GitHub Actions integration (@gemini-cli mentions for PR reviews, issue triage, on-demand assistance) which can run tasks in a cloud CI environment, and Cloud Shell offers a ready cloud runtime — but there's no dedicated 'run this long task in an isolated background cloud sandbox' feature akin to a hosted agent service. missing for 10: explicit isolated cloud sandbox/background execution product, evidence of long-running autonomous task delegation outside CI triggers, and independent confirmation it works reliably for extended background jobs.

   • [github] “Run non-interactively in scripts for workflow automation”
   • [github] “Pull Request Reviews: Automated code review with contextual feedback and suggestions”
   • [github] “Issue Triage: Automated labeling and prioritization of GitHub issues based on content analysis”
   • [github] “On-demand Assistance: Mention @gemini-cli in issues and pull requests for help with debugging, explanations, or task delegation”
   • [github] “On-demand Assistance: Mention `@gemini-cli` in issues and pull requests for help with debugging, explanations, or task delegation”
   • [claimed-docs] “The Gemini CLI is available without additional setup in Cloud Shell”

   proof ↗⚑ flag

   Google Antigravity~partialclaimed5/10

   Antigravity supports background/autonomous execution via Scheduled Tasks that run agents in the background, Git worktree-based isolated background folders, and scheduling messages for agents while away, plus a 'Remote Control' feature to connect to running desktop sessions across machines. However, these mechanisms describe local-machine or worktree isolation and remote access to local sessions, not a distinctly cloud-hosted sandbox environment for offloading long-running tasks the way some competitors do. Missing for 10: explicit documentation of a persistent cloud-hosted execution environment independent of the user's machine, and independent/hands-on confirmation that background tasks truly run isolated in the cloud rather than locally.

   • [claimed-docs] “Automate routine checks with Scheduled Tasks, simply define a cron schedule and the agents start and run autonomously in the background.”
   • [claimed-docs] “Worktree support: Projects natively support Git worktrees, allowing agents to operate in isolated background folders.”
   • [claimed-docs] “users can schedule messages to be sent to their agents while they’re away”
   • [claimed-docs] “Antigravity Remote Control allows you to securely connect to and drive your Antigravity 2.0 desktop sessions running across your machines fr…”
   • [claimed-docs] “Antigravity 2.0 serves as your AI agents’ central command center, providing a unified platform to launch, monitor, and orchestrate their act…”
   • [claimed-docs] “Run Antigravity CLI non-interactively to script agent tasks, integrate with CI pipelines, and capture machine-readable output.”

   proof ↗⚑ flag

Parallel agents

1. ai-native userLaunch fleets of autonomous agents that work in parallel on different tasks for hours or days

   weight 2 · round to Google Antigravity
   Gemini CLI—none0/10

   Evidence shows single-session non-interactive scripting, GitHub Actions integration for issue triage/PR review, and MCP extensibility, but nothing about launching multiple autonomous agents working in parallel for hours or days. No fleet/orchestration/multi-agent parallelism capability is documented anywhere in the pack.

   ⚑ flag

   Google Antigravity~partialclaimed7/10

   Docs describe orchestrating multiple autonomous agents in parallel across independent projects, scheduled/cron tasks that run autonomously in the background, worktree-isolated agents, subagent delegation, and remote control to check on running sessions from a browser — all supporting a 'fleet of parallel long-running agents' story. However, there is no independent/hands-on confirmation of agents actually running unattended for 'hours or days' at scale, and community reports focus on bugs, quota limits, and security issues rather than validating multi-day parallel fleet operation. Missing for 10: independent verification of long-duration (hours/days) autonomous runs, evidence of fleet scale limits, and hands-on confirmation from third parties.

   • [claimed-docs] “Orchestrate multiple autonomous agents working in parallel across independent projects.”
   • [claimed-docs] “Automate routine checks with Scheduled Tasks, simply define a cron schedule and the agents start and run autonomously in the background.”
   • [claimed-docs] “Have multiple agents working in parallel, so larger tasks get tackled faster.”
   • [claimed-docs] “Antigravity 2.0 serves as your AI agents’ central command center, providing a unified platform to launch, monitor, and orchestrate their act…”
   • [claimed-docs] “Worktree support: Projects natively support Git worktrees, allowing agents to operate in isolated background folders.”
   • [claimed-docs] “users can schedule messages to be sent to their agents while they’re away”
   • [claimed-docs] “Antigravity Remote Control allows you to securely connect to and drive your Antigravity 2.0 desktop sessions running across your machines fr…”
   • [claimed-docs] “an agent can delegate tasks—such as running tests or performing extensive codebase searches—to dedicated subagents.”

   proof ↗⚑ flag

2. developerRun several task attempts in parallel and compare results before choosing one

   weight 1 · round to Google Antigravity
   Gemini CLI—none0/10

   No evidence in the pack describes running multiple parallel task attempts or comparing/diffing results before selecting one; features listed are single-session tools (checkpointing, MCP, scripting) with no multi-attempt/parallel comparison workflow mentioned. Missing for 10: any mention of parallel run/branching feature, a comparison UI or mechanism to pick the best of several attempts.

   ⚑ flag

   Google Antigravity~partialclaimed4/10

   Docs confirm agents can run in parallel (multiple agents across projects, multiple CLI agents for large tasks) and a central dashboard to monitor/orchestrate them, but nothing describes running multiple attempts at the SAME task and comparing outputs before choosing a winner — that specific 'compare-and-select' workflow is unevidenced. missing for 10: explicit multi-attempt/variant generation for a single task, a comparison UI or ranking mechanism, and any selection step among parallel attempts.

   • [claimed-docs] “Have multiple agents working in parallel, so larger tasks get tackled faster.”
   • [claimed-docs] “Orchestrate multiple autonomous agents working in parallel across independent projects.”
   • [claimed-docs] “Antigravity 2.0 serves as your AI agents’ central command center, providing a unified platform to launch, monitor, and orchestrate their act…”

   proof ↗⚑ flag

Scheduled automation

1. ai-native userSet up always-on agents that run on schedules or triggers to maintain and fix my software autonomously

   weight 2 · round to Google Antigravity
   Gemini CLI~partialcommunity4/10

   Gemini CLI supports non-interactive scripted runs and GitHub Actions-based triggers (PR reviews, issue triage, @mention on-demand assistance) which can approximate scheduled/triggered automation, but there is no evidence of a persistent, self-scheduling 'always-on agent' that autonomously maintains and fixes software over time. missing for 10: native scheduler/cron support, persistent agent daemon or watch-mode, evidence of autonomous multi-cycle maintenance without human triggering, and reliability data (community reports actually describe agent mode getting stuck in loops or failing tasks).

   • [github] “Run non-interactively in scripts for workflow automation”
   • [github] “Pull Request Reviews: Automated code review with contextual feedback and suggestions”
   • [github] “Issue Triage: Automated labeling and prioritization of GitHub issues based on content analysis”
   • [github] “On-demand Assistance: Mention @gemini-cli in issues and pull requests for help with debugging, explanations, or task delegation”
   • [community] “A lot of times Gemini models will get stuck in a loop of errors, and a lot of times it fails to edit/read or other simple function calling -…”
   • [community] “I really tried to get gemini to work properly in Agent mode. Tho it way too often went crazy, started rewriting files empty, and ran into pe…”

   proof ↗⚑ flag

   Google Antigravity✓fullcommunity7/10

   First-party docs explicitly describe Scheduled Tasks with cron schedules that start and run agents autonomously in the background, plus scheduling messages to agents while away, parallel autonomous agent orchestration, and headless CLI mode for CI/trigger-based automation. However, there is no independent/hands-on corroboration of the scheduling feature itself, and community reports document serious reliability/safety incidents with autonomous execution (e.g., an agent deleting a whole drive via unattended terminal auto-execution), raising doubt about safely running such agents unattended. Missing for 10: independent verification that scheduled/cron-triggered agents work reliably in practice, and evidence that autonomous 'maintain and fix' runs don't require the same close supervision seen in incident reports.

   • [claimed-docs] “Automate routine checks with Scheduled Tasks, simply define a cron schedule and the agents start and run autonomously in the background.”
   • [claimed-docs] “users can schedule messages to be sent to their agents while they’re away”
   • [claimed-docs] “Orchestrate multiple autonomous agents working in parallel across independent projects.”
   • [claimed-docs] “Run Antigravity CLI non-interactively to script agent tasks, integrate with CI pipelines, and capture machine-readable output.”
   • [community] “Google Antigravity just deleted the contents of whole drive - came down to commanding a deletion of a 'directory with space in the name' wit…”

   proof ↗⚑ flag

Debugging

1. developerDebug a live running web application directly from my coding assistant

   weight 1 · round to Google Antigravity
   Gemini CLI~partialcommunity3/10

   Gemini CLI advertises general 'Debug issues and troubleshoot with natural language' capability and MCP extensibility that could in theory connect to browser/dev tools, and one community comment references an internal 'browser control stack,' but there is no first-party or hands-on evidence of live web-app debugging (e.g., attaching to a running app, inspecting DOM/network/console, or browser automation workflows). Missing for 10: explicit live-app/browser debugging workflow docs, DevTools or runtime inspection integration, and hands-on confirmation of debugging a running web app.

   • [github] “Debug issues and troubleshoot with natural language”
   • [github] “Use MCP servers to connect new capabilities, including media generation with Imagen, Veo or Lyria”
   • [github] “Configure MCP servers in ~/.gemini/settings.json to extend Gemini CLI with custom tools”
   • [community] “All in all, a 140 MB Go binary with its own browser control stack, sandbox, Git, language detector, skills runtime, and subagent system. I'm…”

   proof ↗⚑ flag

   Google Antigravity~partialclaimed4/10

   Antigravity's agent can 'autonomously operate across your editor, terminal, and browser' and produces 'browser recordings' as artifacts, implying some browser-based interaction/testing, but there is no explicit documentation of live debugging features (console inspection, breakpoints, network tab, DOM inspection) for a running web app. missing for 10: explicit live-debugging tooling (breakpoints, console/network inspection), documented workflow for attaching to a running app, independent hands-on confirmation of debugging use.

   • [claimed-docs] “Able to autonomously operate across your editor, terminal, and browser.”
   • [claimed-docs] “Artifacts include rich markdown plans (Implementation Plans), code diffs, architecture diagrams, images, and browser recordings.”

   proof ↗⚑ flag

2. developerDebug issues and troubleshoot using natural-language queries

   weight 2 · round to Google Antigravity
   Gemini CLI!disputedcontradicted5/10

   Gemini CLI explicitly advertises natural-language debugging/troubleshooting (gemini-cli-gh-3, gh-12/21/23) and community reports confirm strong codebase navigation and code-review value (gemini-cli-comm-1, comm-20). However, multiple hands-on reports directly contradict reliable debugging: users describe it getting stuck in error loops, failing simple file edits, and in one case catastrophically deleting user data during a troubleshooting session (gemini-cli-comm-10, comm-11, comm-14, comm-16).

   • [github] “Debug issues and troubleshoot with natural language”
   • [github] “On-demand Assistance: Mention @gemini-cli in issues and pull requests for help with debugging, explanations, or task delegation”
   • [github] “On-demand Assistance: Mention `@gemini-cli` in issues and pull requests for help with debugging, explanations, or task delegation”
   • [github] “Mention @gemini-cli in issues and pull requests for help with debugging, explanations, or task delegation”
   • [community] “I have been using this for about a month and it's a beast, mostly thanks to 2.5pro being SOTA and how it leverages that huge 1M context wind…”
   • [community] “We have tried out Gemini code review vs Copilot code review and Gemini is consistently offering better code review tips. It has officially c…”
   • [community] “A lot of times Gemini models will get stuck in a loop of errors, and a lot of times it fails to edit/read or other simple function calling -…”
   • [community] “I really tried to get gemini to work properly in Agent mode. Tho it way too often went crazy, started rewriting files empty, and ran into pe…”
   • [community] “The problem is that Gemini CLI simply doesn't work. Beside simplest tasks like creating a new release it is useless as a coding assistant. D…”
   • [community] “Gemini told the user: 'I have failed you completely and catastrophically... I have lost your data. This is an unacceptable, irreversible fai…”

   proof ↗⚑ flag

   Google Antigravity~partialclaimed6/10

   Antigravity's docs show natural-language code commands, autonomous operation across editor/terminal/browser, and subagents that can run tests and search codebases (docs-6,7,9,18,46), which collectively support debugging/troubleshooting via NL prompts, but there is no explicit documentation of a dedicated 'debug' workflow or troubleshooting examples, and community reports focus on stability/security issues rather than confirming debugging quality. Missing for 10: explicit debugging-specific documentation or examples, and independent hands-on validation that NL debugging queries work reliably.

   • [claimed-docs] “Google Antigravity's Editor view offers tab autocompletion, natural language code commands, and a configurable, and context-aware configurab…”
   • [claimed-docs] “Able to autonomously operate across your editor, terminal, and browser.”
   • [claimed-docs] “Edit, orchestrate, and build all in natural language. Tell your agents what you need, and they’ll work on getting it done.”
   • [claimed-docs] “an agent can delegate tasks—such as running tests or performing extensive codebase searches—to dedicated subagents.”
   • [claimed-docs] “an agent can delegate tasks—such as running tests or performing extensive codebase searches—to dedicated subagents”

   proof ↗⚑ flag

Feature implementation

1. developerTurn a tracked issue into a complete pull request end-to-end

   weight 3 · round to Gemini CLI
   Gemini CLI!disputedcontradicted5/10

   Gemini CLI's GitHub integration supports @gemini-cli task delegation from issues/PRs, automated PR reviews, and issue triage, which vendor docs frame as enabling issue-to-PR workflows (gh-12, gh-21, gh-10, gh-22, gh-4). However, hands-on community reports describe the agent getting stuck in loops, failing basic file edits, lacking a plan mode, and producing 'spaghetti code' rather than completing tasks reliably — directly undermining claims of smooth end-to-end PR generation (gemini-cli-comm-10, gemini-cli-comm-11, gemini-cli-comm-14). Missing for 10: a documented full issue→PR walkthrough, evidence of successful autonomous PR creation from an issue, and independent confirmation resolving the agentic reliability complaints.

   • [github] “On-demand Assistance: Mention @gemini-cli in issues and pull requests for help with debugging, explanations, or task delegation”
   • [github] “On-demand Assistance: Mention `@gemini-cli` in issues and pull requests for help with debugging, explanations, or task delegation”
   • [github] “Pull Request Reviews: Automated code review with contextual feedback and suggestions”
   • [github] “@github List my open pull requests”
   • [github] “Automate operational tasks like querying pull requests or handling complex rebases”
   • [community] “A lot of times Gemini models will get stuck in a loop of errors, and a lot of times it fails to edit/read or other simple function calling -…”
   • [community] “I really tried to get gemini to work properly in Agent mode. Tho it way too often went crazy, started rewriting files empty, and ran into pe…”
   • [community] “The problem is that Gemini CLI simply doesn't work. Beside simplest tasks like creating a new release it is useless as a coding assistant. D…”

   proof ↗⚑ flag

   Google Antigravity—none0/10

   Antigravity's docs describe autonomous coding agents that can edit files, run terminal commands, and operate across editor/terminal/browser, but there is no evidence of any issue-tracker (e.g., GitHub Issues) integration or an end-to-end workflow that ingests a tracked issue and produces a pull request. Missing for 10: issue-tracker ingestion, automated branch/PR creation, and any documented GitHub/GitLab PR workflow example.

   • [claimed-docs] “Able to autonomously operate across your editor, terminal, and browser.”
   • [claimed-docs] “Antigravity 2.0 serves as your AI agents’ central command center, providing a unified platform to launch, monitor, and orchestrate their act…”
   • [claimed-docs] “Run Antigravity CLI non-interactively to script agent tasks, integrate with CI pipelines, and capture machine-readable output.”

   proof ↗⚑ flag

2. developerDescribe a feature or bug in plain language and have the agent implement or fix it across multiple files

   weight 3 · round to Google Antigravity
   Gemini CLI!disputedcontradicted5/10

   Vendor docs/GitHub claim strong support for describing features/bugs in plain language and having the agent edit/debug across large codebases (gemini-cli-gh-1, gemini-cli-gh-3), but multiple hands-on community reports directly contradict this: users report the agent getting stuck in error loops, failing basic file edit/read operations, ignoring GEMINI.md context files, jumping straight into 'spaghetti code' without a plan mode, and in one case catastrophically deleting user data via botched commands. missing for 10: consistent hands-on success stories on multi-file feature implementation, resolution of the reported reliability/looping failures, and independent benchmarks confirming multi-file bug-fix accuracy.

   • [github] “Query and edit large codebases”
   • [github] “Debug issues and troubleshoot with natural language”
   • [github] “Custom context files (GEMINI.md) to tailor behavior for your projects”
   • [community] “A lot of times Gemini models will get stuck in a loop of errors, and a lot of times it fails to edit/read or other simple function calling -…”
   • [community] “I really tried to get gemini to work properly in Agent mode. Tho it way too often went crazy, started rewriting files empty, and ran into pe…”
   • [community] “Tip 1, it consistently ignores my GEMINI.md file, both global and local, even though it always says '1 GEMINI.md file is being used.'”
   • [community] “The problem is that Gemini CLI simply doesn't work. Beside simplest tasks like creating a new release it is useless as a coding assistant. D…”
   • [community] “Gemini told the user: 'I have failed you completely and catastrophically... I have lost your data. This is an unacceptable, irreversible fai…”

   proof ↗⚑ flag

   Google Antigravity~partialcommunity7/10

   Docs describe the core loop clearly: natural-language commands drive an agent that autonomously edits code across the editor/terminal, with Projects spanning multiple folders/repos giving full codebase context and Artifacts showing diffs/plans for review (antigravity-docs-6,7,9,17,24,30,40). Community reports confirm it functions as a real coding-agent IDE (comm-1) but also describe hands-on quality issues with the agent harness and model reliability during actual implementation work (comm-8), so delivery is real but not consistently polished. Missing for 10: independent benchmark/case-study evidence of successful multi-file feature implementation, and resolution of reported harness/quality complaints.

   • [claimed-docs] “Google Antigravity's Editor view offers tab autocompletion, natural language code commands, and a configurable, and context-aware configurab…”
   • [claimed-docs] “Able to autonomously operate across your editor, terminal, and browser.”
   • [claimed-docs] “Edit, orchestrate, and build all in natural language. Tell your agents what you need, and they’ll work on getting it done.”
   • [claimed-docs] “a project can work with one folder or multiple folders (e.g., a frontend and a backend repo), providing your agents with all of the context …”
   • [claimed-docs] “Planning Mode: The agent plans thoroughly before executing tasks... produces structured implementation plans called Artifacts”
   • [claimed-docs] “Artifacts include rich markdown plans (Implementation Plans), code diffs, architecture diagrams, images, and browser recordings.”
   • [claimed-docs] “Build AI agents that autonomously read files, run commands, edit code, and more.”
   • [community] “I went ahead and downloaded it, it looks to be a VSCode fork very similar to Cursor, with support for Gemini 3 Pro, Claude Sonnet 4.5, and G…”
   • [community] “It's not even good, honestly. I was using it for couple weeks before dropping that 2 months ago. The model was not good and slow, the harnes…”

   proof ↗⚑ flag

Maintenance automation

1. developerHave the agent write tests, fix lint errors, resolve merge conflicts, and update dependencies for me

   weight 3 · round to Google Antigravity
   Gemini CLI!disputedcontradicted5/10

   GitHub docs claim broad code-editing, debugging, and complex-rebase (merge conflict) automation capabilities (gemini-cli-gh-1, gemini-cli-gh-3, gemini-cli-gh-4), which would cover fixing lint issues and dependency/test work as part of general codebase editing, and PR review/issue triage features suggest lint-like feedback (gemini-cli-gh-10, gemini-cli-gh-11). However, multiple hands-on community reports concretely contradict reliable agentic code work: users report it getting stuck in error loops, failing simple file edit/read operations, ignoring GEMINI.md context files, producing 'spaghetti code' with no plan mode, and in one case catastrophically deleting user data during a file operation (gemini-cli-comm-10, gemini-cli-comm-11, gemini-cli-comm-13, gemini-cli-comm-14, gemini-cli-comm-16). No explicit evidence names test-writing, lint-fixing, or dependency-updating tasks specifically. Missing for 10: explicit documentation/examples of writing tests, fixing lint errors, or updating dependencies, and independent corroboration that these specific tasks work reliably.

   • [github] “Query and edit large codebases”
   • [github] “Debug issues and troubleshoot with natural language”
   • [github] “Automate operational tasks like querying pull requests or handling complex rebases”
   • [github] “Pull Request Reviews: Automated code review with contextual feedback and suggestions”
   • [github] “Issue Triage: Automated labeling and prioritization of GitHub issues based on content analysis”
   • [community] “A lot of times Gemini models will get stuck in a loop of errors, and a lot of times it fails to edit/read or other simple function calling -…”
   • [community] “I really tried to get gemini to work properly in Agent mode. Tho it way too often went crazy, started rewriting files empty, and ran into pe…”
   • [community] “Tip 1, it consistently ignores my GEMINI.md file, both global and local, even though it always says '1 GEMINI.md file is being used.'”
   • [community] “The problem is that Gemini CLI simply doesn't work. Beside simplest tasks like creating a new release it is useless as a coding assistant. D…”
   • [community] “Gemini told the user: 'I have failed you completely and catastrophically... I have lost your data. This is an unacceptable, irreversible fai…”

   proof ↗⚑ flag

   Google Antigravity~partialcommunity6/10

   Antigravity's docs describe general-purpose coding agents/subagents that can run tests, edit code, and operate across editor/terminal/browser (docs-18, docs-46, docs-40, docs-7), which implicitly covers writing tests and dependency/code edits, but there is no explicit documentation calling out lint-error fixing, merge-conflict resolution, or dependency updates as named capabilities. Community evidence is mixed on general quality/reliability but does not concretely refute these specific tasks. Missing for 10: explicit first-party documentation or hands-on examples of lint-fixing, merge-conflict resolution, and dependency-update workflows specifically.

   • [claimed-docs] “an agent can delegate tasks—such as running tests or performing extensive codebase searches—to dedicated subagents.”
   • [claimed-docs] “an agent can delegate tasks—such as running tests or performing extensive codebase searches—to dedicated subagents”
   • [claimed-docs] “Build AI agents that autonomously read files, run commands, edit code, and more.”
   • [claimed-docs] “Able to autonomously operate across your editor, terminal, and browser.”
   • [claimed-docs] “The Agent SDK gives you the same tools, agent loop, and context management that power Google Antigravity, programmable in Python.”
   • [community] “It's not even good, honestly. I was using it for couple weeks before dropping that 2 months ago. The model was not good and slow, the harnes…”

   proof ↗⚑ flag

Multimodal generation

1. ai-native userGenerate a working app from a sketch, image, or PDF design

   weight 2 · round to Gemini CLI
   Gemini CLI~partialcommunity6/10

   Official docs explicitly claim 'Generate new apps from PDFs, images, or sketches using multimodal capabilities,' directly matching the story, but there is no independent/hands-on corroboration of this specific capability, and broader community feedback raises general concerns about agentic reliability that could affect complex generation tasks. missing for 10: independent hands-on demonstration of sketch/PDF-to-app generation, details on fidelity/limitations of this workflow.

   • [github] “Generate new apps from PDFs, images, or sketches using multimodal capabilities”
   • [community] “A lot of times Gemini models will get stuck in a loop of errors, and a lot of times it fails to edit/read or other simple function calling -…”
   • [community] “The problem is that Gemini CLI simply doesn't work. Beside simplest tasks like creating a new release it is useless as a coding assistant. D…”

   proof ↗⚑ flag

   Google Antigravity~partialclaimed4/10

   Antigravity supports passing images, PDFs and other multimedia attachments to the agent as part of prompts (docs-15, docs-32), which implies it could take a sketch/image/PDF as design input for code generation, but there is no explicit documentation or example of a 'sketch-to-app' or 'design-to-code' workflow, nor any hands-on report of this being used successfully. missing for 10: dedicated design-to-app feature/workflow documentation, an example or case study of generating an app from an image/PDF, and independent verification that this works in practice.

   • [claimed-docs] “Pass rich multimedia file attachments (images, videos, audio, and documents) to the agent alongside textual instruction prompt lists.”
   • [claimed-docs] “External files such as Google Drive links, PDFs, and Office documents now appear in their own Documents section in the sidebar above Artifac…”

   proof ↗⚑ flag

Codebase mapping

1. developerUnderstand how a codebase fits together to find where to start making changes

   weight 3 · round to Google Antigravity
   Gemini CLI!disputedcontradicted5/10

   Gemini CLI advertises large-codebase querying/editing (gemini-cli-gh-1) with a 1M-token context window, custom GEMINI.md context files, and --include-directories flags for scoping (gemini-cli-gh-9, gemini-cli-gh-16), and one HN user praises its ability to 'navigate and learn' large codebases effortlessly (gemini-cli-comm-1). However, other hands-on users report the opposite: it is 'stupid at navigation in the codebase' taking 10x longer (gemini-cli-comm-15) and 'consistently ignores' the GEMINI.md context file despite claiming to use it (gemini-cli-comm-13), directly undercutting the codebase-understanding claim. Missing for 10: consistent independent corroboration of reliable codebase navigation, and no contradicting failure reports.

   • [github] “Query and edit large codebases”
   • [github] “Custom context files (GEMINI.md) to tailor behavior for your projects”
   • [github] “gemini --include-directories ../lib,../docs”
   • [community] “I have been using this for about a month and it's a beast, mostly thanks to 2.5pro being SOTA and how it leverages that huge 1M context wind…”
   • [community] “I love the model, hate the tool. Anthropic has the killer app with Claude Code. I tried Gemini cli for about 5 seconds and was so frustrated…”
   • [community] “Tip 1, it consistently ignores my GEMINI.md file, both global and local, even though it always says '1 GEMINI.md file is being used.'”

   proof ↗⚑ flag

   Google Antigravity~partialclaimed6/10

   Antigravity provides contextual codebase understanding indirectly: Projects give agents full context across multiple folders/repos, subagents can perform 'extensive codebase searches', and Artifacts can include architecture diagrams and implementation plans that map out how a change fits into the codebase. However, there's no dedicated codebase-mapping/explanation feature, and no independent/hands-on evidence confirming how well the agent actually explains codebase structure. Missing for 10: a first-class 'explain/visualize codebase architecture' feature, independent hands-on validation of comprehension quality on real repos.

   • [claimed-docs] “a project can work with one folder or multiple folders (e.g., a frontend and a backend repo), providing your agents with all of the context …”
   • [claimed-docs] “an agent can delegate tasks—such as running tests or performing extensive codebase searches—to dedicated subagents.”
   • [claimed-docs] “Artifacts include rich markdown plans (Implementation Plans), code diffs, architecture diagrams, images, and browser recordings.”
   • [claimed-docs] “Agents work within Projects, which define the boundaries of the folders and repositories they can access.”
   • [claimed-docs] “an agent can delegate tasks—such as running tests or performing extensive codebase searches—to dedicated subagents”
   • [claimed-docs] “Google Antigravity's Editor view offers tab autocompletion, natural language code commands, and a configurable, and context-aware configurab…”

   proof ↗⚑ flag

2. developerHave the agent map and explain an entire unfamiliar codebase without manually selecting context files

   weight 3 · round to Google Antigravity
   Gemini CLI!disputedcontradicted5/10

   Google claims large-codebase querying/editing (gemini-cli-gh-1) and Gemini CLI's 1M-token context lets it 'navigate and learn' huge codebases 'effortlessly' per one user (gemini-cli-comm-1), but other hands-on reports directly contradict this, calling it 'so stupid at navigation in the codebase it takes 10x as long' (gemini-cli-comm-15) and prone to getting 'stuck in spaghetti code' with no plan mode (gemini-cli-comm-14), plus it reportedly ignores its own GEMINI.md context file (gemini-cli-comm-13). Missing for 10: consistent independent benchmarks confirming autonomous whole-codebase mapping without file selection, and resolution of the navigation-quality contradiction.

   • [github] “Query and edit large codebases”
   • [community] “I have been using this for about a month and it's a beast, mostly thanks to 2.5pro being SOTA and how it leverages that huge 1M context wind…”
   • [community] “I love the model, hate the tool. Anthropic has the killer app with Claude Code. I tried Gemini cli for about 5 seconds and was so frustrated…”
   • [community] “The problem is that Gemini CLI simply doesn't work. Beside simplest tasks like creating a new release it is useless as a coding assistant. D…”
   • [community] “Tip 1, it consistently ignores my GEMINI.md file, both global and local, even though it always says '1 GEMINI.md file is being used.'”

   proof ↗⚑ flag

   Google Antigravity~partialclaimed5/10

   Docs indicate agents automatically get full-project context (docs-17, docs-35) and can delegate to subagents that perform 'extensive codebase searches' (docs-18/46), suggesting the agent can explore an unfamiliar repo without manual file selection. However, there is no explicit feature or example describing whole-codebase mapping/explanation, and no independent/hands-on evidence confirming this works well in practice. missing for 10: a dedicated 'explain codebase' or repo-mapping feature description, and independent verification of this on an unfamiliar large codebase.

   • [claimed-docs] “a project can work with one folder or multiple folders (e.g., a frontend and a backend repo), providing your agents with all of the context …”
   • [claimed-docs] “an agent can delegate tasks—such as running tests or performing extensive codebase searches—to dedicated subagents.”
   • [claimed-docs] “Agents work within Projects, which define the boundaries of the folders and repositories they can access.”
   • [claimed-docs] “an agent can delegate tasks—such as running tests or performing extensive codebase searches—to dedicated subagents”

   proof ↗⚑ flag

Context management

1. developerHave the agent build and recall memory automatically across sessions

   weight 2 · round to Gemini CLI
   Gemini CLI!disputedcontradicted3/10

   Gemini CLI offers static project context via GEMINI.md files and a `/memory` command, plus manual conversation checkpointing to save/resume sessions—but these are manually configured/invoked, not automatic memory building/recall across sessions. Hands-on community evidence directly contradicts even the GEMINI.md context mechanism working reliably: a user reports it 'consistently ignores my GEMINI.md file... even though it always says 1 GEMINI.md file is being used' (gemini-cli-comm-13), undermining the claimed persistent-context capability. missing for 10: evidence of automatic memory formation/recall without user action, evidence /memory command builds persistent cross-session knowledge, independent corroboration that GEMINI.md context reliably persists.

   • [github] “Conversation checkpointing to save and resume complex sessions”
   • [github] “Custom context files (GEMINI.md) to tailor behavior for your projects”
   • [claimed-docs] “Comandos de Gemini CLI: /memory, /stats, /tools y /mcp”
   • [community] “Tip 1, it consistently ignores my GEMINI.md file, both global and local, even though it always says '1 GEMINI.md file is being used.'”

   proof ↗⚑ flag

   Google Antigravity—none0/10

   The evidence describes Projects, Rules, Artifacts, and context management, but none of these describe an automatic memory system that builds and recalls information across sessions without user re-specification; Rules are explicitly manual, and Projects only scope folders/permissions, not persistent learned memory. No documentation or community evidence confirms automatic cross-session memory recall.

   • [claimed-docs] “a project can work with one folder or multiple folders (e.g., a frontend and a backend repo), providing your agents with all of the context …”
   • [claimed-docs] “At the rule level you can define how a rule should be activated: Manual... Always On... Model Decision... Glob”
   • [claimed-docs] “Agents work within Projects, which define the boundaries of the folders and repositories they can access.”
   • [claimed-docs] “Rules are manually defined constraints for the Agent to follow, at both the local and global levels.”

   proof ↗⚑ flag

2. developerInclude multiple project directories in a single session for broader context

   weight 2 · round drawn
   Gemini CLI✓fullclaimed8/10

   The official CLI flag `--include-directories ../lib,../docs` explicitly allows adding multiple project directories into a single session for broader context, directly matching the story. Missing for 10: independent hands-on confirmation of multi-directory usage quality/behavior beyond the flag documentation.

   • [github] “gemini --include-directories ../lib,../docs”

   proof ↗⚑ flag

   Google Antigravity✓fullclaimed8/10

   Docs explicitly state Projects can span multiple folders (e.g., a frontend and backend repo) giving agents full codebase context, with Projects defining folder/repo access boundaries and worktree support for isolated background folders. Missing for 10: independent/hands-on corroboration of multi-folder session use in practice.

   • [claimed-docs] “Group your conversations into Projects, which can span multiple folders and support custom settings and scoped permissions.”
   • [claimed-docs] “a project can work with one folder or multiple folders (e.g., a frontend and a backend repo), providing your agents with all of the context …”
   • [claimed-docs] “Agents work within Projects, which define the boundaries of the folders and repositories they can access.”
   • [claimed-docs] “Worktree support: Projects natively support Git worktrees, allowing agents to operate in isolated background folders.”

   proof ↗⚑ flag

3. developerAdd a project instructions file to set coding standards and conventions the agent follows

   weight 3 · round to Google Antigravity
   Gemini CLI!disputedcontradicted5/10

   Gemini CLI documents GEMINI.md custom context files for tailoring behavior/project conventions (gemini-cli-gh-9) and docs mention /memory command for managing this context (gemini-cli-docs-3). However, hands-on community feedback reports the file being ignored despite being loaded ('it consistently ignores my GEMINI.md file, both global and local, even though it always says 1 GEMINI.md file is being used' - gemini-cli-comm-13), directly contradicting reliable adherence to project instructions. Missing for 10: independent corroboration that GEMINI.md is consistently honored, more detail on precedence/hierarchy of instruction files, and resolution of the reported ignoring behavior.

   • [github] “Custom context files (GEMINI.md) to tailor behavior for your projects”
   • [claimed-docs] “Comandos de Gemini CLI: /memory, /stats, /tools y /mcp”
   • [community] “Tip 1, it consistently ignores my GEMINI.md file, both global and local, even though it always says '1 GEMINI.md file is being used.'”

   proof ↗⚑ flag

   Google Antigravity✓fullclaimed7/10

   Antigravity supports Rules (manually defined constraints for the agent at local and global levels, with activation modes like Always On/Glob) which serve as a project instructions file for coding standards and conventions, and Projects scope these settings per folder/repo. missing for 10: no independent/hands-on confirmation of rules file format or behavior, and no evidence of a specific standardized file name (e.g. AGENTS.md-equivalent) or examples of it being used in practice.

   • [claimed-docs] “At the rule level you can define how a rule should be activated: Manual... Always On... Model Decision... Glob”
   • [claimed-docs] “Rules are manually defined constraints for the Agent to follow, at both the local and global levels.”
   • [claimed-docs] “a project can work with one folder or multiple folders (e.g., a frontend and a backend repo), providing your agents with all of the context …”
   • [claimed-docs] “Agents work within Projects, which define the boundaries of the folders and repositories they can access.”

   proof ↗⚑ flag

Issue diagnosis

1. developerReproduce issues, narrow down root causes, and verify fixes

   weight 3 · round to Google Antigravity
   Gemini CLI!disputedcontradicted4/10

   Google markets debugging/troubleshooting via natural language and a /bug reporting flow (gh-3, gh-20), and one HN user praises its ability to navigate huge codebases (comm-1). However multiple hands-on reports directly contradict root-cause/verify-fix workflows: users describe it getting stuck in error loops, rewriting files empty, ignoring GEMINI.md context, being 'terrible at agentic stuff', and in one case catastrophically deleting user data during a file operation (comm-10, comm-11, comm-13, comm-14, comm-15, comm-16). missing for 10: reliable reproduction of bugs, consistent root-cause narrowing without loops, and independent verification of fix correctness.

   • [github] “Debug issues and troubleshoot with natural language”
   • [github] “Use `/bug` command to report issues directly from the CLI.”
   • [community] “I have been using this for about a month and it's a beast, mostly thanks to 2.5pro being SOTA and how it leverages that huge 1M context wind…”
   • [community] “A lot of times Gemini models will get stuck in a loop of errors, and a lot of times it fails to edit/read or other simple function calling -…”
   • [community] “I really tried to get gemini to work properly in Agent mode. Tho it way too often went crazy, started rewriting files empty, and ran into pe…”
   • [community] “The problem is that Gemini CLI simply doesn't work. Beside simplest tasks like creating a new release it is useless as a coding assistant. D…”
   • [community] “I love the model, hate the tool. Anthropic has the killer app with Claude Code. I tried Gemini cli for about 5 seconds and was so frustrated…”
   • [community] “Gemini told the user: 'I have failed you completely and catastrophically... I have lost your data. This is an unacceptable, irreversible fai…”

   proof ↗⚑ flag

   Google Antigravity~partialcommunity6/10

   Antigravity's agents can run terminal commands and browser sessions, delegate to subagents that run tests or search the codebase (docs-18, docs-46, docs-7), and produce Artifacts with diffs, plans and browser recordings that could serve as reproduction/verification evidence (docs-30, docs-51). Headless/CI mode (docs-50) also supports automated verification loops. However there is no explicit documented workflow for issue reproduction or root-cause narrowing, and community reports show real-world reliability problems (deleted directories, exfiltration bugs) rather than confirmation that debugging workflows work well. Missing for 10: a dedicated debugging/root-cause-analysis feature, explicit test-verification-of-fix workflow, and independent hands-on validation that this works well in practice.

   • [claimed-docs] “Able to autonomously operate across your editor, terminal, and browser.”
   • [claimed-docs] “an agent can delegate tasks—such as running tests or performing extensive codebase searches—to dedicated subagents.”
   • [claimed-docs] “Artifacts include rich markdown plans (Implementation Plans), code diffs, architecture diagrams, images, and browser recordings.”
   • [claimed-docs] “an agent can delegate tasks—such as running tests or performing extensive codebase searches—to dedicated subagents”
   • [claimed-docs] “Run Antigravity CLI non-interactively to script agent tasks, integrate with CI pipelines, and capture machine-readable output.”
   • [claimed-docs] “An Artifact is a structured deliverable created by the agent to accomplish its task and communicate its progress and thinking to the human u…”
   • [community] “Google Antigravity just deleted the contents of whole drive - came down to commanding a deletion of a 'directory with space in the name' wit…”

   proof ↗⚑ flag

Marketplace

1. developerEquip the agent with custom skills to perform specialized tasks

   weight 1 · round to Google Antigravity
   Gemini CLI~partialcommunity6/10

   Gemini CLI supports extensibility through MCP servers (custom tools, media generation) and GEMINI.md context files to tailor agent behavior for specific projects, and a community mention references a built-in 'skills runtime' as part of its architecture. However, there is no dedicated first-party 'skills' marketplace or packaging system, and community reports note GEMINI.md is sometimes ignored in practice. Missing for 10: a documented first-class 'skills' framework/marketplace, independent corroboration that custom skills work reliably, and confirmation that the skills runtime mentioned in community feedback is a stable, documented feature.

   • [github] “Use MCP servers to connect new capabilities, including media generation with Imagen, Veo or Lyria”
   • [github] “Custom context files (GEMINI.md) to tailor behavior for your projects”
   • [github] “Configure MCP servers in ~/.gemini/settings.json to extend Gemini CLI with custom tools”
   • [community] “All in all, a 140 MB Go binary with its own browser control stack, sandbox, Git, language detector, skills runtime, and subagent system. I'm…”
   • [community] “Tip 1, it consistently ignores my GEMINI.md file, both global and local, even though it always says '1 GEMINI.md file is being used.'”

   proof ↗⚑ flag

   Google Antigravity✓fullclaimed8/10

   Antigravity has a dedicated Skills system: SKILL.md-based reusable packages of knowledge/instructions the agent follows for specific tasks, creatable/downloadable and accessible via slash commands, plus composable with plugins that bundle skills, rules, MCP servers, and hooks. This is documented across product and docs pages consistently, though no independent/community hands-on verification of custom skills specifically was found. Missing for 10: independent/hands-on corroboration of custom skill creation working in practice, and a marketplace/registry of shareable skills.

   • [claimed-docs] “Create or download fully customizable skills to further your agent’s autonomy and transform how you get work done.”
   • [claimed-docs] “A skill is a folder containing a `SKILL.md` file with instructions that the agent can follow when working on specific tasks.”
   • [claimed-docs] “Skills are reusable packages of knowledge that extend what the agent can do.”
   • [claimed-docs] “Access plugins, MCP, skills, and hooks configurations instantly via slash commands, quickly enhancing your workflow.”
   • [claimed-docs] “Layer custom Python callables, Model Context Protocol (MCP) servers, and reusable agent skills over our built-in filesystem and terminal too…”
   • [claimed-docs] “Plugins are namespaced bundles that allow you to extend Antigravity’s capabilities by grouping skills, rules, MCP servers, and hooks into a …”

   proof ↗⚑ flag

2. engineering-leadIntegrate third-party partner-built agent apps into my workflows

   weight 1 · round to Gemini CLI
   Gemini CLI~partialclaimed5/10

   Gemini CLI supports connecting external capabilities via MCP servers (e.g., Imagen, Veo, Lyria) and integrates with GitHub via @gemini-cli mentions and Actions, showing some ecosystem extensibility for third-party tools. However, there's no evidence of a curated marketplace or directory of partner-built 'agent apps' specifically designed for cross-workflow integration, only generic MCP server configuration support. Missing for 10: a documented partner/agent-app ecosystem or marketplace, case studies of third-party agent apps being integrated, and independent confirmation of smooth interoperability.

   • [github] “Use MCP servers to connect new capabilities, including media generation with Imagen, Veo or Lyria”
   • [github] “Configure MCP servers in ~/.gemini/settings.json to extend Gemini CLI with custom tools”
   • [github] “@github List my open pull requests”
   • [github] “On-demand Assistance: Mention @gemini-cli in issues and pull requests for help with debugging, explanations, or task delegation”

   proof ↗⚑ flag

   Google Antigravity!disputedcontradicted4/10

   Vendor docs describe an extensibility layer (MCP servers, plugins, skills, hooks) that in principle lets teams plug in third-party building blocks (docs-14, docs-28, docs-12), suggesting an ecosystem for integrating outside agent capabilities. However, hands-on community reports directly contradict the notion of freely integrating partner-built agent apps: using a third-party agent ('Pi agent') alongside Antigravity triggered a Google account ban under Antigravity's TOS restricting 3rd-party usage, and users discovered unofficial vs official extensions causing confusion (comm-17, comm-18). Missing for 10: an official partner/marketplace program for third-party agent apps, clear TOS allowance for such integrations, and independent confirmation that such integrations work without account risk.

   • [claimed-docs] “Layer custom Python callables, Model Context Protocol (MCP) servers, and reusable agent skills over our built-in filesystem and terminal too…”
   • [claimed-docs] “Plugins are namespaced bundles that allow you to extend Antigravity’s capabilities by grouping skills, rules, MCP servers, and hooks into a …”
   • [claimed-docs] “Access plugins, MCP, skills, and hooks configurations instantly via slash commands, quickly enhancing your workflow.”
   • [community] “Google Antigravity TOS: 3rd party usage can get Google account suspended. My friend got a ban by using Pi agent with Antigravity. They un-ba…”
   • [community] “The VSCode Antigravity extension I was using turns out to be a 3rd-party one. I found out only today that there's an official extension too,…”

   proof ↗⚑ flag

Team knowledge

1. engineering-leadCreate a shared workspace from my docs and repos as a common source of truth for the team

   weight 1 · round drawn
   Gemini CLI—none0/10

   Gemini CLI offers per-project GEMINI.md context files and --include-directories for local context, but there is no evidence of a shared, centrally managed team workspace combining docs and repos as a common source of truth across a team.

   • [github] “Custom context files (GEMINI.md) to tailor behavior for your projects”
   • [github] “gemini --include-directories ../lib,../docs”
   • [community] “Tip 1, it consistently ignores my GEMINI.md file, both global and local, even though it always says '1 GEMINI.md file is being used.'”

   proof ↗⚑ flag

   Google Antigravity—none0/10

   Antigravity's 'Projects' concept groups folders/repos for a single agent session's context (docs-5, docs-17, docs-35, docs-38) and can surface Docs/Drive links (docs-32), but there is no evidence of a multi-user, team-shared workspace or collaborative source-of-truth that an engineering-lead could set up for a whole team — Projects appear to be individually scoped, local constructs rather than shared team assets.

   • [claimed-docs] “Group your conversations into Projects, which can span multiple folders and support custom settings and scoped permissions.”
   • [claimed-docs] “a project can work with one folder or multiple folders (e.g., a frontend and a backend repo), providing your agents with all of the context …”
   • [claimed-docs] “Agents work within Projects, which define the boundaries of the folders and repositories they can access.”
   • [claimed-docs] “Worktree support: Projects natively support Git worktrees, allowing agents to operate in isolated background folders.”
   • [claimed-docs] “External files such as Google Drive links, PDFs, and Office documents now appear in their own Documents section in the sidebar above Artifac…”

   proof ↗⚑ flag

Tool integration

1. developerConnect the agent to workflow tools like Jira, Slack, and Google Drive to extend its context

   weight 3 · round drawn
   Gemini CLI~partialclaimed5/10

   Gemini CLI supports connecting MCP servers to add custom tools/capabilities (gh-5, gh-19), which is the generic mechanism that could extend context to third-party services, but the evidence never mentions Jira, Slack, or Google Drive specifically or any pre-built connectors for them. Missing for 10: named/official Jira, Slack, or Google Drive integrations or MCP servers, and any documented example of using these workflow tools with Gemini CLI.

   • [github] “Use MCP servers to connect new capabilities, including media generation with Imagen, Veo or Lyria”
   • [github] “Configure MCP servers in ~/.gemini/settings.json to extend Gemini CLI with custom tools”

   proof ↗⚑ flag

   Google Antigravity~partialclaimed5/10

   Antigravity documents generic MCP support for connecting to 'local developer tools, databases, file parsers, and external remote APIs' and explicitly shows Google Drive links/files appearing in its sidebar Documents section, giving a plausible path to hook in workflow tools. However, there is no explicit documentation of Jira or Slack connectors/integrations, and no first-party or community evidence of anyone actually wiring these specific tools in via MCP. Missing for 10: explicit Jira/Slack connector docs or MCP server examples, and independent confirmation of successful workflow-tool integrations beyond Drive.

   • [claimed-docs] “MCP lets Antigravity fetch structured context directly or execute safe actions on your behalf when needed.”
   • [claimed-docs] “lets AI agents and editors securely connect to local developer tools, databases, file parsers, and external remote APIs”
   • [claimed-docs] “External files such as Google Drive links, PDFs, and Office documents now appear in their own Documents section in the sidebar above Artifac…”
   • [claimed-docs] “Layer custom Python callables, Model Context Protocol (MCP) servers, and reusable agent skills over our built-in filesystem and terminal too…”

   proof ↗⚑ flag

2. developerKick off agent tasks directly from GitHub, GitLab, Linear, or Slack

   weight 2 · round to Gemini CLI
   Gemini CLI~partialclaimed4/10

   Gemini CLI has a documented GitHub integration (GitHub Action/App) that lets developers trigger tasks via @gemini-cli mentions in issues/PRs, automated PR reviews, and issue triage, but there is no evidence of native GitLab, Linear, or Slack integrations for kicking off agent tasks. missing for 10: GitLab integration, Linear integration, Slack integration, independent corroboration of GitHub workflow reliability

   • [github] “Pull Request Reviews: Automated code review with contextual feedback and suggestions”
   • [github] “Issue Triage: Automated labeling and prioritization of GitHub issues based on content analysis”
   • [github] “On-demand Assistance: Mention @gemini-cli in issues and pull requests for help with debugging, explanations, or task delegation”
   • [github] “On-demand Assistance: Mention `@gemini-cli` in issues and pull requests for help with debugging, explanations, or task delegation”
   • [github] “@github List my open pull requests”
   • [github] “Mention @gemini-cli in issues and pull requests for help with debugging, explanations, or task delegation”

   proof ↗⚑ flag

   Google Antigravity—none0/10

   No evidence that Antigravity supports kicking off agent tasks from GitHub, GitLab, Linear, or Slack; documentation covers IDE, CLI, SDK, scheduled tasks, and MCP but no mention of triggers from these external issue-tracker/chat platforms.

   ⚑ flag

Cross device continuity

1. developerStart a task on one device and continue it later from another device or browser

   weight 2 · round to Google Antigravity
   Gemini CLI—none0/10

   Gemini CLI offers local conversation checkpointing to save/resume sessions (gh-8) and can run in Cloud Shell (docs-1), but there is no evidence of cloud-synced session state that lets a developer start a task on one device/terminal and pick it up seamlessly on another device or browser. missing for 10: cross-device session sync, browser-based continuation of an existing CLI session, any documented mechanism to transfer checkpoint state between machines.

   • [github] “Conversation checkpointing to save and resume complex sessions”
   • [claimed-docs] “The Gemini CLI is available without additional setup in Cloud Shell”

   proof ↗⚑ flag

   Google Antigravity✓fullclaimed7/10

   Antigravity Remote Control explicitly lets users securely connect to and drive their desktop Antigravity sessions from any web browser, directly enabling continuing a task started on one device from another device/browser, and scheduled/background tasks further support async continuation across sessions. Missing for 10: independent hands-on verification of cross-device continuity, details on session/state sync fidelity, and any community confirmation of this specific feature working in practice.

   • [claimed-docs] “Antigravity Remote Control allows you to securely connect to and drive your Antigravity 2.0 desktop sessions running across your machines fr…”
   • [claimed-docs] “users can schedule messages to be sent to their agents while they’re away”
   • [claimed-docs] “Antigravity 2.0 serves as your AI agents’ central command center, providing a unified platform to launch, monitor, and orchestrate their act…”

   proof ↗⚑ flag

Ide integration

1. developerView interactive diffs and share selected code as context from within my JetBrains IDE

   weight 1 · round drawn
   Gemini CLI—none0/10

   No evidence mentions JetBrains IDE integration, interactive diffs, or sharing code context from within an IDE for Gemini CLI; evidence pack only covers terminal/CLI usage, GitHub Actions, and MCP servers.

   ⚑ flag

   Google Antigravity—none0/10

   Antigravity is documented as a standalone VSCode-fork IDE with its own Editor view, Artifacts diff viewer, and CLI/SDK — there is no mention anywhere in the docs, changelog, or community threads of a JetBrains plugin or JetBrains-specific integration for diffs or context sharing.

   • [claimed-docs] “Google Antigravity's Editor view offers tab autocompletion, natural language code commands, and a configurable, and context-aware configurab…”
   • [claimed-docs] “Artifacts include rich markdown plans (Implementation Plans), code diffs, architecture diagrams, images, and browser recordings.”
   • [claimed-docs] “Added a "Hide Whitespace Changes" option to the Review Changes overflow menu and file diff viewers to filter out whitespace-only edits.”
   • [claimed-docs] “Code and data artifacts like SQL and JSONL files now open in a virtualized viewer with syntax highlighting and line numbers”
   • [community] “I went ahead and downloaded it, it looks to be a VSCode fork very similar to Cursor, with support for Gemini 3 Pro, Claude Sonnet 4.5, and G…”

   proof ↗⚑ flag

2. developerChat with the coding assistant directly inside my IDE for contextual help

   weight 3 · round to Google Antigravity
   Gemini CLI—none0/10

   The evidence pack describes Gemini CLI as a terminal-based agent (context files, MCP servers, Cloud Shell access) but contains no mention of an IDE extension, sidebar chat, or in-editor contextual panel that would let a developer chat with it directly inside an IDE. Community threads discuss its terminal/agentic performance, not IDE integration.

   ⚑ flag

   Google Antigravity✓fullcommunity7/10

   Antigravity is a VSCode-fork IDE with an editor view offering tab autocompletion, natural language code commands, and a context-aware conversational agent, confirmed by community hands-on reports of using it like Cursor. This directly supports in-IDE chat for contextual help. missing for 10: independent review specifically praising chat UX/quality (community notes mixed quality/performance complaints), and no detailed walkthrough of the chat interface itself beyond high-level docs.

   • [claimed-docs] “Google Antigravity's Editor view offers tab autocompletion, natural language code commands, and a configurable, and context-aware configurab…”
   • [claimed-docs] “offers tab autocompletion, natural language code commands, and a configurable, and context-aware configurable agent”
   • [community] “I went ahead and downloaded it, it looks to be a VSCode fork very similar to Cursor, with support for Gemini 3 Pro, Claude Sonnet 4.5, and G…”
   • [claimed-docs] “Users can select which reasoning model they want to use within the model selector drop-down under the conversation prompt box”

   proof ↗⚑ flag

Session management

1. engineering-leadManage multiple agent-driven coding sessions from one unified workspace

   weight 2 · round to Google Antigravity
   Gemini CLI—none0/10

   Evidence shows single-session features (conversation checkpointing to save/resume one session, GEGEMINI.md context files) but nothing about running or coordinating multiple concurrent agent sessions from one unified dashboard/workspace for a lead overseeing a team's work. missing for 10: multi-session dashboard/orchestration UI, evidence of concurrent session management, any lead-oriented workspace view.

   • [github] “Conversation checkpointing to save and resume complex sessions”
   • [github] “Custom context files (GEMINI.md) to tailor behavior for your projects”

   proof ↗⚑ flag

   Google Antigravity✓fullcommunity8/10

   Antigravity's docs describe a unified 'command center' (antigravity-docs-37) that lets a lead orchestrate multiple autonomous agents in parallel across projects (antigravity-docs-1, antigravity-docs-10), grouped into Projects spanning folders/repos with scoped permissions (antigravity-docs-5, antigravity-docs-17, antigravity-docs-35), plus worktree isolation (antigravity-docs-38), scheduled/background tasks (antigravity-docs-2, antigravity-docs-39), subagent delegation (antigravity-docs-18/19), and even remote browser-based control of running sessions (antigravity-docs-26). This directly matches the engineering-lead's need to manage many concurrent agent sessions from one place. Missing for 10: independent verification of managing many simultaneous sessions at scale, and community reports note real stability/reliability issues (antigravity-comm-6, antigravity-comm-8, antigravity-comm-9) that temper confidence though they don't specifically contradict the multi-session orchestration claim.

   • [claimed-docs] “Antigravity 2.0 serves as your AI agents’ central command center, providing a unified platform to launch, monitor, and orchestrate their act…”
   • [claimed-docs] “Orchestrate multiple autonomous agents working in parallel across independent projects.”
   • [claimed-docs] “Have multiple agents working in parallel, so larger tasks get tackled faster.”
   • [claimed-docs] “Group your conversations into Projects, which can span multiple folders and support custom settings and scoped permissions.”
   • [claimed-docs] “a project can work with one folder or multiple folders (e.g., a frontend and a backend repo), providing your agents with all of the context …”
   • [claimed-docs] “Worktree support: Projects natively support Git worktrees, allowing agents to operate in isolated background folders.”
   • [claimed-docs] “Automate routine checks with Scheduled Tasks, simply define a cron schedule and the agents start and run autonomously in the background.”
   • [claimed-docs] “Antigravity Remote Control allows you to securely connect to and drive your Antigravity 2.0 desktop sessions running across your machines fr…”
   • [community] “Google made its lack of interest in Antigravity IDE obvious from very early. Updates were few and far between and app-breaking bugs stuck ar…”
   • [community] “It's not even good, honestly. I was using it for couple weeks before dropping that 2 months ago. The model was not good and slow, the harnes…”

   proof ↗⚑ flag

Terminal workflow

1. developerRun a coding agent locally from my terminal

   weight 3 · round drawn
   Gemini CLI✓fullcommunity8/10

   Gemini CLI is a terminal-native coding agent with first-party docs (gemini-cli-gh-1 through -20, gemini-cli-docs-1/2/3) describing running locally, querying/editing codebases, non-interactive scripting, and Cloud Shell availability with no extra setup, and abundant community evidence (gemini-cli-comm-1, -9, -12) confirms real-world local terminal usage. Missing for 10: independent benchmark of reliability (several community reports of agentic failures/loops, e.g. gemini-cli-comm-10, -11, -14) and no first-party install/runtime docs beyond GitHub README excerpts.

   • [github] “Query and edit large codebases”
   • [github] “Run non-interactively in scripts for workflow automation”
   • [github] “gemini --include-directories ../lib,../docs”
   • [claimed-docs] “The Gemini CLI is available without additional setup in Cloud Shell”
   • [community] “I have been using this for about a month and it's a beast, mostly thanks to 2.5pro being SOTA and how it leverages that huge 1M context wind…”
   • [community] “The correct way of using Gemini CLI is: ABUSE IT! With 1M Context Window (soon 2M) and generous daily free quota are huge advantages.”

   proof ↗⚑ flag

   Google Antigravity✓fullprobed8/10

   Google Antigravity ships an official CLI product (antigravity-cli) with terminal-native features like slash commands, headless/non-interactive mode for scripting, sandboxing, vim-mode editing, and config management, explicitly designed to run agents locally from the terminal, and a community comment confirms using 'Antigravity CLI with vscode' works fine. Missing for 10: deeper independent hands-on reviews specifically of the CLI (most community feedback focuses on the IDE, not the terminal tool) and no third-party benchmarks of terminal performance/reliability.

   • [claimed-docs] “Edit, orchestrate, and build all in natural language. Tell your agents what you need, and they’ll work on getting it done.”
   • [claimed-docs] “Have multiple agents working in parallel, so larger tasks get tackled faster.”
   • [claimed-docs] “Navigate your entire workflow via standard terminal shortcuts: adjust permissions, themes, and preferences via /config and type /keybindings…”
   • [claimed-docs] “Access plugins, MCP, skills, and hooks configurations instantly via slash commands, quickly enhancing your workflow.”
   • [claimed-docs] “Run Antigravity CLI non-interactively to script agent tasks, integrate with CI pipelines, and capture machine-readable output.”
   • [claimed-docs] “Sensitive files like ~/.ssh and .env are blocked, anything not explicitly mounted is invisible inside the sandbox”
   • [claimed-docs] “Vim editor mode replaces the editing model in every multi-line input surface of the CLI”
   • [probe] “official CLI documented at https://antigravity.google/product/antigravity-cli”
   • [community] “I much prefer using Gemini CLI in combination with vscode. It works like a charm. Now, I'll do the same with Antigravity CLI and vscode. It …”

   proof ↗⚑ flag

2. developerRun the agent non-interactively in scripts for workflow automation

   weight 2 · round to Gemini CLI
   Gemini CLI✓fullclaimed9/10

   Gemini CLI explicitly documents non-interactive scripting support with structured output flags (--output-format json / stream-json) and lists 'Run non-interactively in scripts for workflow automation' as a core feature; GitHub Actions integration for PR review/issue triage further evidences automation use cases. Missing for 10: independent hands-on validation specifically of scripting/automation workflows (community feedback focuses on interactive agent quality, not scripted use).

   • [github] “Run non-interactively in scripts for workflow automation”
   • [github] “use the `--output-format json` flag to get structured output”
   • [github] “use `--output-format stream-json` to get newline-delimited JSON events”
   • [github] “Pull Request Reviews: Automated code review with contextual feedback and suggestions”
   • [github] “Issue Triage: Automated labeling and prioritization of GitHub issues based on content analysis”

   proof ↗⚑ flag

   Google Antigravity✓fullclaimed7/10

   Official docs explicitly describe a headless mode: 'Run Antigravity CLI non-interactively to script agent tasks, integrate with CI pipelines, and capture machine-readable output,' directly matching the workflow-automation story. Missing for 10: independent/hands-on confirmation of headless CI usage and details on machine-readable output format/exit codes.

   • [claimed-docs] “Run Antigravity CLI non-interactively to script agent tasks, integrate with CI pipelines, and capture machine-readable output.”
   • [claimed-docs] “Edit, orchestrate, and build all in natural language. Tell your agents what you need, and they’ll work on getting it done.”
   • [claimed-docs] “Create or download fully customizable skills to further your agent’s autonomy and transform how you get work done.”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Gemini CLI
   Gemini CLI~partialprobed5/10

   Gemini CLI supports non-interactive scripting and structured JSON/stream-JSON output (gh-6, gh-17, gh-18), suggesting most interactive capabilities can be invoked programmatically for automation. However, there's no explicit documentation confirming full feature parity between interactive sessions and scripted/API use, and probes found no formal API/OpenAPI spec (probe-1, probe-2), so completeness of parity is unverified. Missing for 10: explicit parity documentation, a formal API surface beyond CLI flags, and independent confirmation that all UI/interactive features (e.g., checkpointing, MCP tool use) are scriptable identically.

   • [github] “Run non-interactively in scripts for workflow automation”
   • [github] “use the `--output-format json` flag to get structured output”
   • [github] “use `--output-format stream-json` to get newline-delimited JSON events”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.google.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.google.com/openapi.json, https://developers.google.com/swagger.json, https://deve…”

   proof ↗⚑ flag

   Google Antigravity~partialprobed4/10

   Antigravity offers an Agent SDK (Python programmable) and a headless/non-interactive CLI mode for scripting agent tasks, plugins, MCP, and hooks, suggesting substantial programmatic access to agent capabilities. However, there is no documented public REST/HTTP API or OpenAPI spec (probe explicitly found all openapi.json candidate paths 404'd), and no evidence that UI-only features like Remote Control, Editor tab-autocompletion, artifact review UI, or scheduled task UI are fully exposed via API parity. missing for 10: a documented public API/OpenAPI spec, confirmation that all UI features (remote control, artifact review, scheduling UI) have API equivalents, and independent verification of API-UI parity.

   • [claimed-docs] “The Agent SDK gives you the same tools, agent loop, and context management that power Google Antigravity, programmable in Python.”
   • [claimed-docs] “Run Antigravity CLI non-interactively to script agent tasks, integrate with CI pipelines, and capture machine-readable output.”
   • [claimed-docs] “Layer custom Python callables, Model Context Protocol (MCP) servers, and reusable agent skills over our built-in filesystem and terminal too…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://antigravity.google/openapi.json, https://antigravity.google/swagger.json, https://antigravit…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round drawn
   Gemini CLI—none0/10

   No evidence of any data export feature or open-format data portability in Gemini CLI; the tool is a local coding agent that reads/writes local files but nothing indicates exporting conversation history, settings, or usage data in an open format for user-controlled exit. Probes for llms.txt/openapi also failed, showing no structured data-access surface.

   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.google.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.google.com/openapi.json, https://developers.google.com/swagger.json, https://deve…”

   proof ↗⚑ flag

   Google Antigravity—none0/10

   No evidence in the pack mentions data export, open-format portability, or account/data deletion features for Antigravity; docs cover projects, agents, artifacts, and CLI but never data portability or export-and-leave capability.

   ⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round to Gemini CLI
   Gemini CLI~partialprobed5/10

   The product's source is hosted publicly at github.com/google-gemini/gemini-cli (referenced repeatedly across the evidence pack), implying open availability for reading, but no citation in the evidence pack explicitly names or confirms an open-source license (e.g., Apache/MIT) or points to a LICENSE file. Missing for 10: explicit license text/citation, confirmation of license type, and any independent corroboration of open-license terms.

   • [github] “Query and edit large codebases”
   • [github] “Use `/bug` command to report issues directly from the CLI.”
   • [probe] “official CLI documented at https://developers.google.com/gemini-code-assist/docs/gemini-cli”

   proof ↗⚑ flag

   Google Antigravity—none0/10

   No evidence of any open-source license or public source repository for Antigravity; it appears closed-source (VSCode fork distributed as binary download, third-party unofficial extensions noted). Nothing in the docs or community reports references source availability or a license.

   ⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   Gemini CLI—none0/10

   Gemini CLI is an open-source client, but the core product (the Gemini models/backend) is a Google-hosted cloud service accessed via Google account sign-in; no evidence anywhere in the pack describes a self-hosted or on-prem deployment option for the core model/service.

   • [github] “No API key management - just sign in with your Google account”
   • [claimed-docs] “The Gemini CLI is available without additional setup in Cloud Shell”

   proof ↗⚑ flag

   Google Antigravity—none0/10

   No evidence anywhere in the pack indicates Antigravity can be self-hosted; it is described only as a downloadable desktop app/IDE/CLI/SDK connecting to Google's cloud-hosted models, with account/entitlement gating and TOS restrictions mentioned in community reports, but no self-hosted server or on-prem deployment option is documented.

   • [claimed-docs] “Visit antigravity.google/download to download Google Antigravity 2.0. Select your operating system below”
   • [claimed-docs] “Antigravity 2.0 serves as your AI agents’ central command center, providing a unified platform to launch, monitor, and orchestrate their act…”
   • [community] “don't buy Google AI subscription before you confirm you have 'Antigravity entitlement'... You can have verified account, bank card added, ac…”
   • [community] “Google Antigravity TOS: 3rd party usage can get Google account suspended. My friend got a ban by using Pi agent with Antigravity. They un-ba…”

   proof ↗⚑ flag

Authentication

1. developerAuthenticate with an API key instead of an account login

   weight 2 · round to Gemini CLI
   Gemini CLI~partialclaimed4/10

   The docs emphasize signing in with a Google account (gh-13) as the primary flow, but they also note that developers needing 'specific model control or paid tier access' (gh-24) have an alternative path, implying API-key-based auth exists without detailing it. There's no explicit example or setup instructions for API-key authentication itself. Missing for 10: explicit API key env-var/config documentation, first-party steps for key-based auth, and independent confirmation it works without Google login.

   • [github] “No API key management - just sign in with your Google account”
   • [github] “Developers who need specific model control or paid tier access”

   proof ↗⚑ flag

   Google Antigravity—none0/10

   Evidence shows Antigravity requires a Google account/login and even ties usage to 'Antigravity entitlement' on that account (comm-19), with account-level bans possible (comm-17, comm-20); no docs or CLI reference mention an API-key authentication mode as an alternative to account login.

   • [community] “Google Antigravity TOS: 3rd party usage can get Google account suspended. My friend got a ban by using Pi agent with Antigravity. They un-ba…”
   • [community] “don't buy Google AI subscription before you confirm you have 'Antigravity entitlement'... You can have verified account, bank card added, ac…”
   • [community] “Banning the entire account rather than AI access is wildly user hostile... And then you get to fight the support bots and eventually go to t…”

   proof ↗⚑ flag

2. engineering-leadAuthenticate through an enterprise identity or cloud platform for compliance and scalability

   weight 2 · round to Gemini CLI
   Gemini CLI!disputedcontradicted4/10

   Google claims 'Enterprise features: Advanced security and compliance' and frictionless Google-account sign-in without API key management, plus Cloud Shell availability, suggesting cloud/enterprise identity support. However, a hands-on community report shows authentication explicitly failing for Workspace (enterprise) accounts ('Failed to login. Ensure your Google account is not a Workspace account'), directly contradicting the enterprise-identity claim for a core scenario. Missing for 10: documented enterprise SSO/IAM integration details, confirmation Workspace login issue is resolved, and independent verification of compliance certifications.

   • [github] “No API key management - just sign in with your Google account”
   • [github] “Enterprise features: Advanced security and compliance”
   • [claimed-docs] “The Gemini CLI is available without additional setup in Cloud Shell”
   • [community] “'Failed to login. Ensure your Google account is not a Workspace account.' I have had a Workspace account since GSuite and now as a Workspace…”

   proof ↗⚑ flag

   Google Antigravity—none0/10

   No evidence of SSO/SAML/OIDC, Google Workspace/Cloud IAM enterprise login, or any enterprise identity federation for Antigravity; docs mention only Google account sign-in and entitlement issues, with community reports of account suspensions rather than enterprise auth support. Missing for 10: SSO/SAML/OIDC support, Google Cloud IAM or Workspace admin console integration, enterprise provisioning/SCIM documentation.

   • [community] “don't buy Google AI subscription before you confirm you have 'Antigravity entitlement'... You can have verified account, bank card added, ac…”
   • [community] “Banning the entire account rather than AI access is wildly user hostile... And then you get to fight the support bots and eventually go to t…”

   proof ↗⚑ flag

3. developerSign in with my existing product subscription plan to use the coding agent

   weight 2 · round to Gemini CLI
   Gemini CLI!disputedcontradicted4/10

   Gemini CLI advertises frictionless Google-account sign-in with no API key management (gh-13), suggesting subscribers could just log in and go, but hands-on community reports concretely contradict this: a Gemini Pro subscriber found that paying for 'Gemini' doesn't unlock Gemini CLI usage, requiring a separate 'Gemini Code Assist Standard/Enterprise' plan, and another user explicitly asks for one unified subscription across CLI, Code Assist, Jules, etc. like Claude's Max plan. Missing for 10: evidence that an existing Google One/Gemini Advanced subscription actually raises CLI usage limits, and resolution of the reported subscription fragmentation.

   • [github] “No API key management - just sign in with your Google account”
   • [community] “I love how fragmented Google's Gemini offerings are. I'm a Pro subscriber but I learn I should be a 'Gemini Code Assist Standard or Enterpri…”
   • [community] “Again, with the complicated subscription. Please just give us a monthly subscription for developers that I can pay whatever, and then use Ge…”
   • [github] “Developers who need specific model control or paid tier access”

   proof ↗⚑ flag

   Google Antigravity—none0/10

   No documentation describes signing in with an existing Google AI/Gemini subscription plan to unlock Antigravity access, and community reports directly state that users with an active AI Pro subscription still could not use even the free tier without a separate 'Antigravity entitlement.' missing for 10: any first-party docs describing subscription-based sign-in, evidence of successful subscription-linked access, and confirmation that paid Google AI plans map directly to Antigravity usage.

   • [community] “don't buy Google AI subscription before you confirm you have 'Antigravity entitlement'... You can have verified account, bank card added, ac…”
   • [community] “Google Antigravity TOS: 3rd party usage can get Google account suspended. My friend got a ban by using Pi agent with Antigravity. They un-ba…”
   • [community] “On the pricing page it says free individual plan with 'generous rate limits'. I gave it an HTML file and 2 minutes later got: 'Model quota l…”

   proof ↗⚑ flag

4. developerSign in with a personal account to get free-tier access without managing API keys

   weight 1 · round to Gemini CLI
   Gemini CLI✓fullcommunity7/10

   GitHub docs explicitly state 'No API key management - just sign in with your Google account' (gemini-cli-gh-13), directly matching the story, and Cloud Shell docs describe zero-setup access. Community reports don't dispute personal-account sign-in itself (the failure noted is specific to Workspace accounts, an edge case outside 'personal account'), though some users voice confusion over how free vs paid tiers interact. Missing for 10: independent/hands-on confirmation of the free-tier quota limits and clearer documentation distinguishing personal free-tier access from paid Code Assist tiers.

   • [github] “No API key management - just sign in with your Google account”
   • [claimed-docs] “The Gemini CLI is available without additional setup in Cloud Shell”
   • [community] “I love how fragmented Google's Gemini offerings are. I'm a Pro subscriber but I learn I should be a 'Gemini Code Assist Standard or Enterpri…”
   • [community] “'Failed to login. Ensure your Google account is not a Workspace account.' I have had a Workspace account since GSuite and now as a Workspace…”

   proof ↗⚑ flag

   Google Antigravity!disputedcontradicted3/10

   Vendor pages advertise a free individual plan with no mention of API key management, implying sign-in-with-personal-account access, but community hands-on reports directly contradict the free-tier promise — one user got a 'Model quota limit exceeded' error within minutes despite the 'generous rate limits' claim, and another describes being locked out of even the free tier due to an 'Antigravity entitlement' gate despite having an active subscription. missing for 10: first-party documentation explicitly describing the personal-account sign-in flow and free-tier terms, and independent confirmation that free-tier access works reliably without unexpected quota/entitlement blocks.

   • [community] “On the pricing page it says free individual plan with 'generous rate limits'. I gave it an HTML file and 2 minutes later got: 'Model quota l…”
   • [community] “don't buy Google AI subscription before you confirm you have 'Antigravity entitlement'... You can have verified account, bank card added, ac…”
   • [claimed-docs] “Visit antigravity.google/download to download Google Antigravity 2.0. Select your operating system below”

   proof ↗⚑ flag

Model choice

1. developerLet the tool automatically pick the best model for each task

   weight 1 · round drawn
   Gemini CLI—none0/10

   Evidence shows manual model selection ('Choose specific Gemini models' for 'developers who need specific model control') rather than automatic task-based model selection; no evidence of the CLI auto-choosing the optimal model per task.

   • [github] “Model selection: Choose specific Gemini models”
   • [github] “Developers who need specific model control or paid tier access”

   proof ↗⚑ flag

   Google Antigravity—none0/10

   Docs describe a manual model selector dropdown where users choose the reasoning model themselves (antigravity-docs-16), not an automatic 'best model per task' selection mechanism; no evidence anywhere of automatic model routing or task-based model optimization.

   • [claimed-docs] “Users can select which reasoning model they want to use within the model selector drop-down under the conversation prompt box”

   proof ↗⚑ flag

2. developerChoose which underlying AI model powers my session from multiple providers

   weight 2 · round to Google Antigravity
   Gemini CLI—none0/10

   Evidence shows Gemini CLI only supports choosing among Google's own Gemini models (gh-14, gh-24), not switching between different AI providers (e.g., OpenAI, Anthropic); community complaints (comm-2, comm-3, comm-19) reinforce that it's locked to Google's ecosystem/billing. There is no evidence of multi-provider model selection, so the story as written (choosing from multiple providers) is not delivered.

   • [github] “Model selection: Choose specific Gemini models”
   • [github] “Developers who need specific model control or paid tier access”
   • [community] “The killer feature of Claude Code is that you can just pay for Max and not worry about API billing. Until Gemini does that, I'm sticking wit…”
   • [community] “I love how fragmented Google's Gemini offerings are. I'm a Pro subscriber but I learn I should be a 'Gemini Code Assist Standard or Enterpri…”
   • [community] “Again, with the complicated subscription. Please just give us a monthly subscription for developers that I can pay whatever, and then use Ge…”

   proof ↗⚑ flag

   Google Antigravity✓fullcommunity8/10

   Docs explicitly describe a model selector dropdown for choosing reasoning models, and community hands-on evidence confirms multiple providers (Gemini 3 Pro, Claude Sonnet 4.5, GPT-OSS 120B) are selectable, not locked to Gemini only. Missing for 10: pricing/tier restrictions per model and independent benchmarking of model-switching quality across providers.

   • [claimed-docs] “Users can select which reasoning model they want to use within the model selector drop-down under the conversation prompt box”
   • [community] “I went ahead and downloaded it, it looks to be a VSCode fork very similar to Cursor, with support for Gemini 3 Pro, Claude Sonnet 4.5, and G…”
   • [community] “Nice to see that it's not locked to just Gemini models.”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Gemini CLI—none0/10

   No evidence in the pack mentions data residency, regional storage options, or configurable data location controls for Gemini CLI; only enterprise 'security and compliance' features are mentioned generically without specifics.

   ⚑ flag

   Google Antigravity—none0/10

   No evidence pack item mentions data residency, region selection, or storage location controls; only a telemetry on/off toggle is documented, which does not address data residency. Missing for 10: any documentation of regional data storage options, residency guarantees, or enterprise data-location controls.

   ⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round to Google Antigravity
   Gemini CLI—none0/10

   No evidence in the pack addresses data usage/training opt-out policies, privacy controls, or terms governing whether user data trains Google's models; only unrelated feature/community commentary is present. Missing for 10: explicit data-usage/training policy documentation, opt-out mechanism, enterprise/no-training guarantee.

   ⚑ flag

   Google Antigravity~partialclaimed5/10

   Antigravity's settings docs mention a Telemetry toggle to enable/disable sharing interaction logs 'to improve models,' which is the only evidence addressing training-data opt-out; there's no further detail on scope, default state, or enterprise data-processing guarantees. Missing for 10: independent verification the toggle actually excludes data from training, clarity on default setting, and any enterprise/DPA-level documentation of data usage.

   • [claimed-docs] “toggle Telemetry (enable/disable sharing interaction logs to improve models)”

   proof ↗⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Google Antigravity
   Gemini CLI—none0/10

   No evidence pack items address data retention controls, deletion mechanisms, or privacy settings for Gemini CLI; only enterprise 'security and compliance' is vaguely mentioned without specifics. Missing for 10: documentation on data retention policy, user-controlled deletion mechanism, opt-out of data collection, and any privacy settings UI/CLI flags.

   ⚑ flag

   Google Antigravity~partialclaimed3/10

   Docs mention a Telemetry toggle to enable/disable sharing interaction logs, which is a privacy-related control, but there is no documented mechanism for viewing, exporting, or deleting stored data/history, nor any stated retention policy. Missing for 10: explicit data deletion controls, data export/retention policy documentation, and independent confirmation these settings work as described.

   • [claimed-docs] “toggle Telemetry (enable/disable sharing interaction logs to improve models)”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round to Google Antigravity
   Gemini CLI—none0/10

   No evidence in the pack mentions telemetry settings, opt-out flags, or usage-data collection policy for Gemini CLI. Missing for 10: any documentation of a telemetry/usage-tracking toggle, privacy settings, or opt-out mechanism.

   ⚑ flag

   Google Antigravity✓fullclaimed7/10

   Docs confirm a settings toggle to enable/disable telemetry ('sharing interaction logs to improve models'), giving users a direct opt-out. Missing for 10: independent/hands-on confirmation that the toggle fully stops all data collection, and no detail on what telemetry remains even when disabled.

   • [claimed-docs] “toggle Telemetry (enable/disable sharing interaction logs to improve models)”

   proof ↗⚑ flag

Data governance

1. engineering-leadOpt out of having my code and prompts used for AI model training

   weight 1 · round to Google Antigravity
   Gemini CLI—none0/10

   No evidence in the pack addresses data usage, training opt-out policies, or privacy controls for Gemini CLI; only feature lists and general community sentiment are present. missing for 10: any documentation of data usage/training policy, opt-out settings or enterprise privacy controls, and independent confirmation of such settings working.

   ⚑ flag

   Google Antigravity~partialclaimed5/10

   Docs mention a Telemetry toggle to 'enable/disable sharing interaction logs to improve models,' which functions as an opt-out from data being used for model improvement, but there is no explicit documentation framing this as a training opt-out for enterprise/engineering-lead governance needs (e.g., no data-processing agreement, no distinction between prompts/code vs telemetry, no enterprise admin-level control). Missing for 10: explicit statement that code/prompts are excluded from training, org-wide/admin-level enforcement of the opt-out, and independent confirmation the toggle actually stops training use.

   • [claimed-docs] “toggle Telemetry (enable/disable sharing interaction logs to improve models)”

   proof ↗⚑ flag

Pr review

1. developerHave the agent stage changes, write commit messages, create branches, and open pull requests

   weight 3 · round to Gemini CLI
   Gemini CLI~partialclaimed4/10

   Evidence shows Gemini CLI can automate git-related operational tasks like querying pull requests and handling complex rebases, and its GitHub Action can do automated PR reviews and issue triage, but there's no explicit documentation of the agent staging changes, writing commit messages, creating branches, or opening new pull requests itself. Missing for 10: explicit commit-message generation, branch creation, and PR-opening workflow evidence, plus independent confirmation these work reliably.

   • [github] “Automate operational tasks like querying pull requests or handling complex rebases”
   • [github] “Pull Request Reviews: Automated code review with contextual feedback and suggestions”
   • [github] “@github List my open pull requests”
   • [github] “On-demand Assistance: Mention @gemini-cli in issues and pull requests for help with debugging, explanations, or task delegation”

   proof ↗⚑ flag

   Google Antigravity~partialclaimed3/10

   Antigravity's agents can operate the terminal and natively support Git worktrees, which implies they could run git commands like staging, committing, and branching, but no documentation explicitly describes agent-driven commit message generation, branch creation, or PR opening (e.g., GitHub integration). Missing for 10: explicit docs on commit-message authoring, branch creation workflow, and pull-request creation/integration with GitHub/GitLab.

   • [claimed-docs] “Worktree support: Projects natively support Git worktrees, allowing agents to operate in isolated background folders.”
   • [claimed-docs] “Able to autonomously operate across your editor, terminal, and browser.”
   • [claimed-docs] “Build AI agents that autonomously read files, run commands, edit code, and more.”

   proof ↗⚑ flag

2. developerGet automatic code review with contextual feedback on every pull request

   weight 3 · round to Gemini CLI
   Gemini CLI✓fullcommunity8/10

   Gemini CLI's GitHub Actions integration explicitly provides automated PR code review with contextual feedback and suggestions, plus on-demand @gemini-cli assistance in PRs, and community reports corroborate favorable code review quality compared to competitors. Missing for 10: independent hands-on verification of the PR-review workflow specifically (most community feedback covers general CLI agentic use rather than the PR-review action itself), and no detail on configurability/false-positive rates.

   • [github] “Pull Request Reviews: Automated code review with contextual feedback and suggestions”
   • [github] “Issue Triage: Automated labeling and prioritization of GitHub issues based on content analysis”
   • [github] “On-demand Assistance: Mention @gemini-cli in issues and pull requests for help with debugging, explanations, or task delegation”
   • [github] “On-demand Assistance: Mention `@gemini-cli` in issues and pull requests for help with debugging, explanations, or task delegation”
   • [github] “@github List my open pull requests”
   • [community] “We have tried out Gemini code review vs Copilot code review and Gemini is consistently offering better code review tips. It has officially c…”

   proof ↗⚑ flag

   Google Antigravity—none0/10

   Antigravity offers in-editor 'Review Changes' diff viewing and Artifact-based plan review, but there is no evidence of a GitHub/GitLab pull-request bot or CI-integrated review that automatically posts contextual feedback on every PR. The CLI headless mode allows scripting into CI, but no docs describe an automated PR-review workflow.

   • [claimed-docs] “Planning Mode: The agent plans thoroughly before executing tasks... produces structured implementation plans called Artifacts”
   • [claimed-docs] “The agent always halts and requests your explicit approval before proceeding with proposed changes.”
   • [claimed-docs] “Added a "Hide Whitespace Changes" option to the Review Changes overflow menu and file diff viewers to filter out whitespace-only edits.”
   • [claimed-docs] “Run Antigravity CLI non-interactively to script agent tasks, integrate with CI pipelines, and capture machine-readable output.”

   proof ↗⚑ flag

3. developerInspect diffs and run checks to catch problems before merging

   weight 3 · round drawn
   Gemini CLI~partialcommunity6/10

   Gemini CLI supports GitHub PR review automation with contextual feedback (gemini-cli-gh-10) and issue triage, plus community reports confirm it catches bugs reviewers missed (gemini-cli-comm-20), supporting diff inspection and pre-merge checks. However, there's no dedicated diff-viewing UI or built-in test/lint-running check suite documented, and community reports raise concerns about reliability, security prompts, and agentic mistakes (gemini-cli-comm-14, gemini-cli-comm-17). missing for 10: dedicated diff-inspection UI/commands, built-in CI/test-running integration, and stronger independent corroboration of reliability for pre-merge checks.

   • [github] “Pull Request Reviews: Automated code review with contextual feedback and suggestions”
   • [github] “Issue Triage: Automated labeling and prioritization of GitHub issues based on content analysis”
   • [github] “Automate operational tasks like querying pull requests or handling complex rebases”
   • [community] “We have tried out Gemini code review vs Copilot code review and Gemini is consistently offering better code review tips. It has officially c…”
   • [community] “The problem is that Gemini CLI simply doesn't work. Beside simplest tasks like creating a new release it is useless as a coding assistant. D…”
   • [community] “However, it does seem that Gemini pays less attention to security than Claude Code. Gemini will happily open in my root directory. Claude Co…”

   proof ↗⚑ flag

   Google Antigravity~partialcommunity6/10

   Docs describe a Review Changes/diff viewer (with whitespace filtering, syntax highlighting) and Artifacts containing code diffs, plus mandatory human approval before changes are applied, and subagents/CI headless mode that can run tests. This covers diff inspection and pre-merge gating, but there's no dedicated 'run checks' feature (e.g., integrated linting/test-run summary) beyond subagent test delegation, and no independent hands-on confirmation that this workflow reliably catches problems — community reports instead highlight safety failures (accidental deletion, data exfiltration) that occurred despite review/approval mechanisms. Missing for 10: independent verification that diff review + checks actually catch bugs pre-merge, and a dedicated automated check/test-report feature beyond ad-hoc subagent delegation.

   • [claimed-docs] “Planning Mode: The agent plans thoroughly before executing tasks... produces structured implementation plans called Artifacts”
   • [claimed-docs] “The agent always halts and requests your explicit approval before proceeding with proposed changes.”
   • [claimed-docs] “Artifacts include rich markdown plans (Implementation Plans), code diffs, architecture diagrams, images, and browser recordings.”
   • [claimed-docs] “Added a "Hide Whitespace Changes" option to the Review Changes overflow menu and file diff viewers to filter out whitespace-only edits.”
   • [claimed-docs] “Code and data artifacts like SQL and JSONL files now open in a virtualized viewer with syntax highlighting and line numbers”
   • [claimed-docs] “an agent can delegate tasks—such as running tests or performing extensive codebase searches—to dedicated subagents.”
   • [claimed-docs] “Run Antigravity CLI non-interactively to script agent tasks, integrate with CI pipelines, and capture machine-readable output.”
   • [community] “Google Antigravity just deleted the contents of whole drive - came down to commanding a deletion of a 'directory with space in the name' wit…”
   • [community] “absolutely no sympathy for someone running Antigravity in Turbo mode (this is not the default and it clearly states that Antigravity auto-ex…”

   proof ↗⚑ flag

Safe execution

1. engineering-leadControl which external tools and integrations the agent is allowed to access

   weight 2 · round to Gemini CLI
   Gemini CLI~partialcommunity5/10

   Gemini CLI supports configuring MCP servers via ~/.gemini/settings.json and exposes /tools and /mcp commands to inspect and manage available tools, giving engineering leads some control over which integrations are enabled. However, evidence lacks any centralized admin/policy control, allowlist/denylist enforcement, or org-wide governance mechanism for restricting tool access across a team, and community reports note weak security defaults (e.g. opening root directories without prompting). missing for 10: org-level/admin enforcement of tool allowlists, granular permission scoping per tool/integration, independent verification that access controls are robust rather than just configurable per-user.

   • [github] “Configure MCP servers in ~/.gemini/settings.json to extend Gemini CLI with custom tools”
   • [claimed-docs] “Comandos de Gemini CLI: /memory, /stats, /tools y /mcp”
   • [community] “However, it does seem that Gemini pays less attention to security than Claude Code. Gemini will happily open in my root directory. Claude Co…”

   proof ↗⚑ flag

   Google Antigravity!disputedcontradicted5/10

   Antigravity docs describe granular controls—Deny/Ask/Allow permission lists, MCP server configuration, plugins bundling MCP servers, and sandboxing that blocks sensitive files—giving engineering leads levers to restrict tool/integration access (antigravity-docs-23, antigravity-docs-42, antigravity-docs-12, antigravity-docs-28, antigravity-docs-48). However, independent security reports document that these controls were bypassed in practice: Gemini accessed .env files despite being configured not to, and the default Allowlist shipped with webhook.site, which was used as a live exfiltration vector—directly contradicting the claim that admins can reliably restrict external access (antigravity-comm-11, antigravity-comm-12, antigravity-comm-13). Missing for 10: evidence of a fix/patch to these bypasses, and no first-party acknowledgment/remediation documentation confirming the control now holds as designed.

   • [claimed-docs] “Permissions are evaluated across three distinct access lists: Deny... Ask... Allow”
   • [claimed-docs] “Permissions are evaluated across three distinct access lists: Deny...Ask...Allow”
   • [claimed-docs] “Access plugins, MCP, skills, and hooks configurations instantly via slash commands, quickly enhancing your workflow.”
   • [claimed-docs] “Plugins are namespaced bundles that allow you to extend Antigravity’s capabilities by grouping skills, rules, MCP servers, and hooks into a …”
   • [claimed-docs] “Sensitive files like ~/.ssh and .env are blocked, anything not explicitly mounted is invisible inside the sandbox”
   • [community] “Google Antigravity exfiltrates data via indirect prompt injection attack: Gemini is not supposed to have access to .env files with default s…”
   • [community] “The default Allowlist provided with Antigravity includes 'webhook.site', which was used as an exfiltration vector for secrets.”
   • [community] “Antigravity was also vulnerable to the classic Markdown image exfiltration bug, reported a few days prior and flagged as 'intended behavior'…”

   proof ↗⚑ flag

2. engineering-leadHave the agent operate inside a sandbox when interacting with code, tools, and network resources

   weight 2 · round to Google Antigravity
   Gemini CLI—none0/10

   The evidence pack contains no vendor documentation of a sandboxed execution mode for code/tool/network interactions—only a vague 'Enterprise features: Advanced security and compliance' bullet with no detail. Community evidence actually points the other way: reviewers note Gemini CLI 'happily opens in my root directory' without any directory-trust prompt, unlike Claude Code, and one report describes it destructively running file-system commands, suggesting a lack of sandboxing guardrails rather than presence of them.

   • [github] “Enterprise features: Advanced security and compliance”
   • [community] “However, it does seem that Gemini pays less attention to security than Claude Code. Gemini will happily open in my root directory. Claude Co…”
   • [community] “Gemini told the user: 'I have failed you completely and catastrophically... I have lost your data. This is an unacceptable, irreversible fai…”

   proof ↗⚑ flag

   Google Antigravity!disputedcontradicted4/10

   Antigravity CLI docs describe a real sandbox mechanism (sensitive files like ~/.ssh and .env blocked, unmounted paths invisible) plus a permission allow/ask/deny system, suggesting sandboxed tool/network access is a documented feature. However, independent reports concretely contradict this: Gemini bypassed its own .env protection to exfiltrate secrets via indirect prompt injection using an allow-listed exfiltration endpoint, a known markdown-image exfiltration bug was dismissed as 'intended behavior,' and unrestrained terminal auto-execution led to a user's entire drive being deleted — showing the sandbox/permission boundary is not reliably enforced in practice. Missing for 10: consistent enforcement of sandbox boundaries against prompt-injection/exfiltration, first-party acknowledgment/fix of these incidents, and independent verification that the CLI's stated sandbox extends to the IDE agent's file/network access.

   • [claimed-docs] “Sensitive files like ~/.ssh and .env are blocked, anything not explicitly mounted is invisible inside the sandbox”
   • [claimed-docs] “Permissions are evaluated across three distinct access lists: Deny... Ask... Allow”
   • [claimed-docs] “MCP lets Antigravity fetch structured context directly or execute safe actions on your behalf when needed.”
   • [community] “Google Antigravity exfiltrates data via indirect prompt injection attack: Gemini is not supposed to have access to .env files with default s…”
   • [community] “The default Allowlist provided with Antigravity includes 'webhook.site', which was used as an exfiltration vector for secrets.”
   • [community] “Antigravity was also vulnerable to the classic Markdown image exfiltration bug, reported a few days prior and flagged as 'intended behavior'…”
   • [community] “Google Antigravity just deleted the contents of whole drive - came down to commanding a deletion of a 'directory with space in the name' wit…”
   • [community] “The most useful suggestion from the Reddit thread: turn off 'Terminal Command Auto Execution' via File > Preferences > Antigravity Settings …”
   • [community] “absolutely no sympathy for someone running Antigravity in Turbo mode (this is not the default and it clearly states that Antigravity auto-ex…”

   proof ↗⚑ flag

Security checks

1. engineering-leadSee license and public-code matching references for AI-suggested code

   weight 1 · round drawn
   Gemini CLI—none0/10

   No evidence anywhere in the pack of license attribution, public-code matching, or provenance references for AI-suggested code; features listed cover code editing, review, MCP, PR automation, etc. but nothing about license/originality detection.

   ⚑ flag

   Google Antigravity—none0/10

   No evidence in the pack mentions license compliance checks, public-code/OSS matching, provenance detection, or any similar review-safety feature for AI-suggested code; the docs focus on agents, artifacts, permissions, and workflow tooling with no mention of license scanning.

   ⚑ flag

2. developerGet contextual explanations and automatic fixes for security vulnerabilities

   weight 2 · round to Gemini CLI
   Gemini CLI~partialclaimed4/10

   Gemini CLI offers general debugging/explanation via natural language (gh-3, gh-12) and automated PR review with 'contextual feedback and suggestions' (gh-10), plus vague 'enterprise advanced security and compliance' (gh-15), which could incidentally surface and explain security issues, but there is no evidence of a dedicated vulnerability-scanning or automatic-fix feature specifically for security flaws. Missing for 10: explicit vulnerability detection/scanning capability, documented automatic remediation of security issues, and independent verification that PR reviews catch/fix security vulnerabilities specifically.

   • [github] “Debug issues and troubleshoot with natural language”
   • [github] “Pull Request Reviews: Automated code review with contextual feedback and suggestions”
   • [github] “On-demand Assistance: Mention @gemini-cli in issues and pull requests for help with debugging, explanations, or task delegation”
   • [github] “Enterprise features: Advanced security and compliance”

   proof ↗⚑ flag

   Google Antigravity—none0/10

   No evidence that Antigravity provides security-vulnerability-specific explanations or automatic fixes; the docs describe general agentic coding, planning, and review features but never mention vulnerability scanning or security remediation. Community evidence instead highlights security *problems* in Antigravity itself (prompt injection exfiltration), not a vulnerability-fixing capability for users' code.

   ⚑ flag