Devin vs Google Antigravity

Agent access

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

   weight 2 · round drawn
   Devin✓fullprobed9/10

   Devin's own docs site serves llms.txt (HTTP 200, confirmed by probe) and per-page .md variants, and also supports AGENTS.md as an agent-oriented instructions standard, directly matching the story. Missing for 10: no independent/community confirmation that external agents have actually consumed llms.txt successfully.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.devin.ai/llms.txt # Devin Docs - [Desktop (100 pages)](https://docs.devin.ai/_llms/en/desktop.md):…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.devin.ai/get-started/devin-intro.md > ## Documentation Index > Fetch the complete documentation inde…”
   • [claimed-docs] “Devin supports AGENTS.md - a simple, open standard for providing context and instructions to AI agents.”

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

   Devin offers a full API for creating/managing sessions programmatically (including create_as_user_id for automation on behalf of users), a CLI with a --sandbox flag for OS-level isolated headless runs, and explicit CI/CD pipeline integration for responding to static analysis findings and PR checks, all supporting headless/automated usage without a human in the loop. Missing for 10: no independent/hands-on report specifically validating CI automation workflows end-to-end, and no explicit CI example (e.g., GitHub Actions snippet) beyond doc references.

   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”
   • [claimed-docs] “you can create sessions on behalf of any user in your organization using the create_as_user_id parameter”
   • [claimed-docs] “Integrate Devin into your CI/CD pipeline to respond to findings from static analysis tools like SonarQube, Fortify, or Veracode.”
   • [claimed-docs] “With Auto-Fix enabled, Devin automatically responds to code review comments, fixes flagged bugs, and iterates on CI failures — creating a cl…”
   • [claimed-docs] “The --sandbox flag runs the CLI with OS-level isolation, enforcing writable paths and deny rules at the operating-system level and optionall…”
   • [claimed-docs] “a local command-line coding agent with deep Devin Cloud integration”

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

   The evidence only documents Devin exposing its own MCP server so other agents/IDEs can call Devin's tools (session management, playbooks, knowledge, scheduling) — the reverse direction of this story. There is no evidence that a user can configure Devin itself to consume/plug in external MCP servers so Devin can use their tools.

   • [claimed-docs] “it gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [claimed-docs] “gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [probe] “official MCP server documented at https://docs.devin.ai/work-with-devin/devin-mcp”

   proof ↗⚑ flag

   Google Antigravity✓fullclaimed8/10

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

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

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round drawn
   Devin✓fullprobed8/10

   Devin has an official CLI ('Devin CLI, a local command-line coding agent with deep Devin Cloud integration') with documented usage examples and a sandbox flag for OS-level isolation, confirmed by both docs and probe. Missing for 10: independent/hands-on community verification of the CLI specifically (community evidence covers the web/session product, not CLI usage).

   • [claimed-docs] “Devin CLI, a local command-line coding agent with deep Devin Cloud integration.”
   • [claimed-docs] “devin -- check out this code and suggest a feasible, helpful feature”
   • [claimed-docs] “The --sandbox flag runs the CLI with OS-level isolation, enforcing writable paths and deny rules at the operating-system level and optionall…”
   • [claimed-docs] “a local command-line coding agent with deep Devin Cloud integration”
   • [probe] “official CLI documented at https://docs.devin.ai/cli/index”

   proof ↗⚑ flag

   Google Antigravity✓fullprobed8/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Devin
   Devin✓fullprobed8/10

   Devin ships a documented public API (docs-7) with session creation, org-level features like create_as_user_id (docs-8), plus a CLI and MCP server for programmatic/agentic control (docs-4, docs-6, probe-4, probe-5), directly enabling AI-native users to drive it programmatically. Missing for 10: a discoverable OpenAPI/swagger spec (probe-3 found 404s on all candidate paths) and independent hands-on corroboration of API usage.

   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”
   • [claimed-docs] “you can create sessions on behalf of any user in your organization using the create_as_user_id parameter”
   • [claimed-docs] “Devin CLI, a local command-line coding agent with deep Devin Cloud integration.”
   • [claimed-docs] “it gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [probe] “official MCP server documented at https://docs.devin.ai/work-with-devin/devin-mcp”
   • [probe] “official CLI documented at https://docs.devin.ai/cli/index”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.devin.ai/openapi.json, https://docs.devin.ai/swagger.json, https://docs.devin.ai/api/op…”

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

   Devin exposes a general API (devin-docs-7) and can act on behalf of a specified user via create_as_user_id (devin-docs-8), but there is no evidence of scoped/least-privilege API key or token issuance, role-based permission scopes, or credential-level restriction mechanisms for agent access.

   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”
   • [claimed-docs] “you can create sessions on behalf of any user in your organization using the create_as_user_id parameter”

   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
   Devin~partialprobed4/10

   Devin provides an API for integration (docs-7, docs-8) allowing developers to build applications and automate workflows, but the evidence never mentions dedicated official SDKs/client libraries (e.g., Python/JS packages), and probes for an OpenAPI spec that would back SDK generation all returned 404s (devin-probe-3). Missing for 10: named SDK packages in specific languages, SDK installation/usage docs, and a published OpenAPI/schema artifact confirming SDK-generation support.

   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”
   • [claimed-docs] “you can create sessions on behalf of any user in your organization using the create_as_user_id parameter”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.devin.ai/openapi.json, https://docs.devin.ai/swagger.json, https://docs.devin.ai/api/op…”

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

   No evidence in the pack mentions webhooks or event subscription mechanisms; Devin's API/MCP docs describe session creation and management but nothing about outbound webhook notifications for events.

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

   Devin generates insights/suggestions from a user's own codebase data via 'Ask Devin' (code structure/dependency Q&A), auto-generated DeepWiki documentation, and Devin Review's automated PR feedback, all built on repository indexing. Missing for 10: independent/hands-on validation of the quality of these AI-generated insights (community evidence covers general task execution issues, not this specific feature) and no benchmark of insight accuracy.

   • [claimed-docs] “Ask Devin can answer questions about code structure and dependencies, and help you scope and plan tasks before implementation.”
   • [claimed-docs] “Devin Review provides automated first-pass reviews on pull requests, checking for correctness and conformance with organizational best pract…”
   • [claimed-docs] “Use DeepWiki to navigate architecture and code with auto-generated documentation.”
   • [claimed-docs] “Indexing your repositories allows Devin to understand your codebase and enables powerful features like Ask Devin and DeepWiki”

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

   Devin explicitly supports background/autonomous execution: cloud sessions run in their own VM and 'keep going after you close your laptop' (devin-docs-13), MCP access includes 'scheduling' (devin-docs-6/23), the API lets you 'automate workflows' and create sessions programmatically (devin-docs-7/8), CI/CD integration triggers Devin on findings (devin-docs-19), and Auto-Fix creates a closed loop that iterates PRs 'without you in the loop' (devin-docs-18). This spans scheduled triggers, API-driven automation, and hands-off background operation. Missing for 10: independent/community verification that scheduled automations run reliably unattended, and more detail on a dedicated 'automation/schedule' UI beyond scattered doc mentions.

   • [claimed-docs] “The cloud session gets its own VM with a shell, browser, and full repo access, so it can keep going after you close your laptop.”
   • [claimed-docs] “it gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [claimed-docs] “gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”
   • [claimed-docs] “you can create sessions on behalf of any user in your organization using the create_as_user_id parameter”
   • [claimed-docs] “With Auto-Fix enabled, Devin automatically responds to code review comments, fixes flagged bugs, and iterates on CI failures — creating a cl…”
   • [claimed-docs] “Integrate Devin into your CI/CD pipeline to respond to findings from static analysis tools like SonarQube, Fortify, or Veracode.”
   • [claimed-docs] “Carve out independent tasks and run them simultaneously.”

   proof ↗⚑ flag

   Google Antigravity✓fullclaimed8/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Google Antigravity
   Devin~partialcommunity6/10

   Devin's core product is designed for task delegation — via Ask Devin, ticket assignment, Slack/Teams tagging, and a conversational IDE (devin-docs-1, devin-docs-3, devin-docs-24) — so the axis clearly applies and is well documented. However, hands-on community reports show real caveats: Devin can add extraneous unrequested changes it can't undo, gets stuck for long periods without asking for help, and requires active babysitting/session termination to get value (devin-comm-1, devin-comm-2, devin-comm-5), undercutting a fully seamless delegation experience. Missing for 10: independent verification that delegated tasks reliably complete without extraneous side-effects or getting stuck, and stronger corroboration beyond one HN thread.

   • [claimed-docs] “Ask Devin to tackle Linear/Jira tickets, implement entirely new features, repro and fix bugs, build internal tools, and more!”
   • [claimed-docs] “Devin is designed to be a conversational user interface, and allows you to follow and take over Devin's development process in the embedded …”
   • [claimed-docs] “Tag Devin on a Slack or Teams thread about a bug you're discussing with coworkers”
   • [community] “Trialed Devin, it's quite impressive when it understands code formatting and local test setup, but it always adds extraneous changes beyond …”
   • [community] “One thing that surprised me is there doesn't seem to be an 'ask for help' escape hatch in Devin - it would work away for literally days on a…”
   • [community] “I've learned to just click 'Terminate Session' immediately after spotting Devin doing something hopeless. I've managed to get real work done…”

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

   Devin is explicitly designed as a conversational agent: users assign tasks via natural language (Slack/Teams tagging, chat interface, CLI prompts like 'devin -- check out this code...'), and it interprets these into autonomous coding/dev actions across IDE, CLI, and cloud sessions. Community evidence corroborates it operates on natural-language task descriptions in practice, though with noted friction around scope creep and knowing when to stop. Missing for 10: independent benchmarking of NL command accuracy/robustness and richer detail on how ambiguous instructions are resolved.

   • [claimed-docs] “Ask Devin to tackle Linear/Jira tickets, implement entirely new features, repro and fix bugs, build internal tools, and more!”
   • [claimed-docs] “Tagging Devin on a Slack or Teams thread about a bug you're discussing with coworkers”
   • [claimed-docs] “Devin is designed to be a conversational user interface, and allows you to follow and take over Devin's development process in the embedded …”
   • [claimed-docs] “devin -- check out this code and suggest a feasible, helpful feature”
   • [claimed-docs] “Tag Devin on a Slack or Teams thread about a bug you're discussing with coworkers”
   • [community] “Trialed Devin, it's quite impressive when it understands code formatting and local test setup, but it always adds extraneous changes beyond …”
   • [community] “I've learned to just click 'Terminate Session' immediately after spotting Devin doing something hopeless. I've managed to get real work done…”

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

   Devin has a documented API (devin-docs-7) but a direct probe for a machine-readable OpenAPI/swagger spec returned 404 on all candidate paths, and no documentation item references a downloadable spec file.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.devin.ai/openapi.json, https://docs.devin.ai/swagger.json, https://docs.devin.ai/api/op…”
   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”

   proof ↗⚑ flag

   Google Antigravity—none0/10

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

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

   proof ↗⚑ flag

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

   weight 1 · round to Devin
   Devin~partialclaimed6/10

   Devin sessions run in isolated cloud VMs with their own shell/browser/full repo access, configurable environment blueprints for a 'known-good state,' and a CLI --sandbox flag enforcing OS-level write/network isolation, all of which support testing in isolated environments away from live infrastructure. However, there is no explicit documentation addressing production-data isolation or masking, or confirmation that these sandboxes are guaranteed free of production data. missing for 10: explicit statement on production-data separation/masking, independent hands-on confirmation that sandbox testing never touches production data.

   • [claimed-docs] “The cloud session gets its own VM with a shell, browser, and full repo access, so it can keep going after you close your laptop.”
   • [claimed-docs] “Configure it once, and every session boots into that known-good state.”
   • [claimed-docs] “The --sandbox flag runs the CLI with OS-level isolation, enforcing writable paths and deny rules at the operating-system level and optionall…”
   • [claimed-docs] “The `--sandbox` flag runs the CLI with OS-level isolation, enforcing writable paths and `deny` rules at the operating-system level”
   • [claimed-docs] “Outposts lets you run Devin sessions inside infrastructure you control — your own VMs, containers, Kubernetes clusters, or even a Mac Mini o…”
   • [claimed-docs] “Devin inspects your repository, figures out which tools, runtimes, and dependencies are needed, and generates the blueprint for you.”

   proof ↗⚑ flag

   Google Antigravity!disputedcontradicted4/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Devin—none0/10

   There's an API reference (devin-docs-7) and even an OpenAPI probe, but that probe found no OpenAPI spec (devin-probe-3), and no evidence anywhere mentions API versioning scheme or a documented deprecation policy for the API.

   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.devin.ai/openapi.json, https://docs.devin.ai/swagger.json, https://docs.devin.ai/api/op…”

   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 Google Antigravity
   Devin~partialcommunity5/10

   Devin's API supports programmatic session creation (including on behalf of other users) and docs explicitly encourage carving out independent tasks to run simultaneously, which together enable bulk-style automation across many tickets/items, but there is no dedicated 'bulk operations' or batch-processing feature documented, and community feedback raises concerns about reliability/oversight needed per session that would complicate true bulk workflows. Missing for 10: an explicit batch/bulk API endpoint or UI for processing many items in one request, and independent evidence of successful large-scale bulk runs.

   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”
   • [claimed-docs] “you can create sessions on behalf of any user in your organization using the create_as_user_id parameter”
   • [claimed-docs] “Carve out independent tasks and run them simultaneously.”
   • [claimed-docs] “Ask Devin to tackle Linear/Jira tickets, implement entirely new features, repro and fix bugs, build internal tools, and more!”
   • [community] “Trialed Devin, it's quite impressive when it understands code formatting and local test setup, but it always adds extraneous changes beyond …”

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

   Devin supports several built-in event-triggered automations — Auto-Fix responds automatically to PR review comments and CI failures, CI/CD integration triggers Devin off static-analysis findings (SonarQube/Fortify/Veracode), and MCP exposes 'scheduling' as a capability — but there's no evidence of a general-purpose, user-defined rules/webhook engine for arbitrary custom triggers. Missing for 10: documentation of a configurable custom-rule/webhook trigger system, details on the scheduling feature's flexibility, and independent confirmation that these automations work reliably as event triggers.

   • [claimed-docs] “With Auto-Fix enabled, Devin automatically responds to code review comments, fixes flagged bugs, and iterates on CI failures — creating a cl…”
   • [claimed-docs] “Integrate Devin into your CI/CD pipeline to respond to findings from static analysis tools like SonarQube, Fortify, or Veracode.”
   • [claimed-docs] “Enable Devin Review with Auto-Fix so Devin automatically responds to code review comments, fixe”
   • [claimed-docs] “it gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [claimed-docs] “gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”

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

   Devin's MCP docs mention 'scheduling' as one of the capabilities exposed to MCP-compatible agents, implying some scheduling functionality exists, but there is no dedicated documentation, UI, or examples describing recurring jobs, cron-like triggers, or workflow automation configuration. missing for 10: dedicated scheduling feature docs, examples of recurring/cron jobs, independent confirmation of scheduled workflows in practice.

   • [claimed-docs] “it gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [claimed-docs] “gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”

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

   The evidence shows Devin has knowledge, playbooks, and scheduling features but nothing about versioning, reviewing, or rolling back those automation configurations themselves; Devin Review/Auto-Fix pertains to PR code review, not to the automation definitions. Missing for 10: version history for playbooks/knowledge, a review workflow for automation changes, and a rollback mechanism for automations.

   ⚑ flag

   Google Antigravity—none0/10

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

   ⚑ flag

Background execution

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

   weight 2 · round to Devin
   Devin~partialcommunity7/10

   Devin's cloud sessions run in dedicated VMs with shell/browser/full repo access, can implement features, run tests, and continue autonomously after handoff, then present PRs for review (docs-1,13,17). However, community hands-on reports describe unreliable autonomy — extraneous breaking changes, inability to self-correct, and needing frequent human monitoring/termination — undercutting the 'build, test, demo end-to-end' promise. missing for 10: reliable independent verification of unattended end-to-end demo quality, and clearer evidence of a built-in demo/walkthrough artifact for reviewers beyond PR creation.

   • [claimed-docs] “Ask Devin to tackle Linear/Jira tickets, implement entirely new features, repro and fix bugs, build internal tools, and more!”
   • [claimed-docs] “The cloud session gets its own VM with a shell, browser, and full repo access, so it can keep going after you close your laptop.”
   • [claimed-docs] “Devin Review provides automated first-pass reviews on pull requests, checking for correctness and conformance with organizational best pract…”
   • [claimed-docs] “With Auto-Fix enabled, Devin automatically responds to code review comments, fixes flagged bugs, and iterates on CI failures — creating a cl…”
   • [community] “Trialed Devin, it's quite impressive when it understands code formatting and local test setup, but it always adds extraneous changes beyond …”
   • [community] “One thing that surprised me is there doesn't seem to be an 'ask for help' escape hatch in Devin - it would work away for literally days on a…”
   • [community] “I've learned to just click 'Terminate Session' immediately after spotting Devin doing something hopeless. I've managed to get real work done…”

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

   Devin runs tasks in isolated cloud VMs with full shell/browser/repo access that persist after the user disconnects, explicitly supporting long-running background work and parallel independent tasks, corroborated by community reports of multi-day autonomous runs. Missing for 10: independent third-party benchmarking of long-running task reliability/quality beyond anecdotal HN reports.

   • [claimed-docs] “The cloud session gets its own VM with a shell, browser, and full repo access, so it can keep going after you close your laptop.”
   • [claimed-docs] “Carve out independent tasks and run them simultaneously.”
   • [claimed-docs] “Configure it once, and every session boots into that known-good state.”
   • [claimed-docs] “Hand a task off to a cloud Devin session and keep working locally.”
   • [community] “One thing that surprised me is there doesn't seem to be an 'ask for help' escape hatch in Devin - it would work away for literally days on a…”
   • [community] “You can set a 'max work time' before Devin pauses so it won't go for days endlessly spending your credits. By default it's set to 10 credits…”

   proof ↗⚑ flag

   Google Antigravity~partialclaimed5/10

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

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

   proof ↗⚑ flag

Parallel agents

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

   weight 2 · round to Google Antigravity
   Devin~partialcommunity6/10

   Docs confirm parallel task execution ('Carve out independent tasks and run them simultaneously'), cloud sessions that persist after closing the laptop, and an API to spin up multiple sessions programmatically (including on behalf of other users), which together support a 'fleet of parallel long-running agents' story. However, community hands-on reports show real friction with the 'hours/days autonomous' claim: sessions can get stuck without an escape hatch, users must babysit and manually terminate sessions every 10-15 minutes, and there's a default max-work-time cap limiting unsupervised runtime. Missing for 10: independent verification of successful multi-day/multi-task fleets running unattended, and evidence addressing the reported lack of a reliable 'ask for help' escalation during long runs.

   • [claimed-docs] “Carve out independent tasks and run them simultaneously.”
   • [claimed-docs] “The cloud session gets its own VM with a shell, browser, and full repo access, so it can keep going after you close your laptop.”
   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”
   • [claimed-docs] “you can create sessions on behalf of any user in your organization using the create_as_user_id parameter”
   • [community] “One thing that surprised me is there doesn't seem to be an 'ask for help' escape hatch in Devin - it would work away for literally days on a…”
   • [community] “Devin does ask for help when it can't do something, but it really hates asking for help if it's a skill issue - it would prefer running in c…”
   • [community] “You can set a 'max work time' before Devin pauses so it won't go for days endlessly spending your credits. By default it's set to 10 credits…”
   • [community] “I've learned to just click 'Terminate Session' immediately after spotting Devin doing something hopeless. I've managed to get real work done…”

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

   Devin's docs mention running multiple independent tasks simultaneously (devin-docs-25) but this describes parallelizing different tasks, not running several parallel attempts of the SAME task to compare and choose the best result. No evidence describes a compare/choose-best-attempt workflow.

   • [claimed-docs] “Carve out independent tasks and run them simultaneously.”

   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 Google Antigravity
   Devin~partialcommunity6/10

   Devin supports trigger-based autonomous work (Slack/Teams tags, PR review comments, CI/CD/static-analysis findings) and Auto-Fix creates a closed loop that iterates on CI failures without a human in the loop, and MCP exposes 'scheduling' as a session capability, all suggesting some always-on/triggered agent operation. However there's no dedicated docs for cron-like recurring schedules, and community reports describe sessions needing frequent human monitoring/termination rather than fully unattended long-running maintenance. Missing for 10: explicit scheduling/cron configuration docs, independent evidence of reliable unattended multi-day maintenance loops, and confirmation that Auto-Fix/CI triggers work without human oversight in practice.

   • [claimed-docs] “it gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [claimed-docs] “With Auto-Fix enabled, Devin automatically responds to code review comments, fixes flagged bugs, and iterates on CI failures — creating a cl…”
   • [claimed-docs] “Integrate Devin into your CI/CD pipeline to respond to findings from static analysis tools like SonarQube, Fortify, or Veracode.”
   • [claimed-docs] “Tag Devin on a Slack or Teams thread about a bug you're discussing with coworkers”
   • [community] “One thing that surprised me is there doesn't seem to be an 'ask for help' escape hatch in Devin - it would work away for literally days on a…”
   • [community] “You can set a 'max work time' before Devin pauses so it won't go for days endlessly spending your credits. By default it's set to 10 credits…”

   proof ↗⚑ flag

   Google Antigravity✓fullcommunity7/10

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

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

   proof ↗⚑ flag

Debugging

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

   weight 1 · round to Devin
   Devin~partialclaimed6/10

   Devin's computer-use/desktop mode gives it a full browser and desktop environment (mouse, keyboard, screenshots) plus VPN access to internal services, and docs explicitly mention reproducing and fixing bugs, which together support interacting with and debugging a live running app. However, there's no explicit documentation of dev-tools-style debugging features (breakpoints, console/log inspection, network tracing) or a dedicated 'live app debugging' workflow, and community evidence doesn't corroborate this specific use case. Missing for 10: explicit live-debugging tooling (breakpoints/console/log inspection), independent hands-on confirmation of debugging a running app.

   • [claimed-docs] “Ask Devin to tackle Linear/Jira tickets, implement entirely new features, repro and fix bugs, build internal tools, and more!”
   • [claimed-docs] “Devin has access to a full desktop environment — not just a browser. It can move the mouse, click on UI elements, type on the keyboard, take…”
   • [claimed-docs] “Devin can connect to a VPN from inside its workspace, so sessions can reach internal services such as package registries, databases, and int…”
   • [claimed-docs] “The cloud session gets its own VM with a shell, browser, and full repo access, so it can keep going after you close your laptop.”

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

   Docs clearly support NL-driven debugging: 'repro and fix bugs', 'Ask Devin can answer questions about code structure...help you scope and plan tasks', and tagging Devin in Slack/Teams about a bug thread. However, hands-on community reports describe practical caveats—Devin adding extraneous changes it can't undo, getting stuck without escalating, requiring manual babysitting—that temper reliability for troubleshooting workflows. Missing for 10: independent benchmark/case study specifically on debugging accuracy, and resolution of the 'getting stuck on bugs' community complaint.

   • [claimed-docs] “Ask Devin to tackle Linear/Jira tickets, implement entirely new features, repro and fix bugs, build internal tools, and more!”
   • [claimed-docs] “Tagging Devin on a Slack or Teams thread about a bug you're discussing with coworkers”
   • [claimed-docs] “Ask Devin can answer questions about code structure and dependencies, and help you scope and plan tasks before implementation.”
   • [claimed-docs] “Tag Devin on a Slack or Teams thread about a bug you're discussing with coworkers”
   • [community] “Trialed Devin, it's quite impressive when it understands code formatting and local test setup, but it always adds extraneous changes beyond …”
   • [community] “One thing that surprised me is there doesn't seem to be an 'ask for help' escape hatch in Devin - it would work away for literally days on a…”
   • [community] “Devin does ask for help when it can't do something, but it really hates asking for help if it's a skill issue - it would prefer running in c…”

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

   Devin's docs explicitly describe taking Linear/Jira tickets and implementing full features, with Devin Review/Auto-Fix looping PRs toward merge-ready status without human involvement, covering the issue-to-PR pipeline end-to-end. However, hands-on community reports describe practical friction — extraneous unrelated changes that can break things, inability to easily undo them, and agents getting stuck for days rather than asking for help — casting doubt on how cleanly the 'complete' PR is delivered without oversight. Missing for 10: independent verification of a clean ticket→merged-PR flow without manual intervention, and resolution of the reported reliability/quality issues.

   • [claimed-docs] “Ask Devin to tackle Linear/Jira tickets, implement entirely new features, repro and fix bugs, build internal tools, and more!”
   • [claimed-docs] “Devin Review provides automated first-pass reviews on pull requests, checking for correctness and conformance with organizational best pract…”
   • [claimed-docs] “With Auto-Fix enabled, Devin automatically responds to code review comments, fixes flagged bugs, and iterates on CI failures — creating a cl…”
   • [claimed-docs] “Code migrations, refactors, and modernization”
   • [community] “Trialed Devin, it's quite impressive when it understands code formatting and local test setup, but it always adds extraneous changes beyond …”
   • [community] “One thing that surprised me is there doesn't seem to be an 'ask for help' escape hatch in Devin - it would work away for literally days on a…”
   • [community] “Devin does ask for help when it can't do something, but it really hates asking for help if it's a skill issue - it would prefer running in c…”
   • [community] “I've learned to just click 'Terminate Session' immediately after spotting Devin doing something hopeless. I've managed to get real work done…”

   proof ↗⚑ flag

   Google Antigravity—none0/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Google Antigravity
   Devin!disputedcontradicted5/10

   Devin's docs strongly claim end-to-end feature/bug implementation across a full repo (Linear/Jira tickets, multi-file fixes, code migrations) with full workspace/VM access [devin-docs-1, devin-docs-13, devin-docs-21, devin-docs-27], but hands-on community reports concretely contradict smooth delivery: it 'always adds extraneous changes beyond the task that can break other things, and can't undo those changes if asked' and required constant supervision/termination to get real work done [devin-comm-1, devin-comm-5], with another user noting it can run for days without an escape hatch when stuck [devin-comm-2]. Missing for 10: independent benchmark data on multi-file correctness, and resolution of the extraneous-change/undo failure mode reported by users.

   • [claimed-docs] “Ask Devin to tackle Linear/Jira tickets, implement entirely new features, repro and fix bugs, build internal tools, and more!”
   • [claimed-docs] “The cloud session gets its own VM with a shell, browser, and full repo access, so it can keep going after you close your laptop.”
   • [claimed-docs] “Code migrations, refactors, and modernization”
   • [claimed-docs] “Indexing your repositories allows Devin to understand your codebase and enables powerful features like Ask Devin and DeepWiki”
   • [community] “Trialed Devin, it's quite impressive when it understands code formatting and local test setup, but it always adds extraneous changes beyond …”
   • [community] “One thing that surprised me is there doesn't seem to be an 'ask for help' escape hatch in Devin - it would work away for literally days on a…”
   • [community] “I've learned to just click 'Terminate Session' immediately after spotting Devin doing something hopeless. I've managed to get real work done…”

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

   Docs show Devin is a general-purpose coding agent that can fix bugs, implement features, iterate on CI failures, respond to review comments (Auto-Fix), and handle code migrations/refactors/modernization, which plausibly covers lint fixes and CI-related work, but none of the docs explicitly mention writing tests, resolving merge conflicts, or updating dependencies as named capabilities. Community reports (devin-comm-1) also note Devin can introduce extraneous changes and struggles to cleanly undo them, tempering confidence in reliably delivering these specific maintenance tasks. Missing for 10: explicit documentation/evidence of test-writing, lint-fixing, merge-conflict resolution, and dependency-update workflows, plus independent hands-on confirmation of these specific tasks succeeding.

   • [claimed-docs] “Ask Devin to tackle Linear/Jira tickets, implement entirely new features, repro and fix bugs, build internal tools, and more!”
   • [claimed-docs] “With Auto-Fix enabled, Devin automatically responds to code review comments, fixes flagged bugs, and iterates on CI failures — creating a cl…”
   • [claimed-docs] “Integrate Devin into your CI/CD pipeline to respond to findings from static analysis tools like SonarQube, Fortify, or Veracode.”
   • [claimed-docs] “Code migrations, refactors, and modernization”
   • [community] “Trialed Devin, it's quite impressive when it understands code formatting and local test setup, but it always adds extraneous changes beyond …”

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

   No evidence anywhere in the pack that Devin accepts a sketch/image/PDF design as input and generates a working app from it; documentation focuses on text-based tasks, tickets, Slack threads, code review, and CLI/desktop environment features with no multimodal design-to-app capability mentioned.

   ⚑ flag

   Google Antigravity~partialclaimed4/10

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

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

   proof ↗⚑ flag

Codebase mapping

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

   weight 3 · round to Devin
   Devin✓fullclaimed7/10

   Devin explicitly indexes repositories to power 'Ask Devin' and 'DeepWiki', which answer questions about code structure and dependencies and help developers scope/plan where to start making changes, directly matching the story. missing for 10: independent/hands-on evidence validating DeepWiki/Ask Devin's accuracy on real codebases (community evidence only covers task execution, not codebase-understanding features).

   • [claimed-docs] “Use DeepWiki to navigate architecture and code with auto-generated documentation.”
   • [claimed-docs] “Ask Devin can answer questions about code structure and dependencies, and help you scope and plan tasks before implementation.”
   • [claimed-docs] “Indexing your repositories allows Devin to understand your codebase and enables powerful features like Ask Devin and DeepWiki”

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

   Docs describe repo indexing that lets Devin understand the codebase and power 'Ask Devin' and DeepWiki auto-generated architecture docs, directly enabling exploration/explanation of an unfamiliar codebase without manual file selection (devin-docs-27, devin-docs-15, devin-docs-16). No community evidence contradicts this specific capability. Missing for 10: independent/hands-on verification of codebase-mapping accuracy and no concrete example of DeepWiki output quality.

   • [claimed-docs] “Indexing your repositories allows Devin to understand your codebase and enables powerful features like Ask Devin and DeepWiki”
   • [claimed-docs] “Use DeepWiki to navigate architecture and code with auto-generated documentation.”
   • [claimed-docs] “Ask Devin can answer questions about code structure and dependencies, and help you scope and plan tasks before implementation.”

   proof ↗⚑ flag

   Google Antigravity~partialclaimed5/10

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

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

   proof ↗⚑ flag

Context management

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

   weight 2 · round to Devin
   Devin~partialclaimed5/10

   Devin supports persistent cross-session context via "Knowledge" (instructions referenced in all sessions), AGENTS.md, and environment blueprints that let every session boot into a known-good state, which enables some recall across sessions. However, these mechanisms are largely user-configured/onboarded rather than autonomously built by the agent from its own experience, and there's no evidence of automatic memory creation or recall behavior demonstrated in practice. Missing for 10: evidence the agent automatically extracts/updates memory from its own task experience without manual setup, and independent confirmation that recalled memory improves subsequent session performance.

   • [claimed-docs] “Knowledge is a collection of instructions and advice that Devin can reference in all sessions.”
   • [claimed-docs] “Devin supports AGENTS.md - a simple, open standard for providing context and instructions to AI agents.”
   • [claimed-docs] “Configure it once, and every session boots into that known-good state.”
   • [claimed-docs] “Indexing your repositories allows Devin to understand your codebase and enables powerful features like Ask Devin and DeepWiki”

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

   No evidence describes attaching or indexing multiple project directories/repositories within a single Devin session; docs discuss single-repo indexing, knowledge, and environment setup but not multi-directory context in one session.

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

   Devin explicitly supports AGENTS.md, an open standard for providing context and instructions to AI agents, plus a separate 'Knowledge' feature for instructions/advice referenced across all sessions, directly covering project-level coding standards/conventions. Missing for 10: independent/hands-on confirmation that these instructions are reliably followed in practice.

   • [claimed-docs] “Devin supports AGENTS.md - a simple, open standard for providing context and instructions to AI agents.”
   • [claimed-docs] “Knowledge is a collection of instructions and advice that Devin can reference in all sessions.”

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

   Docs explicitly claim Devin can 'repro and fix bugs' (devin-docs-1), use Ask Devin/DeepWiki to narrow root causes via codebase understanding (devin-docs-15, devin-docs-16, devin-docs-27), and verify fixes through CI iteration/Auto-Fix loops (devin-docs-18). However, hands-on community testimony reports Devin often adds extraneous changes beyond the task scope and cannot reliably undo them when asked, undermining clean verification of fixes (devin-comm-1), and lacks an escape hatch when stuck on root-cause diagnosis (devin-comm-2, devin-comm-3). Missing for 10: independent verification of successful bug reproduction/root-cause narrowing at scale, and resolution of the reported inability to cleanly revert unwanted changes during fix verification.

   • [claimed-docs] “Ask Devin to tackle Linear/Jira tickets, implement entirely new features, repro and fix bugs, build internal tools, and more!”
   • [claimed-docs] “Use DeepWiki to navigate architecture and code with auto-generated documentation.”
   • [claimed-docs] “Ask Devin can answer questions about code structure and dependencies, and help you scope and plan tasks before implementation.”
   • [claimed-docs] “With Auto-Fix enabled, Devin automatically responds to code review comments, fixes flagged bugs, and iterates on CI failures — creating a cl…”
   • [claimed-docs] “Indexing your repositories allows Devin to understand your codebase and enables powerful features like Ask Devin and DeepWiki”
   • [community] “Trialed Devin, it's quite impressive when it understands code formatting and local test setup, but it always adds extraneous changes beyond …”
   • [community] “One thing that surprised me is there doesn't seem to be an 'ask for help' escape hatch in Devin - it would work away for literally days on a…”
   • [community] “Devin does ask for help when it can't do something, but it really hates asking for help if it's a skill issue - it would prefer running in c…”

   proof ↗⚑ flag

   Google Antigravity~partialcommunity6/10

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

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

   proof ↗⚑ flag

Marketplace

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

   weight 1 · round to Google Antigravity
   Devin~partialclaimed6/10

   Devin supports several skill-like extension mechanisms — 'Knowledge' (persistent instructions/advice for all sessions), AGENTS.md for structured agent instructions, and 'Playbooks' exposed via MCP — plus an open-source 'Devin Handoff' explicitly described as a 'plugin and skill'. This gives developers real levers to encode specialized, reusable task behavior, but the docs don't show a dedicated skill-authoring UI/marketplace or detailed examples of building a complex custom skill, and there is no independent/community evidence confirming this works well in practice. Missing for 10: concrete examples/tutorials of authoring a non-trivial custom skill, a discoverable skills registry, and independent hands-on corroboration.

   • [claimed-docs] “Knowledge is a collection of instructions and advice that Devin can reference in all sessions.”
   • [claimed-docs] “Devin supports AGENTS.md - a simple, open standard for providing context and instructions to AI agents.”
   • [claimed-docs] “it gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [claimed-docs] “gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [claimed-docs] “Devin Handoff is an open-source plugin and skill that brings the same handoff workflow to any coding agent — Claude Code, Codex, Cursor, and…”

   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 Devin
   Devin~partialprobed4/10

   Devin exposes an MCP server so external MCP-compatible agents/IDEs can access its session management and tools, and its open-source 'Devin Handoff' plugin interoperates with other coding agents (Claude Code, Codex, Cursor), showing some cross-agent workflow integration. However there is no evidence of a partner/marketplace ecosystem of third-party agent apps being integrated into Devin's own workflows. Missing for 10: a documented partner-app marketplace or catalog, evidence of installing/configuring third-party agent apps within Devin, and any case study of an engineering-lead orchestrating partner-built agents through Devin.

   • [claimed-docs] “it gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [claimed-docs] “Devin Handoff is an open-source plugin and skill that brings the same handoff workflow to any coding agent — Claude Code, Codex, Cursor, and…”
   • [claimed-docs] “gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [probe] “official MCP server documented at https://docs.devin.ai/work-with-devin/devin-mcp”

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

   Devin offers building blocks for a team-wide source of truth — repo indexing that powers 'Ask Devin' and DeepWiki architecture docs, org-wide 'Knowledge' referenced in all sessions, and AGENTS.md support for shared context — which collectively let a lead centralize docs/repo knowledge for the team. However, there's no explicit product feature framed as a 'shared workspace' UI for team-wide docs/repo browsing outside of Devin's own agent sessions. Missing for 10: a dedicated shared workspace/knowledge-base product surface for humans to browse, independent evidence of teams using it as a collaborative source of truth, and clarity on cross-repo doc aggregation beyond per-session knowledge.

   • [claimed-docs] “Indexing your repositories allows Devin to understand your codebase and enables powerful features like Ask Devin and DeepWiki”
   • [claimed-docs] “Knowledge is a collection of instructions and advice that Devin can reference in all sessions.”
   • [claimed-docs] “Devin supports AGENTS.md - a simple, open standard for providing context and instructions to AI agents.”
   • [claimed-docs] “Use DeepWiki to navigate architecture and code with auto-generated documentation.”
   • [claimed-docs] “Devin inspects your repository, figures out which tools, runtimes, and dependencies are needed, and generates the blueprint for you.”

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

   Devin can be tagged in Slack/Teams threads and work Jira/Linear tickets, giving it direct workflow-tool integration, and its MCP server plus API enable further extension to other tools. However there is no explicit documented Google Drive integration, and no independent/hands-on corroboration of these integrations actually working in practice. missing for 10: Google Drive connector evidence, independent verification of Jira/Slack integration reliability.

   • [claimed-docs] “Ask Devin to tackle Linear/Jira tickets, implement entirely new features, repro and fix bugs, build internal tools, and more!”
   • [claimed-docs] “Tagging Devin on a Slack or Teams thread about a bug you're discussing with coworkers”
   • [claimed-docs] “Tag Devin on a Slack or Teams thread about a bug you're discussing with coworkers”
   • [claimed-docs] “it gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”

   proof ↗⚑ flag

   Google Antigravity~partialclaimed5/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Devin
   Devin~partialclaimed6/10

   Docs confirm Devin can be invoked from Linear/Jira tickets and Slack/Teams threads, plus API integration for building custom workflow triggers, but there's no explicit mention of GitHub or GitLab issue/PR-based task kickoff in the evidence pack. Community evidence doesn't directly contradict the integration claims, only general effectiveness concerns. Missing for 10: explicit GitHub/GitLab-triggered task creation documentation, independent hands-on confirmation of these specific integrations working.

   • [claimed-docs] “Ask Devin to tackle Linear/Jira tickets, implement entirely new features, repro and fix bugs, build internal tools, and more!”
   • [claimed-docs] “Tagging Devin on a Slack or Teams thread about a bug you're discussing with coworkers”
   • [claimed-docs] “Tag Devin on a Slack or Teams thread about a bug you're discussing with coworkers”
   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”
   • [claimed-docs] “you can create sessions on behalf of any user in your organization using the create_as_user_id parameter”

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

   Devin's cloud sessions run in a dedicated VM that persists independent of the local device (docs-13), can be started from Slack/Teams, IDE, CLI, or API and continued/taken over in the embedded IDE or web UI (docs-3, docs-4, docs-7, docs-24), and Devin Handoff explicitly lets you start work locally and continue in a cloud session accessible from a browser (docs-38). missing for 10: no explicit first-party walkthrough of resuming the same session from a different browser/device login, and no independent/community confirmation of cross-device continuity.

   • [claimed-docs] “Devin is designed to be a conversational user interface, and allows you to follow and take over Devin's development process in the embedded …”
   • [claimed-docs] “Devin CLI, a local command-line coding agent with deep Devin Cloud integration.”
   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”
   • [claimed-docs] “The cloud session gets its own VM with a shell, browser, and full repo access, so it can keep going after you close your laptop.”
   • [claimed-docs] “Tag Devin on a Slack or Teams thread about a bug you're discussing with coworkers”
   • [claimed-docs] “Hand a task off to a cloud Devin session and keep working locally.”

   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. developerChat with the coding assistant directly inside my IDE for contextual help

   weight 3 · round to Google Antigravity
   Devin~partialclaimed5/10

   Devin exposes a conversational interface via its own embedded IDE within cloud sessions (devin-docs-3) and its Desktop app that imports VS Code/Cursor settings (devin-docs-9), plus an MCP server letting 'any MCP-compatible AI agent or IDE' access sessions (devin-docs-6/23). However there's no evidence of a native extension that lets a developer chat with Devin directly inside their own existing IDE (e.g., a VS Code/JetBrains plugin) — Devin's model is its own IDE/Desktop environment or MCP bridging rather than embedding in the user's IDE. Missing for 10: a first-party IDE extension for VS Code/JetBrains enabling in-IDE chat, and independent confirmation of this workflow working well in practice.

   • [claimed-docs] “Devin is designed to be a conversational user interface, and allows you to follow and take over Devin's development process in the embedded …”
   • [claimed-docs] “Import VS Code or Cursor settings, configure themes, and start coding with AI-powered assistance.”
   • [claimed-docs] “it gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [claimed-docs] “gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”

   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 to Google Antigravity
   Devin~partialclaimed4/10

   Devin has a documented Desktop app (docs-9) and supports running multiple independent sessions in parallel (docs-25), but there is no evidence of a visual diff review feature or explicit side-by-side session UI within the desktop app itself. Missing for 10: explicit documentation of an in-app diff viewer, UI showing multiple sessions simultaneously in one window, and any hands-on/community confirmation of this desktop workflow.

   • [claimed-docs] “Import VS Code or Cursor settings, configure themes, and start coding with AI-powered assistance.”
   • [claimed-docs] “Devin is designed to be a conversational user interface, and allows you to follow and take over Devin's development process in the embedded …”
   • [claimed-docs] “Carve out independent tasks and run them simultaneously.”

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

   Devin supports running multiple parallel sessions ('carve out independent tasks and run them simultaneously'), an API to create sessions on behalf of users, and an embedded IDE/CLI/desktop app to interact with sessions, which together enable a lead-like workspace for managing several agent sessions. However, there's no dedicated 'unified workspace' dashboard evidence for an engineering-lead specifically monitoring/managing a team's multiple concurrent sessions, and community feedback highlights session reliability issues that would complicate multi-session oversight. missing for 10: explicit multi-session dashboard/UI for a lead role, team-level session oversight features, independent corroboration of smooth multi-session management at scale.

   • [claimed-docs] “Carve out independent tasks and run them simultaneously.”
   • [claimed-docs] “you can create sessions on behalf of any user in your organization using the create_as_user_id parameter”
   • [claimed-docs] “Devin is designed to be a conversational user interface, and allows you to follow and take over Devin's development process in the embedded …”
   • [claimed-docs] “Devin CLI, a local command-line coding agent with deep Devin Cloud integration.”
   • [community] “Trialed Devin, it's quite impressive when it understands code formatting and local test setup, but it always adds extraneous changes beyond …”
   • [community] “I've learned to just click 'Terminate Session' immediately after spotting Devin doing something hopeless. I've managed to get real work done…”

   proof ↗⚑ flag

   Google Antigravity✓fullcommunity8/10

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

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

   proof ↗⚑ flag

Terminal workflow

1. developerRun a coding agent locally from my terminal

   weight 3 · round drawn
   Devin✓fullprobed8/10

   Devin CLI is explicitly documented as a local command-line coding agent that can be invoked from terminal (e.g. `devin -- check out this code...`), with local sandboxing (--sandbox flag) and deep integration with Devin Cloud for handoff. Missing for 10: independent/hands-on community verification specifically of the CLI experience (community evidence only covers the cloud/browser Devin product, not the local CLI).

   • [claimed-docs] “Devin CLI, a local command-line coding agent with deep Devin Cloud integration.”
   • [claimed-docs] “devin -- check out this code and suggest a feasible, helpful feature”
   • [claimed-docs] “a local command-line coding agent with deep Devin Cloud integration”
   • [claimed-docs] “The --sandbox flag runs the CLI with OS-level isolation, enforcing writable paths and deny rules at the operating-system level and optionall…”
   • [claimed-docs] “The `--sandbox` flag runs the CLI with OS-level isolation, enforcing writable paths and `deny` rules at the operating-system level”
   • [probe] “official CLI documented at https://docs.devin.ai/cli/index”

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

   Devin exposes a documented API for creating sessions programmatically (including on behalf of users) and explicit CI/CD pipeline integration to auto-respond to static-analysis findings, plus a CLI (`devin -- <prompt>`) that can be invoked headlessly, all pointing to non-interactive, scriptable automation. Missing for 10: independent/hands-on confirmation of headless CLI scripting in real CI pipelines and more detail on CLI exit codes/output for scripting.

   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”
   • [claimed-docs] “Integrate Devin into your CI/CD pipeline to respond to findings from static analysis tools like SonarQube, Fortify, or Veracode.”
   • [claimed-docs] “Devin CLI, a local command-line coding agent with deep Devin Cloud integration.”
   • [claimed-docs] “devin -- check out this code and suggest a feasible, helpful feature”
   • [claimed-docs] “With Auto-Fix enabled, Devin automatically responds to code review comments, fixes flagged bugs, and iterates on CI failures — creating a cl…”
   • [claimed-docs] “a local command-line coding agent with deep Devin Cloud integration”

   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 Devin
   Devin~partialprobed5/10

   Devin exposes a documented API (session creation, create_as_user_id) and an MCP server giving 'full access to session management, playbooks, knowledge, and scheduling', suggesting broad programmatic parity, but there's no explicit claim of full UI/API feature parity, and probes for an OpenAPI spec all 404'd, indicating the full API surface isn't transparently documented. Missing for 10: explicit parity statement covering UI-only features like Devin Review/Auto-Fix/Computer Use/desktop app settings, a discoverable OpenAPI schema, and independent confirmation that all UI actions are API-reachable.

   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”
   • [claimed-docs] “you can create sessions on behalf of any user in your organization using the create_as_user_id parameter”
   • [claimed-docs] “it gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [claimed-docs] “gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.devin.ai/openapi.json, https://docs.devin.ai/swagger.json, https://docs.devin.ai/api/op…”

   proof ↗⚑ flag

   Google Antigravity~partialprobed4/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Devin—none0/10

   No evidence of a data export feature or open-format export/portability mechanism for Devin sessions, knowledge, or artifacts; the docs cover API, CLI, MCP, and infrastructure but nothing about exporting all user data in open formats to leave the platform.

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

   Devin is a closed, proprietary commercial product; no evidence indicates its source code is available under an open license. The only mention of 'open-source' is for the separate Devin Handoff plugin/skill, not Devin itself.

   • [claimed-docs] “Devin Handoff is an open-source plugin and skill that brings the same handoff workflow to any coding agent — Claude Code, Codex, Cursor, and…”

   proof ↗⚑ flag

   Google Antigravity—none0/10

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

   ⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   Devin—none0/10

   Devin is a cloud-based SaaS agent; Outposts lets you run sessions on your own infrastructure but the core Devin model/orchestration itself remains Cognition-hosted, and there's no evidence of a self-hostable core product/model package. No mention of on-prem/self-hosted deployment of the core Devin engine.

   • [claimed-docs] “Outposts lets you run Devin sessions inside infrastructure you control — your own VMs, containers, Kubernetes clusters, or even a Mac Mini o…”

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

   Devin has a documented API (devin-docs-7) intended for programmatic integration, implying API key auth as an alternative to account login, and even supports creating sessions on behalf of other users (devin-docs-8), suggesting a service-level credential model. However, no explicit documentation of API key generation/management or authentication mechanics is present in the evidence pack. Missing for 10: explicit API key creation/management docs, confirmation that API key auth fully replaces login flows, and independent/community verification of this workflow.

   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”
   • [claimed-docs] “you can create sessions on behalf of any user in your organization using the create_as_user_id parameter”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.devin.ai/openapi.json, https://docs.devin.ai/swagger.json, https://docs.devin.ai/api/op…”

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

   No evidence of SSO/SAML, OIDC, or enterprise identity provider integration (e.g., Okta, Azure AD, Google Workspace) for authentication; the only related item is API session creation on behalf of a user, which is not enterprise identity/SSO authentication.

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

   The evidence describes Devin's own subscription tiers (Pro, Max, Core/Team/Enterprise) but nothing about letting a developer sign in using an existing external subscription (e.g., an existing LLM provider or IDE subscription) to access the agent. No mention of SSO-linked billing or bring-your-own-subscription support.

   • [claimed-docs] “Max is for individual users who consistently exceed the Pro quota. It includes everything in Pro, plus a significantly larger weekly usage q…”
   • [claimed-docs] “Power users who need more quota”

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

   Evidence only describes paid tiers (Pro, Max, 'power users who need more quota') and API key based integration; there's no mention of a free tier accessible via personal account sign-in without API key management.

   • [claimed-docs] “Max is for individual users who consistently exceed the Pro quota. It includes everything in Pro, plus a significantly larger weekly usage q…”
   • [claimed-docs] “Power users who need more quota”
   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”

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

   No evidence that Devin offers automatic model selection or model-routing based on task complexity; docs discuss quotas, tiers (Pro/Max), and features but never mention choosing among multiple underlying models per task.

   ⚑ flag

   Google Antigravity—none0/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Google Antigravity
   Devin—none0/10

   No evidence in the pack mentions selecting or switching between multiple underlying AI model providers (e.g., choosing between different LLMs) for a Devin session; documentation covers agent capabilities, environments, and billing tiers but not model selection.

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

   No evidence of data residency/region selection controls for where Devin stores data; the pack covers deployment options (Outposts, VPN, sandbox isolation) but nothing about choosing storage region/jurisdiction.

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

   The evidence pack contains no mention of data-training opt-out, data usage policy, or privacy controls for AI model training; nothing in the docs or community sources addresses this axis.

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

   No evidence pack items address data retention policies, data deletion controls, or privacy/data-handling settings for user data or session data; the closest items concern sandboxing/isolation of execution environments, not retention/deletion of stored data.

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

   No evidence pack item mentions telemetry opt-out, usage tracking settings, or privacy controls of that kind; the docs cover features, sandboxing, and infrastructure but not data-collection opt-out mechanisms.

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

   No evidence in the pack addresses data usage, training opt-out, or privacy/data-handling policies for Devin; nothing documents an opt-out mechanism for code/prompt use in model training.

   ⚑ 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 Devin
   Devin~partialcommunity6/10

   Devin's docs describe it implementing features/fixing bugs and producing pull requests that get automated review and iteration (devin-docs-17, devin-docs-18), implying it handles the full git workflow (branch, commit, PR) autonomously, but no doc explicitly details staging, commit-message generation, or branch creation as discrete steps. Community feedback (devin-comm-1) also notes it can add extraneous changes it can't cleanly undo, a real caveat on commit hygiene. Missing for 10: explicit documentation of commit/staging/branch mechanics and independent confirmation that generated commits/PRs are clean and reviewable.

   • [claimed-docs] “Ask Devin to tackle Linear/Jira tickets, implement entirely new features, repro and fix bugs, build internal tools, and more!”
   • [claimed-docs] “Devin Review provides automated first-pass reviews on pull requests, checking for correctness and conformance with organizational best pract…”
   • [claimed-docs] “With Auto-Fix enabled, Devin automatically responds to code review comments, fixes flagged bugs, and iterates on CI failures — creating a cl…”
   • [claimed-docs] “Carve out independent tasks and run them simultaneously.”
   • [community] “Trialed Devin, it's quite impressive when it understands code formatting and local test setup, but it always adds extraneous changes beyond …”

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

   Devin Review is explicitly documented as an automated first-pass PR reviewer checking correctness and org best-practice conformance, with Auto-Fix closing the loop by responding to review comments and CI failures. This directly matches the story of automatic contextual code review on PRs, though evidence is vendor-documentation only with no independent hands-on validation of review quality/contextual accuracy. Missing for 10: independent/community corroboration of review quality, and detail on how 'contextual feedback' is surfaced per-PR beyond docs description.

   • [claimed-docs] “Devin Review provides automated first-pass reviews on pull requests, checking for correctness and conformance with organizational best pract…”
   • [claimed-docs] “With Auto-Fix enabled, Devin automatically responds to code review comments, fixes flagged bugs, and iterates on CI failures — creating a cl…”
   • [claimed-docs] “Integrate Devin into your CI/CD pipeline to respond to findings from static analysis tools like SonarQube, Fortify, or Veracode.”
   • [claimed-docs] “Enable Devin Review with Auto-Fix so Devin automatically responds to code review comments, fixe”

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

   Devin's docs describe Devin Review, which performs automated first-pass PR reviews checking correctness and org conformance, plus CI/CD integration to respond to static-analysis findings (SonarQube, Fortify, Veracode) and Auto-Fix iterating on CI failures — directly enabling developers to inspect diffs and run checks before merge. This is corroborated by explicit SDLC integration workflow docs, not just a single mention. missing for 10: independent/hands-on evidence confirming Devin Review's diff-inspection quality in practice, and detail on how diffs are surfaced/inspected by the developer (UI specifics) beyond docs claims.

   • [claimed-docs] “Devin Review provides automated first-pass reviews on pull requests, checking for correctness and conformance with organizational best pract…”
   • [claimed-docs] “With Auto-Fix enabled, Devin automatically responds to code review comments, fixes flagged bugs, and iterates on CI failures — creating a cl…”
   • [claimed-docs] “Integrate Devin into your CI/CD pipeline to respond to findings from static analysis tools like SonarQube, Fortify, or Veracode.”
   • [claimed-docs] “Enable Devin Review with Auto-Fix so Devin automatically responds to code review comments, fixe”

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

   Devin exposes some admin-level controls over its access—an org-wide 'Enable desktop mode' toggle for Computer Use, a CLI --sandbox flag enforcing OS-level writable-path/deny rules and network restriction, and Outposts for running sessions in infra you control—giving leads levers to constrain what Devin can reach or do. However there's no documented centralized policy/allowlist for specific external integrations (e.g., disabling Slack, Jira, GitHub, VPN access per-tool) or granular permission/audit management for engineering leads. missing for 10: a unified integration-permission/allowlist admin panel, per-tool enable/disable controls beyond desktop mode, and independent verification of these controls in practice.

   • [claimed-docs] “Computer Use is controlled by the Enable desktop mode toggle in your organization's customization options.”
   • [claimed-docs] “The --sandbox flag runs the CLI with OS-level isolation, enforcing writable paths and deny rules at the operating-system level and optionall…”
   • [claimed-docs] “The `--sandbox` flag runs the CLI with OS-level isolation, enforcing writable paths and `deny` rules at the operating-system level”
   • [claimed-docs] “Outposts lets you run Devin sessions inside infrastructure you control — your own VMs, containers, Kubernetes clusters, or even a Mac Mini o…”
   • [claimed-docs] “Devin can connect to a VPN from inside its workspace, so sessions can reach internal services such as package registries, databases, and int…”

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

   Devin runs cloud sessions in isolated VMs (devin-docs-13) and provides an explicit CLI --sandbox flag enforcing OS-level isolation, writable path restrictions, deny rules, and optional network restriction (devin-docs-12, devin-docs-37), directly matching the sandboxed code/tool/network isolation story. Missing for 10: independent/hands-on verification of sandbox robustness and more detail on network isolation guarantees beyond docs claims.

   • [claimed-docs] “The --sandbox flag runs the CLI with OS-level isolation, enforcing writable paths and deny rules at the operating-system level and optionall…”
   • [claimed-docs] “The `--sandbox` flag runs the CLI with OS-level isolation, enforcing writable paths and `deny` rules at the operating-system level”
   • [claimed-docs] “The cloud session gets its own VM with a shell, browser, and full repo access, so it can keep going after you close your laptop.”
   • [claimed-docs] “Devin can connect to a VPN from inside its workspace, so sessions can reach internal services such as package registries, databases, and int…”

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

   No evidence of license or public-code matching/attribution references for AI-suggested code anywhere in the docs; Devin Review covers correctness and best-practice conformance but nothing about license/provenance matching.

   ⚑ flag

   Google Antigravity—none0/10

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

   ⚑ flag

2. developerGet contextual explanations and automatic fixes for security vulnerabilities

   weight 2 · round to Devin
   Devin✓fullclaimed7/10

   Devin's docs describe Devin Review giving automated PR reviews with explanations for correctness/best-practice issues, Auto-Fix automatically responding to review comments and fixing flagged bugs/CI failures, and CI/CD integration to respond to findings from security scanners like SonarQube, Fortify, and Veracode — directly matching contextual explanation plus automatic fixing of vulnerabilities. Missing for 10: independent/hands-on evidence specifically validating security-vulnerability fixes (community evidence only discusses general reliability/scope-creep issues, not security-fix accuracy).

   • [claimed-docs] “Devin Review provides automated first-pass reviews on pull requests, checking for correctness and conformance with organizational best pract…”
   • [claimed-docs] “With Auto-Fix enabled, Devin automatically responds to code review comments, fixes flagged bugs, and iterates on CI failures — creating a cl…”
   • [claimed-docs] “Integrate Devin into your CI/CD pipeline to respond to findings from static analysis tools like SonarQube, Fortify, or Veracode.”
   • [claimed-docs] “Ask Devin can answer questions about code structure and dependencies, and help you scope and plan tasks before implementation.”

   proof ↗⚑ flag

   Google Antigravity—none0/10

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

   ⚑ flag