Cline vs Google Antigravity

Agent access

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

   weight 2 · round to Google Antigravity
   Cline~partialprobed6/10

   Cline's own docs site publishes a working llms.txt (probe-confirmed HTTP 200) and Cline can browse the web and pull in external tools/data via MCP, implying a user could point the agent at llms.txt or similar agent-oriented docs for context. However, there is no explicit first-party documentation describing a workflow for feeding llms.txt or agent-oriented doc formats into Cline's context. Missing for 10: explicit documented feature/workflow for ingesting llms.txt as agent context, and independent confirmation of this specific use case.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.cline.bot/llms.txt # Cline > AI-powered coding agent for complex work - [Cline Overview](https://…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.cline.bot/cline-overview.md > ## Documentation Index > Fetch the complete documentation index at: ht…”
   • [claimed-docs] “AI coding assistant in your editor. Create files, run commands, browse the web, and use tools with human-in-the-loop approval.”
   • [claimed-docs] “MCP (Model Context Protocol) lets Cline use external tools and data sources through MCP servers.”

   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 Cline
   Cline✓fullclaimed9/10

   Cline ships a dedicated CLI with explicit headless/automation mode, auto-approve flags for unattended runs, pipeable I/O (git diff | cline), cron scheduling via hub, and documented CI/CD integration (GitHub Actions, GitLab pipelines). Multiple first-party docs corroborate this across CLI overview, scheduling, and marketing pages. Missing for 10: independent/community hands-on confirmation of CI usage specifically (community evidence covers general tool quality, not headless CI runs).

   • [claimed-docs] “Run Cline in your terminal with interactive chat or fully headless automation for CI/CD and scripting.”
   • [claimed-docs] “Use headless mode for scripts/automation and processable output.”
   • [claimed-docs] “Autonomous execution can modify files and run commands without further prompts.”
   • [claimed-docs] “Chat with the agent from Slack, Discord, Telegram, or Linear. Run it headlessly inside GitHub Actions, GitLab, or any pipeline.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [claimed-docs] “Use Cline CLI for interactive terminal sessions and automated headless workflows.”
   • [claimed-docs] “cline --auto-approve true "run tests and fix failures"”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [claimed-docs] “Run agents on cron schedules for recurring automations like daily summaries and code reviews.”

   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 to Cline
   Cline✓fullclaimed9/10

   Cline explicitly documents MCP support ('MCP lets Cline use external tools and data sources through MCP servers') and both the CLI/hub and GitHub docs reference managing MCP servers alongside models and plugins; auto-approve settings even list MCP tools as controllable. Missing for 10: independent hands-on verification of MCP server setup/usage beyond docs and GitHub blurb.

   • [claimed-docs] “MCP (Model Context Protocol) lets Cline use external tools and data sources through MCP servers.”
   • [github] “Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP servers.”
   • [github] “Cline as a native app for macOS and Windows. Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP server…”
   • [claimed-docs] “YOLO mode is Auto Approve on steroids. Check the box and Cline auto-approves everything: file changes, terminal commands, browser actions, M…”

   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 Cline
   Cline✓fullprobed9/10

   Cline ships a well-documented official CLI (npm install -g cline) supporting interactive and headless modes, auto-approve automation, piping (git diff | cline), scripting/CI use, and cron scheduling via the hub, all under the same core engine as other Cline surfaces. Missing for 10: independent/hands-on community verification specifically of the CLI (community evidence discusses the IDE/agent experience generally, not the CLI itself).

   • [claimed-docs] “Run Cline in your terminal with interactive chat or fully headless automation for CI/CD and scripting.”
   • [claimed-docs] “Use headless mode for scripts/automation and processable output.”
   • [claimed-docs] “Autonomous execution can modify files and run commands without further prompts.”
   • [claimed-docs] “npm install -g cline”
   • [claimed-docs] “Use Cline CLI for interactive terminal sessions and automated headless workflows.”
   • [claimed-docs] “cline --auto-approve true "run tests and fix failures"”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [probe] “official CLI documented at https://docs.cline.bot/usage/cli-overview”

   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 drawn
   Cline~partialprobed6/10

   Cline documents multiple programmatic surfaces — a scriptable CLI with headless mode and processable output (cline-docs-3, cline-docs-32), cron-scheduled agents (cline-docs-23), and the ACP protocol letting any ACP-capable client drive Cline as a coding agent (cline-docs-7, cline-docs-26) — which together let an AI-native user drive it programmatically. However, an explicit probe for a formal public REST/OpenAPI API found nothing (cline-probe-3: all candidate openapi/swagger paths 404), so there's no conventional documented public API, only CLI/ACP surfaces. Missing for 10: a formal REST/HTTP API with OpenAPI/swagger docs or SDK reference, and independent hands-on confirmation of scripting the CLI/ACP end-to-end.

   • [claimed-docs] “Use headless mode for scripts/automation and processable output.”
   • [claimed-docs] “Autonomous execution can modify files and run commands without further prompts.”
   • [claimed-docs] “Use Cline CLI for interactive terminal sessions and automated headless workflows.”
   • [claimed-docs] “cline --auto-approve true "run tests and fix failures"”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [claimed-docs] “Any ACP-capable client can use Cline as its coding agent without a dedicated extension”
   • [claimed-docs] “Any ACP-capable client can use Cline as its coding agent without a dedicated extension — the same agent you use in the terminal, embedded in…”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [claimed-docs] “Build AI agents and integrations powered by the same core engine behind the CLI, Kanban, VS Code extension, and JetBrains plugin.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cline.bot/openapi.json, https://docs.cline.bot/swagger.json, https://docs.cline.bot/api…”

   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
   Cline—none0/10

   Evidence shows Cline supports Bring-Your-Own-Key (BYOK) for various providers and its own sign-in credit system, but there is no mention of issuing scoped, permission-limited, or least-privilege API credentials/tokens for the agent — only full provider keys and coarse action-approval settings (auto-approve, plan/act mode) which govern actions, not credential scope.

   • [claimed-docs] “Absolutely! You can bring your own API keys from providers like OpenAI, Anthropic, Google, and others.”
   • [claimed-docs] “Bring Your Own Key (BYOK): use your own provider credentials (cloud or local runtimes).”
   • [claimed-docs] “Instead of managing separate API keys across multiple vendors, you sign in once, add Cline credits, and select from available models directl…”
   • [claimed-docs] “Auto Approve lets you decide which actions Cline can take without prompting you each time.”

   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
   Cline~partialprobed3/10

   Cline docs mention building 'AI agents and integrations powered by the same core engine' behind its CLI/Kanban/IDE plugins, implying an SDK-like foundation, but there's no actual SDK package, API reference, or code samples, and a probe for OpenAPI/schema docs returned 404s across all candidate paths. missing for 10: published SDK package/reference docs, code samples for building against the engine, independent evidence of third-party integrations built with it.

   • [claimed-docs] “Build AI agents and integrations powered by the same core engine behind the CLI, Kanban, VS Code extension, and JetBrains plugin.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cline.bot/openapi.json, https://docs.cline.bot/swagger.json, https://docs.cline.bot/api…”

   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
   Cline—none0/10

   No evidence of webhook subscription capability; Cline's integrations (Slack, Discord, Telegram, Linear, CI/CD pipelines) are described as chat/automation surfaces, not an event/webhook subscription API, and the openapi probe returned all 404s suggesting no public API surface for such events.

   • [claimed-docs] “Chat with the agent from Slack, Discord, Telegram, or Linear. Run it headlessly inside GitHub Actions, GitLab, or any pipeline.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cline.bot/openapi.json, https://docs.cline.bot/swagger.json, https://docs.cline.bot/api…”

   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
   Cline~partialclaimed5/10

   Cline is an agentic coding assistant that generates code changes, diffs, and can research a codebase via subagents, which counts as AI-generated suggestions inside the product, but this is code-editing/task-execution rather than 'insights and suggestions from my data' in a BI/analytics sense — there's no evidence of dashboards, data analysis, or insight summaries over user data. missing for 10: evidence of analyzing/summarizing arbitrary user data (not just code) and presenting insights/recommendations distinct from code edits.

   • [claimed-docs] “Subagents let Cline spawn focused research agents that run in parallel.”
   • [claimed-docs] “Subagents let Cline spawn focused research agents that run in parallel. Each subagent gets its own prompt and context window, explores the c…”
   • [github] “In VS Code and JetBrains, every edit shows up as a diff you can review, modify, or revert.”
   • [claimed-docs] “Coordinated multi-file changes with linter-aware fixes, diffs, checkpoints, and one-click undo on every step.”

   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 drawn
   Cline✓fullclaimed8/10

   Cline's CLI/hub explicitly supports cron-scheduled agents that persist across restarts and run independently of any terminal session, enabling recurring background automations like daily summaries or code reviews, plus headless mode for CI/CD pipelines and chat integrations (Slack/Discord/Telegram/Linear). This is well documented first-party but lacks independent hands-on confirmation of the scheduling feature specifically. Missing for 10: independent/community verification of the cron-scheduling feature working in practice, more detail on reliability/failure handling of unattended runs.

   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [claimed-docs] “Run agents on cron schedules for recurring automations like daily summaries and code reviews.”
   • [claimed-docs] “Chat with the agent from Slack, Discord, Telegram, or Linear. Run it headlessly inside GitHub Actions, GitLab, or any pipeline.”
   • [claimed-docs] “Use headless mode for scripts/automation and processable output.”
   • [claimed-docs] “Autonomous execution can modify files and run commands without further prompts.”

   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 Cline
   Cline✓fullcommunity9/10

   Cline is a built-in AI coding assistant that can be delegated tasks directly (file edits, terminal commands, browser use) via natural conversation, with plan/act modes, auto-approve/YOLO autonomy, and hands-on community corroboration of effective autonomous task completion. Both first-party docs and independent HN reviews confirm real delegation of substantive coding tasks. Missing for 10: no independent benchmark/quality study beyond anecdotal forum praise/criticism.

   • [claimed-docs] “AI coding assistant in your editor. Create files, run commands, browse the web, and use tools with human-in-the-loop approval.”
   • [claimed-docs] “It can read and write files, run terminal commands, use a browser, and help you build features through natural conversation. Every action re…”
   • [claimed-docs] “Plan mode lets you explore and strategize without changing files. Act mode executes against your plan.”
   • [claimed-docs] “Auto Approve lets you decide which actions Cline can take without prompting you each time.”
   • [claimed-docs] “YOLO mode is Auto Approve on steroids. Check the box and Cline auto-approves everything: file changes, terminal commands, browser actions, M…”
   • [community] “Cline is, hands down, the most effective agentic coding tool out there. I've extensively daily driven any one of them you can name, and ther…”
   • [community] “Cline is the most impressive agentic coder tool I've used and it seems to be getting better. I can plan with it for 10-15 minutes, set it lo…”
   • [community] “I can have cline control a terminal command, it's by no means limited to editing code... I find Cline better [than Claude Code] (plus I can …”

   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 Cline
   Cline✓fullcommunity9/10

   Cline is built entirely around natural-language task commands — through IDE chat, CLI ('cline "run tests and fix failures"'), Slack/Discord/Telegram/Linear chat, and headless CI automation — and community reviews corroborate it as a strong agentic natural-language coding tool. Missing for 10: no formal benchmark/independent test of NL command robustness across all surfaces.

   • [claimed-docs] “It can read and write files, run terminal commands, use a browser, and help you build features through natural conversation. Every action re…”
   • [claimed-docs] “cline --auto-approve true "run tests and fix failures"”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [claimed-docs] “Chat with the agent from Slack, Discord, Telegram, or Linear. Run it headlessly inside GitHub Actions, GitLab, or any pipeline.”
   • [claimed-docs] “Use headless mode for scripts/automation and processable output.”
   • [community] “Cline is, hands down, the most effective agentic coding tool out there. I've extensively daily driven any one of them you can name, and ther…”
   • [community] “Cline is the most impressive agentic coder tool I've used and it seems to be getting better. I can plan with it for 10-15 minutes, set it lo…”

   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
   Cline—none0/10

   A direct probe for OpenAPI/swagger specs returned 404 on all candidate paths, and no documentation elsewhere references a downloadable machine-readable API spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cline.bot/openapi.json, https://docs.cline.bot/swagger.json, https://docs.cline.bot/api…”

   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 userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Cline—none0/10

   No evidence of versioned APIs or a documented deprecation policy; the OpenAPI probe found no API spec at any candidate path, and no docs mention API versioning or deprecation practices.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cline.bot/openapi.json, https://docs.cline.bot/swagger.json, https://docs.cline.bot/api…”

   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 to Cline
   Cline✓fullclaimed7/10

   Cline explicitly supports running many agents in parallel via a Kanban task board with isolated worktrees and dependency chains, spawning parallel subagents for research, and CLI/cron-based headless automation for scripted bulk workflows (e.g. batch test-fixing, scheduled recurring runs). This directly supports bulk/automation-depth operations across many items, though evidence is entirely vendor-documented with no independent hands-on account of actually running large-scale bulk jobs. Missing for 10: independent/community verification of large-scale bulk usage, and concrete examples of bulk operations beyond parallel agents (e.g., processing many files/tickets in one command).

   • [claimed-docs] “Run many agents in parallel from a web-based task board with per-card worktrees, auto-commit, and dependency chains.”
   • [claimed-docs] “Use Cline Kanban to run multiple coding agents in parallel with isolated git worktrees.”
   • [claimed-docs] “Subagents let Cline spawn focused research agents that run in parallel.”
   • [claimed-docs] “Subagents let Cline spawn focused research agents that run in parallel. Each subagent gets its own prompt and context window, explores the c…”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [claimed-docs] “Run agents on cron schedules for recurring automations like daily summaries and code reviews.”
   • [claimed-docs] “cline --auto-approve true "run tests and fix failures"”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [claimed-docs] “Use headless mode for scripts/automation and processable output.”

   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
   Cline~partialclaimed7/10

   Cline's CLI/hub supports cron-scheduled agents that persist and run automatically (e.g., daily summaries, code reviews), plus headless mode for CI/CD pipelines and chat-platform triggers (Slack/Discord/Telegram/Linear), which together enable automatic action-triggering on time/events. However, this is scheduling/pipeline-integration rather than a general event-rule engine, and there's no independent/community verification of these automation triggers working reliably in practice. Missing for 10: a broader event-based rule/trigger system beyond cron and CI hooks, and hands-on/community corroboration of scheduled or event-driven automation actually functioning as documented.

   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [claimed-docs] “Run agents on cron schedules for recurring automations like daily summaries and code reviews.”
   • [claimed-docs] “Chat with the agent from Slack, Discord, Telegram, or Linear. Run it headlessly inside GitHub Actions, GitLab, or any pipeline.”
   • [claimed-docs] “Use headless mode for scripts/automation and processable output.”
   • [claimed-docs] “Run Cline in your terminal with interactive chat or fully headless automation for CI/CD and scripting.”

   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
   Cline✓fullclaimed7/10

   Cline's docs explicitly describe running agents on cron schedules through its CLI hub, persisting across restarts, for recurring automations like daily summaries and code reviews (cline-docs-13, cline-docs-23, cline-docs-36), directly matching the story. Missing for 10: independent/hands-on confirmation of scheduling reliability and details on failure handling/monitoring of scheduled jobs.

   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [claimed-docs] “Run agents on cron schedules for recurring automations like daily summaries and code reviews.”
   • [claimed-docs] “Use Cline CLI for interactive terminal sessions and automated headless workflows.”

   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 Cline
   Cline~partialclaimed6/10

   Cline documents checkpoints, per-step diffs, and one-click undo for the agent's actions, plus Kanban card diff review with inline comments, which lets an ai-native user review and roll back the results of an automation run (cline-docs-30, cline-gh-1, cline-docs-47). However, there is no evidence of first-class versioning/rollback for the automation definitions themselves (skills, scheduled cron routines, subagent configs) — no version history or rollback UI is documented for those artifacts. Missing for 10: explicit version history/rollback for skills and scheduled automations, independent hands-on confirmation of the undo/checkpoint feature working reliably.

   • [claimed-docs] “Coordinated multi-file changes with linter-aware fixes, diffs, checkpoints, and one-click undo on every step.”
   • [github] “In VS Code and JetBrains, every edit shows up as a diff you can review, modify, or revert.”
   • [claimed-docs] “Review diffs in card detail view and leave inline comments.”
   • [claimed-docs] “Skills are modular instruction sets that extend Cline's capabilities for specific tasks.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”

   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 drawn
   Cline~partialclaimed6/10

   Cline supports headless/autonomous execution, cron-scheduled agents, parallel Kanban agents with isolated worktrees, auto-commit, diff review, and inline comments, which together approximate a 'cloud agent builds/tests/demos and I review' workflow. However, there's no explicit evidence of a fully cloud-hosted (non-local) agent environment, integrated automated testing/demo generation, or a dedicated review UI beyond diff/comment viewing. missing for 10: dedicated cloud execution environment (not just local/CI runners), built-in test execution and demo artifact generation, end-to-end proof of a single autonomous run producing a reviewable demo, independent hands-on confirmation of this specific workflow.

   • [claimed-docs] “Run many agents in parallel from a web-based task board with per-card worktrees, auto-commit, and dependency chains.”
   • [claimed-docs] “Use Cline Kanban to run multiple coding agents in parallel with isolated git worktrees.”
   • [claimed-docs] “Review diffs in card detail view and leave inline comments.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [claimed-docs] “Chat with the agent from Slack, Discord, Telegram, or Linear. Run it headlessly inside GitHub Actions, GitLab, or any pipeline.”
   • [claimed-docs] “Autonomous execution can modify files and run commands without further prompts.”

   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
   Cline~partialclaimed4/10

   Cline supports background/async execution via CLI headless mode, cron-scheduled agents that 'persist across process restarts and run independently of any terminal session,' and a Kanban board with isolated git worktrees for parallel agents, plus CI/CD integration (GitHub Actions/GitLab). However, none of this evidence describes a Cline-hosted or fully isolated cloud sandbox — the scheduling/hub and worktrees appear to run on the user's own machine or CI infrastructure rather than a dedicated cloud environment. missing for 10: explicit documentation of a Cline-managed cloud/remote execution environment, isolation guarantees (e.g., containerization) for background tasks, and independent confirmation of cloud-hosted background runs.

   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [claimed-docs] “Run agents on cron schedules for recurring automations like daily summaries and code reviews.”
   • [claimed-docs] “Use Cline Kanban to run multiple coding agents in parallel with isolated git worktrees.”
   • [claimed-docs] “Chat with the agent from Slack, Discord, Telegram, or Linear. Run it headlessly inside GitHub Actions, GitLab, or any pipeline.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub.”

   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 Cline
   Cline✓fullclaimed8/10

   Cline's Kanban board explicitly supports running many agents in parallel with isolated git worktrees, auto-commit, and dependency chains, while subagents spawn parallel focused research agents and CLI scheduling lets agents run on cron schedules that persist across restarts and run independently of any terminal session—directly matching 'fleets working in parallel for hours or days.' Missing for 10: independent/hands-on corroboration of long-duration (multi-day) fleet runs and scale limits, since community evidence only discusses single-agent session quality, not fleet orchestration.

   • [claimed-docs] “Run many agents in parallel from a web-based task board with per-card worktrees, auto-commit, and dependency chains.”
   • [claimed-docs] “Use Cline Kanban to run multiple coding agents in parallel with isolated git worktrees.”
   • [claimed-docs] “Subagents let Cline spawn focused research agents that run in parallel. Each subagent gets its own prompt and context window, explores the c…”
   • [claimed-docs] “Subagents let Cline spawn focused research agents that run in parallel.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [claimed-docs] “Run agents on cron schedules for recurring automations like daily summaries and code reviews.”
   • [github] “Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP servers.”

   proof ↗⚑ 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 Cline
   Cline✓fullclaimed8/10

   Cline's Kanban board explicitly supports running multiple coding agents in parallel with isolated git worktrees per card, and lets you review diffs and leave inline comments per card before deciding which to keep — directly matching the parallel-attempt/compare story. missing for 10: independent/hands-on corroboration of the Kanban parallel-run workflow (community evidence covers general Cline use, not Kanban specifically), and no detail on an explicit 'pick winner and discard others' UX beyond diff review.

   • [claimed-docs] “Run many agents in parallel from a web-based task board with per-card worktrees, auto-commit, and dependency chains.”
   • [claimed-docs] “Use Cline Kanban to run multiple coding agents in parallel with isolated git worktrees.”
   • [claimed-docs] “Review diffs in card detail view and leave inline comments.”
   • [github] “Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP servers.”
   • [github] “Cline as a native app for macOS and Windows. Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP server…”

   proof ↗⚑ 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 Cline
   Cline✓fullclaimed8/10

   Cline's CLI documents cron-based scheduling of agents that 'persist across process restarts and run independently of any terminal session,' explicitly for 'recurring automations like daily summaries and code reviews' (cline-docs-13, 23, 36), plus chat-triggered agents via Slack/Discord/Telegram/Linear and headless operation in CI/CD pipelines (cline-docs-17), combined with auto-approve/YOLO mode for unattended autonomous execution (cline-docs-21, 22). missing for 10: independent/hands-on corroboration of the scheduling feature actually working reliably in production, and more detail on trigger-based (non-cron) autonomous maintenance workflows

   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [claimed-docs] “Run agents on cron schedules for recurring automations like daily summaries and code reviews.”
   • [claimed-docs] “Chat with the agent from Slack, Discord, Telegram, or Linear. Run it headlessly inside GitHub Actions, GitLab, or any pipeline.”
   • [claimed-docs] “YOLO mode is Auto Approve on steroids. Check the box and Cline auto-approves everything: file changes, terminal commands, browser actions, M…”
   • [claimed-docs] “cline --auto-approve true "run tests and fix failures"”

   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

Code completion

1. developerReceive inline code completions and next-edit suggestions as I type

   weight 3 · round to Google Antigravity
   Cline—none0/10

   Evidence describes Cline as a chat-driven, task-based agentic coding assistant that edits files via reviewable diffs and terminal actions, not an inline ghost-text/next-edit-suggestion tool that activates as you type. No citation mentions autocomplete-style inline completions or next-edit prediction.

   • [claimed-docs] “AI coding assistant in your editor. Create files, run commands, browse the web, and use tools with human-in-the-loop approval.”
   • [github] “In VS Code and JetBrains, every edit shows up as a diff you can review, modify, or revert.”
   • [claimed-docs] “Plan mode lets you explore and strategize without changing files. Act mode executes against your plan.”
   • [claimed-docs] “Coordinated multi-file changes with linter-aware fixes, diffs, checkpoints, and one-click undo on every step.”

   proof ↗⚑ flag

   Google Antigravity~partialclaimed5/10

   Docs mention the Editor view offers 'tab autocompletion' and 'natural language code commands' alongside the agent, which covers basic inline completion, but there is no detail on next-edit suggestions (predictive multi-line edits) or independent/hands-on confirmation of completion quality or latency. missing for 10: explicit next-edit-suggestion feature description, independent hands-on validation of autocomplete quality/reliability.

   • [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”

   proof ↗⚑ flag

Debugging

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

   weight 1 · round to Cline
   Cline~partialclaimed5/10

   Cline can run and interact with a live dev server/terminal in real time (cline-docs-14) and has a browser tool it can use to inspect visual issues (cline-docs-1, cline-docs-18, cline-docs-22), which supports basic live-app debugging like fixing layout bugs from a screenshot. However there's no evidence of deeper live-debugging features such as reading browser console/network logs, setting breakpoints, or inspecting running app state beyond screenshots. Missing for 10: console/network log inspection, breakpoint/step debugging, structured devtools integration, and independent hands-on confirmation of live web-app debugging.

   • [claimed-docs] “Executes in your terminal and reacts to output as it appears. Long-running dev servers, tests, deploys, all handled live.”
   • [claimed-docs] “AI coding assistant in your editor. Create files, run commands, browse the web, and use tools with human-in-the-loop approval.”
   • [claimed-docs] “fix the layout issue shown in @./screenshot.png”
   • [claimed-docs] “YOLO mode is Auto Approve on steroids. Check the box and Cline auto-approves everything: file changes, terminal commands, browser actions, 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 Cline
   Cline✓fullcommunity7/10

   Cline supports natural-language driven debugging: it can run tests and fix failures (cline-docs-33), react live to terminal output for dev servers/tests/deploys (cline-docs-14), review diffs and codebase issues via conversation (cline-docs-34, cline-docs-31), and community reviews confirm strong agentic troubleshooting effectiveness (cline-comm-1, cline-comm-3, cline-comm-10). Missing for 10: dedicated 'debugging mode' documentation, structured error-trace analysis features, and independent benchmarks specifically on bug-fixing accuracy.

   • [claimed-docs] “cline --auto-approve true "run tests and fix failures"”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [claimed-docs] “Executes in your terminal and reacts to output as it appears. Long-running dev servers, tests, deploys, all handled live.”
   • [claimed-docs] “It can read and write files, run terminal commands, use a browser, and help you build features through natural conversation. Every action re…”
   • [community] “Cline is, hands down, the most effective agentic coding tool out there. I've extensively daily driven any one of them you can name, and ther…”
   • [community] “Cline is the most impressive agentic coder tool I've used and it seems to be getting better. I can plan with it for 10-15 minutes, set it lo…”
   • [community] “I can have cline control a terminal command, it's by no means limited to editing code... I find Cline better [than Claude Code] (plus I can …”

   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 Cline
   Cline~partialclaimed4/10

   Cline offers strong underlying primitives—autonomous file edits, terminal/git command execution, headless CI/CD runs, and PR-adjacent workflows like 'git diff | cline review'—but there is no evidence of a dedicated feature that ingests a tracked issue (e.g., GitHub issue) and produces a complete pull request end-to-end. missing for 10: explicit issue-tracker integration (e.g., GitHub Issues API), automated PR creation/submission step, and any documented end-to-end issue-to-PR workflow or case study.

   • [claimed-docs] “Use headless mode for scripts/automation and processable output.”
   • [claimed-docs] “Autonomous execution can modify files and run commands without further prompts.”
   • [claimed-docs] “Chat with the agent from Slack, Discord, Telegram, or Linear. Run it headlessly inside GitHub Actions, GitLab, or any pipeline.”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [github] “In VS Code and JetBrains, every edit shows up as a diff you can review, modify, or revert.”

   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 Cline
   Cline✓fullcommunity8/10

   Cline's core value prop is natural-language coding tasks executed across files with diffs, multi-file coordination, terminal execution, and undo/checkpoints, backed by both docs and strong community testimony of successful multi-file autonomous edits. missing for 10: independent benchmark data on multi-file bug-fix accuracy, and resolution of community complaints about needing many prompts/codebase indexing gaps in some cases.

   • [claimed-docs] “AI coding assistant in your editor. Create files, run commands, browse the web, and use tools with human-in-the-loop approval.”
   • [claimed-docs] “Coordinated multi-file changes with linter-aware fixes, diffs, checkpoints, and one-click undo on every step.”
   • [github] “In VS Code and JetBrains, every edit shows up as a diff you can review, modify, or revert.”
   • [claimed-docs] “cline --auto-approve true "run tests and fix failures"”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [community] “Cline is, hands down, the most effective agentic coding tool out there. I've extensively daily driven any one of them you can name, and ther…”
   • [community] “Cline is the most impressive agentic coder tool I've used and it seems to be getting better. I can plan with it for 10-15 minutes, set it lo…”
   • [community] “After trying cline, aider, codex, and what not, I feel claude code is just so so better than all of them. It takes much much fewer prompts t…”

   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 Cline
   Cline✓fullcommunity7/10

   Cline is a general-purpose coding agent with terminal execution, file editing, and auto-approve modes; docs show concrete examples of writing/running tests and fixing failures (cline-docs-33), linter-aware multi-file fixes (cline-docs-30), and reviewing diffs (cline-docs-34), all backed by community reports of strong autonomous coding performance (cline-comm-1, cline-comm-3). Merge conflict resolution and dependency updates aren't explicitly demoed, but they fall squarely within the same terminal-command + file-edit capability set already evidenced. missing for 10: explicit worked example of merge conflict resolution, explicit example of dependency update workflow, independent hands-on validation of these exact tasks.

   • [claimed-docs] “cline --auto-approve true "run tests and fix failures"”
   • [claimed-docs] “Coordinated multi-file changes with linter-aware fixes, diffs, checkpoints, and one-click undo on every step.”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [claimed-docs] “Executes in your terminal and reacts to output as it appears. Long-running dev servers, tests, deploys, all handled live.”
   • [community] “Cline is, hands down, the most effective agentic coding tool out there. I've extensively daily driven any one of them you can name, and ther…”
   • [community] “Cline is the most impressive agentic coder tool I've used and it seems to be getting better. I can plan with it for 10-15 minutes, set it lo…”
   • [claimed-docs] “It can read and write files, run terminal commands, use a browser, and help you build features through natural conversation. Every action re…”

   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 Google Antigravity
   Cline~partialclaimed3/10

   Cline's CLI example shows it can accept an image reference (@./screenshot.png) to address a layout issue, implying some multimodal/image input capability, and general docs confirm it can build features from natural conversation and modify files/commands. However there is no evidence of a dedicated 'sketch/image/PDF-to-app' workflow, no PDF input support, and no documented end-to-end example of generating a full working app from a design file. missing for 10: PDF input support, a documented sketch-to-app or design-to-code workflow, evidence of generating a complete app (not just a layout fix) from an image.

   • [claimed-docs] “fix the layout issue shown in @./screenshot.png”
   • [claimed-docs] “It can read and write files, run terminal commands, use a browser, and help you build features through natural conversation. Every action re…”

   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 drawn
   Cline~partialcommunity6/10

   Cline's Plan mode explicitly lets the agent read the codebase, run searches, and discuss strategy before any edits, and Subagents can explore the codebase independently and return detailed reports to help orient before changes are made, supporting the story's core intent. However, community discussion (HN) specifically disputes Cline's codebase-understanding approach, criticizing it for not indexing the codebase and calling this a 'missing major feature,' while other users report good results letting it explore and act on a codebase — a genuine mixed signal on how well it maps large/unfamiliar codebases. Missing for 10: a dedicated codebase-mapping/indexing feature, independent benchmarks on navigation accuracy, and resolution of the indexing critique.

   • [claimed-docs] “Plan mode is where you and Cline figure out what you're building and how. In this mode, Cline can read your codebase, run searches, and disc…”
   • [claimed-docs] “Subagents let Cline spawn focused research agents that run in parallel. Each subagent gets its own prompt and context window, explores the c…”
   • [github] “In VS Code and JetBrains, every edit shows up as a diff you can review, modify, or revert.”
   • [community] “This honestly makes me think less of Cline. They're wrong about this [not indexing codebase] and it seems like they're trying to do damage c…”
   • [community] “Cline is the most impressive agentic coder tool I've used and it seems to be getting better. I can plan with it for 10-15 minutes, set it lo…”

   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
   Cline!disputedcontradicted5/10

   Cline's docs describe agentic exploration (Plan mode reads the codebase and runs searches, subagents spawn parallel research agents that 'explore the codebase independently' and report back) which supports mapping an unfamiliar codebase without manual file selection. However, a hands-on community discussion explicitly disputes this, criticizing Cline for not indexing the codebase and calling it 'wrong' and 'missing a major feature' for large/unfamiliar codebase understanding. Missing for 10: first-party documentation of a dedicated codebase-mapping/indexing feature, and independent corroboration that agentic search alone reliably substitutes for indexing on large unfamiliar repos.

   • [claimed-docs] “Plan mode is where you and Cline figure out what you're building and how. In this mode, Cline can read your codebase, run searches, and disc…”
   • [claimed-docs] “Subagents let Cline spawn focused research agents that run in parallel. Each subagent gets its own prompt and context window, explores the c…”
   • [claimed-docs] “Subagents let Cline spawn focused research agents that run in parallel.”
   • [community] “This honestly makes me think less of Cline. They're wrong about this [not indexing codebase] and it seems like they're trying to do damage c…”
   • [community] “Cline is the most impressive agentic coder tool I've used and it seems to be getting better. I can plan with it for 10-15 minutes, set it lo…”

   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 drawn
   Cline—none0/10

   The evidence pack shows conversation continuity only within a session when switching Plan/Act modes (cline-docs-40), but no documented feature for automatically building and recalling memory across separate sessions (e.g., a memory bank, persistent context store, or session-recall mechanism). Skills, subagents, and scheduling features are unrelated to automatic cross-session memory.

   • [claimed-docs] “The conversation history carries over when you switch modes. Cline remembers everything you discussed in Plan mode, so you don't need to rep…”

   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 to Google Antigravity
   Cline—none0/10

   No evidence describes Cline supporting multiple project directories or multi-root workspaces within a single session; evidence only mentions running agent sessions 'in any folder' (singular) and per-card worktrees for parallel agents, not combined multi-directory context.

   • [github] “Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP servers.”
   • [github] “Cline as a native app for macOS and Windows. Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP server…”

   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
   Cline~partialclaimed3/10

   The evidence only mentions 'Skills' as modular instruction sets that extend Cline's capabilities for specific tasks, which is tangential to a dedicated project-wide instructions/coding-standards file rather than a clear equivalent of a rules file. Missing for 10: explicit documentation of a project-level instructions/rules file (e.g. a .clinerules-style config), guidance on setting coding standards/conventions, and any community corroboration of this specific feature.

   • [claimed-docs] “Skills are modular instruction sets that extend Cline's capabilities for specific tasks.”

   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 Cline
   Cline~partialcommunity7/10

   Cline can execute terminal commands and react live to test/dev-server output (cline-docs-14), run test-fix loops via CLI (cline-docs-33), review diffs (cline-docs-34, cline-gh-1), use Plan mode to explore/narrow root causes via codebase search (cline-docs-39), and spawn subagents for independent codebase investigation (cline-docs-25). Checkpoints/undo support verifying and rolling back fixes (cline-docs-30), and community feedback confirms it can autonomously produce correct diffs after exploration (cline-comm-3). Missing for 10: no explicit debugging-specific tooling (e.g., breakpoints/log tracing) or independent hands-on case studies specifically about root-cause diagnosis and fix verification workflows.

   • [claimed-docs] “Executes in your terminal and reacts to output as it appears. Long-running dev servers, tests, deploys, all handled live.”
   • [claimed-docs] “cline --auto-approve true "run tests and fix failures"”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [claimed-docs] “Plan mode is where you and Cline figure out what you're building and how. In this mode, Cline can read your codebase, run searches, and disc…”
   • [claimed-docs] “Subagents let Cline spawn focused research agents that run in parallel. Each subagent gets its own prompt and context window, explores the c…”
   • [claimed-docs] “Coordinated multi-file changes with linter-aware fixes, diffs, checkpoints, and one-click undo on every step.”
   • [github] “In VS Code and JetBrains, every edit shows up as a diff you can review, modify, or revert.”
   • [community] “Cline is the most impressive agentic coder tool I've used and it seems to be getting better. I can plan with it for 10-15 minutes, set it lo…”

   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 drawn
   Cline✓fullclaimed8/10

   Cline has a dedicated Skills feature: modular instruction sets that package guidance, processes, and optional resources, loaded only when relevant to the task, explicitly designed to extend Cline's capabilities for specialized tasks. This is directly documented first-party functionality matching the story, though independent/hands-on corroboration is absent. Missing for 10: independent or community validation of skill authoring/usage, and details on a skills marketplace/sharing ecosystem.

   • [claimed-docs] “Skills are modular instruction sets that extend Cline's capabilities for specific tasks.”
   • [claimed-docs] “Skills are modular instruction sets that extend Cline's capabilities for specific tasks. Each skill packages detailed guidance, processes, a…”

   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 Cline
   Cline~partialclaimed5/10

   Cline supports MCP servers for external tool/data integration and ACP so third-party clients (editors, tools) can embed Cline as an agent, plus chat integrations (Slack, Discord, Telegram, Linear) and CI/CD pipeline embedding — all evidence of ecosystem interoperability. However there's no explicit evidence of a marketplace or catalog of partner-built 'agent apps' that can be dropped into Cline workflows the way MCP tools can. Missing for 10: a documented partner/agent marketplace, third-party agent app examples, and independent verification of such integrations working end-to-end.

   • [claimed-docs] “MCP (Model Context Protocol) lets Cline use external tools and data sources through MCP servers.”
   • [claimed-docs] “Any ACP-capable client can use Cline as its coding agent without a dedicated extension — the same agent you use in the terminal, embedded in…”
   • [claimed-docs] “Chat with the agent from Slack, Discord, Telegram, or Linear. Run it headlessly inside GitHub Actions, GitLab, or any pipeline.”
   • [github] “Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP servers.”

   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
   Cline—none0/10

   Cline's evidence covers a Kanban task board for running parallel agents with worktrees, MCP integrations, and skills/instructions, but none of this describes ingesting team docs and repos into a shared knowledge workspace or source-of-truth repository for engineering leads. Missing for 10: any feature for indexing/aggregating documentation and codebases into a shared, queryable team knowledge base, evidence of team-wide onboarding or knowledge-sharing workspace, and any first-party or community mention of such a capability.

   • [claimed-docs] “Run many agents in parallel from a web-based task board with per-card worktrees, auto-commit, and dependency chains.”
   • [claimed-docs] “Use Cline Kanban to run multiple coding agents in parallel with isolated git worktrees.”
   • [claimed-docs] “Review diffs in card detail view and leave inline comments.”
   • [claimed-docs] “MCP (Model Context Protocol) lets Cline use external tools and data sources through MCP servers.”

   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 to Cline
   Cline~partialclaimed6/10

   Cline explicitly supports chatting with the agent from Slack (and Discord/Telegram/Linear) and documents MCP as the general mechanism for connecting external tools and data sources, which is how community MCP servers for Jira, Google Drive, etc. are typically wired in. However, there's no direct evidence of a first-party Jira or Google Drive integration or MCP server. Missing for 10: explicit Jira integration evidence, explicit Google Drive integration evidence, and confirmation these connect specifically for context-extension use cases beyond chat.

   • [claimed-docs] “Chat with the agent from Slack, Discord, Telegram, or Linear. Run it headlessly inside GitHub Actions, GitLab, or any pipeline.”
   • [claimed-docs] “MCP (Model Context Protocol) lets Cline use external tools and data sources through MCP servers.”
   • [github] “Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP servers.”

   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 Cline
   Cline~partialclaimed6/10

   cline-docs-17 explicitly claims chat/task-kickoff via Slack, Discord, Telegram, Linear, and headless runs in GitHub Actions/GitLab pipelines, directly matching the story. However this is a single marketing-page mention with no deeper docs on setup, no independent/hands-on corroboration, and no GitHub-specific (issue/PR trigger) integration details beyond CI headless mode. Missing for 10: independent verification, per-platform setup documentation, and confirmation of native GitHub issue/PR-triggered task kickoff.

   • [claimed-docs] “Chat with the agent from Slack, Discord, Telegram, or Linear. Run it headlessly inside GitHub Actions, GitLab, or any pipeline.”

   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
   Cline~partialclaimed5/10

   Cline's Kanban (web-based task board) and CLI with cron-scheduled agents that persist across restarts suggest tasks can be started and later resumed independently of a single device/session, and Cline works across many IDEs/editors so a task's environment isn't tied to one editor. However there is no explicit documentation of cross-device session handoff or browser-based continuation of a specific in-progress task (e.g., syncing an active conversation/task state to a different machine or web UI). missing for 10: explicit cross-device task/session sync or handoff mechanism, browser-based resumption of an existing task, and independent/community confirmation of this specific workflow.

   • [claimed-docs] “Run many agents in parallel from a web-based task board with per-card worktrees, auto-commit, and dependency chains.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [claimed-docs] “Use Cline Kanban to run multiple coding agents in parallel with isolated git worktrees.”
   • [claimed-docs] “Cline works across all major editors: **VS Code**, **Cursor**, **Windsurf**, **JetBrains** (IntelliJ, PyCharm, WebStorm), **Antigravity**, a…”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub.”

   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 to Cline
   Cline~partialclaimed6/10

   Cline explicitly supports JetBrains IDEs and documents that edits in JetBrains show up as reviewable/revertable diffs (cline-gh-1, cline-docs-6, cline-docs-28), covering the interactive diff part of the story. However, there is no explicit documentation of a 'share selected code as context' feature specifically for the JetBrains plugin (only general chat/context usage is implied), so the second half of the story is unevidenced. Missing for 10: explicit JetBrains-specific documentation or screenshots of selecting code and adding it as context, independent/hands-on confirmation of this specific workflow in JetBrains.

   • [github] “In VS Code and JetBrains, every edit shows up as a diff you can review, modify, or revert.”
   • [claimed-docs] “The same Cline experience in IntelliJ IDEA, PyCharm, WebStorm, GoLand, and the rest of the JetBrains family.”
   • [claimed-docs] “Cline works across all major editors: **VS Code**, **Cursor**, **Windsurf**, **JetBrains** (IntelliJ, PyCharm, WebStorm), **Antigravity**, a…”
   • [claimed-docs] “IDE Extension — VS Code, Cursor, JetBrains, Windsurf, VSCodium, Antigravity”

   proof ↗⚑ 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 Cline
   Cline✓fullcommunity9/10

   Cline is documented as an AI coding assistant embedded directly in VS Code, JetBrains IDEs, Cursor, Windsurf, and other editors, providing conversational chat with contextual codebase access, file/command actions, and inline diff review (cline-docs-1, cline-docs-6, cline-docs-28, cline-docs-31, cline-gh-1). Community reports from daily users corroborate effective in-IDE agentic chat experience (cline-comm-1, cline-comm-3, cline-comm-7, cline-comm-10). Missing for 10: independent third-party UX review specifically of the chat panel interface itself (most evidence is vendor docs).

   • [claimed-docs] “AI coding assistant in your editor. Create files, run commands, browse the web, and use tools with human-in-the-loop approval.”
   • [claimed-docs] “The same Cline experience in IntelliJ IDEA, PyCharm, WebStorm, GoLand, and the rest of the JetBrains family.”
   • [claimed-docs] “Cline works across all major editors: **VS Code**, **Cursor**, **Windsurf**, **JetBrains** (IntelliJ, PyCharm, WebStorm), **Antigravity**, a…”
   • [claimed-docs] “It can read and write files, run terminal commands, use a browser, and help you build features through natural conversation. Every action re…”
   • [github] “In VS Code and JetBrains, every edit shows up as a diff you can review, modify, or revert.”
   • [community] “Cline is, hands down, the most effective agentic coding tool out there. I've extensively daily driven any one of them you can name, and ther…”
   • [community] “Cline is the most impressive agentic coder tool I've used and it seems to be getting better. I can plan with it for 10-15 minutes, set it lo…”
   • [community] “This is the golden tool that doesn't get the hype. Hope they can keep delivering. It seems to hit my personal sweet spot.”
   • [community] “I can have cline control a terminal command, it's by no means limited to editing code... I find Cline better [than Claude Code] (plus I can …”

   proof ↗⚑ 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. developerReview diffs visually and run multiple sessions side by side in a desktop app

   weight 2 · round drawn
   Cline✓fullclaimed8/10

   Cline ships a native desktop app (macOS/Windows) with a Kanban-style task board that runs multiple agent sessions in parallel with isolated git worktrees, and supports diff review with inline comments in card detail view; VS Code/JetBrains editors also show diffs for review, modify, or revert. missing for 10: no independent/hands-on review specifically confirming the desktop Kanban diff-review UX (community evidence covers IDE extension use, not the desktop app directly), and no detail on running truly side-by-side sessions within a single app window versus per-card views.

   • [claimed-docs] “Run many agents in parallel from a web-based task board with per-card worktrees, auto-commit, and dependency chains.”
   • [claimed-docs] “Use Cline Kanban to run multiple coding agents in parallel with isolated git worktrees.”
   • [claimed-docs] “Review diffs in card detail view and leave inline comments.”
   • [github] “Cline as a native app for macOS and Windows. Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP server…”
   • [github] “In VS Code and JetBrains, every edit shows up as a diff you can review, modify, or revert.”
   • [github] “Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP servers.”

   proof ↗⚑ flag

   Google Antigravity✓fullcommunity8/10

   Antigravity's desktop app (confirmed as a VSCode-style editor) ships a dedicated 'Review Changes' diff viewer with whitespace filtering and syntax-highlighted artifacts (antigravity-docs-33, -34, -30), plus explicit support for running multiple agents/sessions in parallel across independent projects and worktrees from one command center (antigravity-docs-1, -37, -38, -10). Missing for 10: independent hands-on confirmation of the side-by-side multi-session UI specifically (community evidence mostly discusses general bugs/instability rather than this feature directly).

   • [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] “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] “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…”
   • [claimed-docs] “Worktree support: Projects natively support Git worktrees, allowing agents to operate in isolated background folders.”
   • [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. engineering-leadManage multiple agent-driven coding sessions from one unified workspace

   weight 2 · round to Google Antigravity
   Cline✓fullclaimed7/10

   Cline Kanban is explicitly documented as a web-based task board for running many agents in parallel with per-card isolated git worktrees, auto-commit, dependency chains, and inline diff review—directly matching the engineering-lead's need to manage multiple agent-driven sessions from one unified workspace. This is reinforced by CLI scheduling (cron-based agents persisting independently) and subagents that run in parallel with their own context windows. Missing for 10: independent/hands-on community corroboration specifically of the Kanban multi-session workspace (community evidence only covers single-agent coding quality, not the Kanban feature), and no evidence on scaling limits or team-collaboration aspects of the shared workspace.

   • [claimed-docs] “Run many agents in parallel from a web-based task board with per-card worktrees, auto-commit, and dependency chains.”
   • [claimed-docs] “Use Cline Kanban to run multiple coding agents in parallel with isolated git worktrees.”
   • [claimed-docs] “Review diffs in card detail view and leave inline comments.”
   • [github] “Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP servers.”
   • [github] “Cline as a native app for macOS and Windows. Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP server…”
   • [claimed-docs] “Subagents let Cline spawn focused research agents that run in parallel.”
   • [claimed-docs] “Subagents let Cline spawn focused research agents that run in parallel. Each subagent gets its own prompt and context window, explores the c…”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [claimed-docs] “Run agents on cron schedules for recurring automations like daily summaries and code reviews.”

   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 to Cline
   Cline✓fullcommunity9/10

   Cline ships a dedicated CLI (npm install -g cline) supporting interactive terminal chat, headless automation, auto-approve flags, and live reaction to terminal output, well documented with concrete command examples and corroborated by community usage reports of terminal-based control. missing for 10: independent hands-on verification of the standalone CLI specifically (community evidence mostly covers the IDE extension, not the terminal CLI tool).

   • [claimed-docs] “Run Cline in your terminal with interactive chat or fully headless automation for CI/CD and scripting.”
   • [claimed-docs] “Use headless mode for scripts/automation and processable output.”
   • [claimed-docs] “Autonomous execution can modify files and run commands without further prompts.”
   • [claimed-docs] “Executes in your terminal and reacts to output as it appears. Long-running dev servers, tests, deploys, all handled live.”
   • [claimed-docs] “npm install -g cline”
   • [claimed-docs] “Use Cline CLI for interactive terminal sessions and automated headless workflows.”
   • [claimed-docs] “cline --auto-approve true "run tests and fix failures"”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [community] “I can have cline control a terminal command, it's by no means limited to editing code... I find Cline better [than Claude Code] (plus I can …”

   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 Cline
   Cline✓fullclaimed9/10

   Cline ships a documented CLI with explicit headless/non-interactive mode for scripts and CI/CD, auto-approve flags for unattended execution, pipeable I/O, and cron scheduling for recurring automations, plus explicit examples of running headlessly in GitHub Actions/GitLab pipelines. Missing for 10: independent (non-vendor) hands-on confirmation of headless CI usage specifically.

   • [claimed-docs] “Run Cline in your terminal with interactive chat or fully headless automation for CI/CD and scripting.”
   • [claimed-docs] “Use headless mode for scripts/automation and processable output.”
   • [claimed-docs] “Autonomous execution can modify files and run commands without further prompts.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub.”
   • [claimed-docs] “Chat with the agent from Slack, Discord, Telegram, or Linear. Run it headlessly inside GitHub Actions, GitLab, or any pipeline.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [claimed-docs] “cline --auto-approve true "run tests and fix failures"”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [claimed-docs] “Run agents on cron schedules for recurring automations like daily summaries and code reviews.”

   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 Cline
   Cline~partialprobed6/10

   Cline ships a full-featured CLI/headless mode (scripting, auto-approve, cron scheduling, ACP integration) that covers much of what the UI does, and docs emphasize scriptable automation for CI/CD. However, there is no documented REST/OpenAPI surface (probe found only 404s for openapi endpoints), and some UI-only features like the Kanban board's diff review/inline comments aren't shown to have CLI equivalents, so full UI/API parity isn't confirmed. missing for 10: a formal API/OpenAPI spec, explicit parity between Kanban UI actions (diff review, inline comments) and CLI/API, independent confirmation of complete feature equivalence.

   • [claimed-docs] “Use headless mode for scripts/automation and processable output.”
   • [claimed-docs] “Autonomous execution can modify files and run commands without further prompts.”
   • [claimed-docs] “Use Cline CLI for interactive terminal sessions and automated headless workflows.”
   • [claimed-docs] “cline --auto-approve true "run tests and fix failures"”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [claimed-docs] “Run agents on cron schedules for recurring automations like daily summaries and code reviews.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cline.bot/openapi.json, https://docs.cline.bot/swagger.json, https://docs.cline.bot/api…”
   • [claimed-docs] “Use Cline Kanban to run multiple coding agents in parallel with isolated git worktrees.”
   • [claimed-docs] “Review diffs in card detail view and leave inline comments.”

   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 to Cline
   Cline~partialclaimed4/10

   Cline documents that users are 'never locked into our platform or pricing' and can 'switch providers or self-host anytime' (cline-docs-15), plus BYOK/local-model support (cline-docs-27, cline-docs-41, cline-docs-42), which speaks to avoiding lock-in but is not the same as a documented data-export feature. There is no evidence of an explicit export function for task history, conversations, or configs in open formats. missing for 10: explicit data-export/backup feature, documentation of file formats used for stored history, independent confirmation of a 'leave with your data' workflow.

   • [claimed-docs] “You're never locked into our platform or pricing. Switch providers or self-host anytime.”
   • [claimed-docs] “Absolutely! You can bring your own API keys from providers like OpenAI, Anthropic, Google, and others.”
   • [claimed-docs] “Run Cline with local models using Ollama, LM Studio or Atomic Chat.”
   • [claimed-docs] “Bring Your Own Key (BYOK): use your own provider credentials (cloud or local runtimes).”

   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 Cline
   Cline~partialclaimed5/10

   The evidence confirms Cline's source code is hosted publicly on GitHub (cline/cline), which is strong circumstantial evidence of open availability, but none of the cited items state or link to an explicit open-source license (e.g., Apache/MIT) or licensing terms. missing for 10: explicit license text/citation, confirmation of license type, any docs page addressing licensing.

   • [github] “In VS Code and JetBrains, every edit shows up as a diff you can review, modify, or revert.”
   • [github] “Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP servers.”
   • [github] “Cline as a native app for macOS and Windows. Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP server…”

   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 to Cline
   Cline~partialclaimed6/10

   Cline is open source (VS Code extension, CLI installable via npm) and explicitly supports BYOK/local models (Ollama, LM Studio) and states you're 'never locked into our platform... self-host anytime,' which supports self-hosting the core agent/model layer. However, the evidence lacks concrete self-hosting instructions/docs for the Kanban web task-board, hub/scheduling backend, or a full self-hosted server deployment guide (e.g., Docker, on-prem server setup). missing for 10: dedicated self-hosting/deployment docs for the hub/Kanban/server components, independent confirmation of a full self-hosted stack beyond BYOK/local-model inference.

   • [claimed-docs] “You're never locked into our platform or pricing. Switch providers or self-host anytime.”
   • [claimed-docs] “Run Cline with local models using Ollama, LM Studio or Atomic Chat.”
   • [claimed-docs] “Bring Your Own Key (BYOK): use your own provider credentials (cloud or local runtimes).”
   • [claimed-docs] “npm install -g cline”
   • [claimed-docs] “Use Cline Kanban to run multiple coding agents in parallel with isolated git worktrees.”

   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 Cline
   Cline✓fullclaimed8/10

   Docs explicitly support BYOK (bring your own API key from OpenAI, Anthropic, Google, local runtimes) as an alternative to signing in with a Cline account for credits, and pricing page confirms users are never locked into platform login/pricing and can switch providers or self-host. Missing for 10: independent/hands-on confirmation of API-key-only auth flow and details on any limitations when skipping account login.

   • [claimed-docs] “Absolutely! You can bring your own API keys from providers like OpenAI, Anthropic, Google, and others.”
   • [claimed-docs] “Bring Your Own Key (BYOK): use your own provider credentials (cloud or local runtimes).”
   • [claimed-docs] “You're never locked into our platform or pricing. Switch providers or self-host anytime.”
   • [claimed-docs] “Instead of managing separate API keys across multiple vendors, you sign in once, add Cline credits, and select from available models directl…”

   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 drawn
   Cline—none0/10

   No evidence of SSO/SAML/OIDC enterprise identity integration, or cloud platform (AWS/Azure/GCP) IAM authentication; evidence only covers BYOK API keys, Cline account sign-in for credits, and local model auth. Missing for 10: SSO/SAML/OIDC support, enterprise directory integration, cloud IAM role-based auth, admin/team provisioning for compliance.

   • [claimed-docs] “Bring Your Own Key (BYOK): use your own provider credentials (cloud or local runtimes).”
   • [claimed-docs] “Instead of managing separate API keys across multiple vendors, you sign in once, add Cline credits, and select from available models directl…”
   • [claimed-docs] “Absolutely! You can bring your own API keys from providers like OpenAI, Anthropic, Google, and others.”

   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 drawn
   Cline—none0/10

   Cline's docs describe BYOK (bring-your-own API key), its own Cline account/credits system, and the ClinePass subscription, but there is no evidence of signing in with an existing third-party subscription (e.g., a Claude Pro/ChatGPT Plus plan) to authenticate and use the agent's entitlements.

   • [claimed-docs] “Bring Your Own Key (BYOK): use your own provider credentials (cloud or local runtimes).”
   • [claimed-docs] “Instead of managing separate API keys across multiple vendors, you sign in once, add Cline credits, and select from available models directl…”
   • [claimed-docs] “ClinePass is a low-cost monthly subscription — $9.99/month — that offers 2-5x the usage on popular open coding models compared to standard A…”

   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 Cline
   Cline~partialclaimed6/10

   Cline lets you sign in once and use Cline's account system instead of juggling per-provider API keys (cline-docs-43), and it periodically offers free model promotions with a limited usage quota without requiring your own key (cline-docs-45). However, the primary account-based path is credit-based (ClinePass at $9.99/mo or pay-as-you-go credits, cline-docs-44), so 'free-tier access' is only a limited promotional feature, not a durable no-cost tier. Missing for 10: independent confirmation of the free-tier's usage limits/duration, and clearer positioning of free access vs. paid credits as the default sign-in experience.

   • [claimed-docs] “Instead of managing separate API keys across multiple vendors, you sign in once, add Cline credits, and select from available models directl…”
   • [claimed-docs] “Cline periodically offers free model promotions that let you try select models at no cost, up to a limited usage quota.”
   • [claimed-docs] “ClinePass is a low-cost monthly subscription — $9.99/month — that offers 2-5x the usage on popular open coding models compared to standard A…”
   • [claimed-docs] “Absolutely! You can bring your own API keys from providers like OpenAI, Anthropic, Google, and others.”

   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
   Cline—none0/10

   Cline documents manual model configuration (separate models for Plan/Act, BYOK, ClinePass, free model promotions) but there is no evidence of an automatic 'best model for the task' selection or routing engine choosing models on the user's behalf.

   • [claimed-docs] “You can configure separate models for Plan and Act modes.”
   • [claimed-docs] “Absolutely! You can bring your own API keys from providers like OpenAI, Anthropic, Google, and others.”
   • [claimed-docs] “Bring Your Own Key (BYOK): use your own provider credentials (cloud or local runtimes).”
   • [claimed-docs] “Instead of managing separate API keys across multiple vendors, you sign in once, add Cline credits, and select from available models directl…”
   • [claimed-docs] “ClinePass is a low-cost monthly subscription — $9.99/month — that offers 2-5x the usage on popular open coding models compared to standard A…”

   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 Cline
   Cline✓fullcommunity9/10

   Cline explicitly supports multi-provider model choice: BYOK for OpenAI, Anthropic, Google and others, local models via Ollama/LM Studio, separate model selection per Plan/Act mode, a unified Cline provider to switch between hosted models, and explicit messaging that users are never locked into one provider/pricing. Community evidence corroborates local model (Ollama) and Gemini usage alongside Anthropic. Missing for 10: no independent benchmark of full provider parity/quality across all providers.

   • [claimed-docs] “Absolutely! You can bring your own API keys from providers like OpenAI, Anthropic, Google, and others.”
   • [claimed-docs] “Run Cline with local models using Ollama, LM Studio or Atomic Chat.”
   • [claimed-docs] “Bring Your Own Key (BYOK): use your own provider credentials (cloud or local runtimes).”
   • [claimed-docs] “Instead of managing separate API keys across multiple vendors, you sign in once, add Cline credits, and select from available models directl…”
   • [claimed-docs] “You can configure separate models for Plan and Act modes.”
   • [claimed-docs] “You're never locked into our platform or pricing. Switch providers or self-host anytime.”
   • [community] “I like cline... I was particularly surprised that it worked pretty well with local models... local model support is hit and miss [in other t…”
   • [community] “I can have cline control a terminal command, it's by no means limited to editing code... I find Cline better [than Claude Code] (plus I can …”
   • [community] “Cline also supposedly supports Ollama but it doesn't work that well with most models. There are some models dedicated to cline.”

   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
   Cline—none0/10

   The evidence describes BYOK, local model support (Ollama/LM Studio), and 'self-host anytime' claims, but nothing addresses explicit region/data-residency selection for where data is stored (e.g., choosing EU vs US storage for Cline's own cloud/credits service). This is a fair axis for an AI-native privacy-conscious user but no evidence shows such a control exists.

   • [claimed-docs] “You're never locked into our platform or pricing. Switch providers or self-host anytime.”
   • [claimed-docs] “Run Cline with local models using Ollama, LM Studio or Atomic Chat.”
   • [claimed-docs] “Bring Your Own Key (BYOK): use your own provider credentials (cloud or local runtimes).”

   proof ↗⚑ 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
   Cline—none0/10

   No evidence in the pack addresses data usage for AI model training, opt-out policies, zero-retention agreements, or any privacy/data-training controls for Cline. BYOK and self-hosting options (cline-docs-15, cline-docs-27, cline-docs-42) relate to provider flexibility, not to preventing training on user data.

   ⚑ 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
   Cline—none0/10

   The evidence pack covers BYOK, local model support, and self-hosting options, but contains no mention of data retention policies, conversation/history deletion controls, or telemetry opt-out mechanisms that would let a user control what data is retained or deleted.

   ⚑ 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
   Cline—none0/10

   No evidence in the pack mentions telemetry, usage tracking, analytics collection, or an opt-out/privacy setting for Cline; the docs cover BYOK, local models, and provider choice but not telemetry controls.

   ⚑ 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
   Cline—none0/10

   No evidence in the pack addresses data-retention or training-opt-out policies for code/prompts; while BYOK and self-host options are mentioned, none speak to model-training usage or an opt-out control.

   ⚑ 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 Cline
   Cline~partialclaimed5/10

   Cline can execute arbitrary terminal commands (including git operations) with human-in-the-loop or auto-approve, and Kanban explicitly mentions 'auto-commit' across worktrees, implying it stages and commits changes as part of its workflow. However, there's no explicit documentation of Cline authoring commit messages, creating branches, or opening pull requests as first-class features—this would rely on generic shell/terminal execution rather than a dedicated git/PR workflow. Missing for 10: explicit commit-message generation, branch creation, and PR-opening capability (e.g., via GitHub CLI integration) documented as a feature, plus independent evidence of it doing so successfully.

   • [claimed-docs] “Run many agents in parallel from a web-based task board with per-card worktrees, auto-commit, and dependency chains.”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [claimed-docs] “Executes in your terminal and reacts to output as it appears. Long-running dev servers, tests, deploys, all handled live.”
   • [github] “In VS Code and JetBrains, every edit shows up as a diff you can review, modify, or revert.”
   • [claimed-docs] “Coordinated multi-file changes with linter-aware fixes, diffs, checkpoints, and one-click undo on every step.”

   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 Cline
   Cline~partialclaimed4/10

   Cline can be scripted to review diffs (`git diff | cline "review these changes"`) and run headlessly inside GitHub Actions/GitLab pipelines or on cron schedules for 'recurring automations like...code reviews,' so a review workflow could be built. However there's no evidence of a dedicated PR-triggered bot/GitHub App that automatically posts contextual review comments on every pull request out of the box — it's a general agent that must be manually wired into CI. Missing for 10: a first-party PR-trigger integration (e.g., GitHub App/bot), evidence of automatic invocation on PR open/update, and evidence of posting inline contextual comments on PRs themselves.

   • [claimed-docs] “Chat with the agent from Slack, Discord, Telegram, or Linear. Run it headlessly inside GitHub Actions, GitLab, or any pipeline.”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [claimed-docs] “Run agents on cron schedules for recurring automations like daily summaries and code reviews.”
   • [claimed-docs] “Use headless mode for scripts/automation and processable output.”

   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 to Cline
   Cline✓fullclaimed8/10

   Cline shows every edit as a reviewable diff with modify/revert and one-click undo (cline-gh-1, cline-docs-30), supports piping diffs for review ('git diff | cline "review these changes"', cline-docs-34), can run tests/checks and auto-fix failures (cline-docs-33), and Kanban mode offers diff review with inline comments (cline-docs-47) — together covering diff inspection plus pre-merge checks. Missing for 10: independent/hands-on corroboration specifically validating the diff-review or check-running workflow (community evidence is general praise, not focused on this axis).

   • [github] “In VS Code and JetBrains, every edit shows up as a diff you can review, modify, or revert.”
   • [claimed-docs] “Coordinated multi-file changes with linter-aware fixes, diffs, checkpoints, and one-click undo on every step.”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [claimed-docs] “cline --auto-approve true "run tests and fix failures"”
   • [claimed-docs] “Review diffs in card detail view and leave inline comments.”

   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 Cline
   Cline~partialclaimed7/10

   Cline documents granular Auto Approve settings that let users decide which actions (file edits, terminal commands, browser actions, MCP tools) require approval versus running automatically, and MCP server configuration lets you add/remove which external tool integrations are available at all [cline-docs-21],[cline-docs-22],[cline-docs-38],[cline-docs-16],[cline-gh-2]. This gives meaningful control over tool/integration access, but evidence is all individual-developer-level settings with no organization-wide policy enforcement, role-based restriction, or admin console for an engineering-lead to mandate controls across a team. Missing for 10: team/org-level policy enforcement, audit logging of tool access decisions, and independent verification that these controls hold up in practice.

   • [claimed-docs] “Auto Approve lets you decide which actions Cline can take without prompting you each time.”
   • [claimed-docs] “YOLO mode is Auto Approve on steroids. Check the box and Cline auto-approves everything: file changes, terminal commands, browser actions, M…”
   • [claimed-docs] “Auto Approve lets you decide which actions Cline can take without prompting you each time. It keeps you out of approval popups during routin…”
   • [claimed-docs] “MCP (Model Context Protocol) lets Cline use external tools and data sources through MCP servers.”
   • [github] “Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP servers.”
   • [claimed-docs] “Use Cline Kanban to run multiple coding agents in parallel with isolated git worktrees.”

   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
   Cline—none0/10

   Cline's safety model is built around human-in-the-loop approval, diff review, checkpoints, and auto-approve settings (cline-docs-1, cline-docs-21, cline-docs-30), not sandboxed execution of code/tools/network. Kanban worktrees provide git isolation for parallel agents (cline-docs-24) but this is not a sandbox for code/tool/network execution. No evidence of containerized, VM-based, or otherwise isolated runtime environment for agent actions.

   • [claimed-docs] “Auto Approve lets you decide which actions Cline can take without prompting you each time.”
   • [claimed-docs] “Coordinated multi-file changes with linter-aware fixes, diffs, checkpoints, and one-click undo on every step.”
   • [claimed-docs] “Use Cline Kanban to run multiple coding agents in parallel with isolated git worktrees.”
   • [claimed-docs] “Auto Approve lets you decide which actions Cline can take without prompting you each time. It keeps you out of approval popups during routin…”

   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
   Cline—none0/10

   No evidence anywhere in the pack of license detection, public-code/plagiarism matching, or provenance references for AI-suggested code; Cline's review features focus on diffs, checkpoints, and human approval, not license/originality attribution.

   ⚑ 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 drawn
   Cline—none0/10

   Cline's evidence shows general-purpose code editing, diff review, and command execution (e.g., 'git diff | cline review these changes'), but no dedicated feature for detecting, explaining, or auto-fixing security vulnerabilities (no SAST/CVE integration, security linting, or vulnerability-specific workflow is documented).

   ⚑ 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