Aider vs Google Antigravity

Agent access

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

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

   Probes explicitly show no llms.txt (404) and no machine-readable docs endpoints (404s for .md docs and openapi), and no evidence of agent-oriented docs formats elsewhere in the pack.

   • [probe] “PROBE llms.txt: HTTP 404 at https://aider.chat/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://aider.chat/docs/usage.html.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://aider.chat/openapi.json, https://aider.chat/swagger.json, https://aider.chat/api/openapi.jso…”

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

   Aider's scripting docs explicitly support headless/non-interactive use: `--message` for one-shot instructions that apply edits and exit, plus a Python API (`Coder.create`/`coder.run`) for programmatic/CI integration, alongside config via CLI switches, env vars, or .aider.conf.yml which suits automation pipelines. Community evidence corroborates interest in scriptable use (e.g., chaining PR review agents) though notes it's less commonly used that way. Missing for 10: no first-party CI/CD example (e.g., GitHub Actions workflow) or independent case study of Aider running fully unattended in a pipeline.

   • [claimed-docs] “Aider takes a `--message` argument, where you can give it a natural language instruction. It will do that one thing, apply the edits to the …”
   • [claimed-docs] “coder = Coder.create(main_model=model, fnames=fnames) # This will execute one instruction on those files and then return coder.run("make a …”
   • [claimed-docs] “aider --message "make a script that prints hello" hello.js”
   • [claimed-docs] “coder.run("make a script that prints hello world")”
   • [claimed-docs] “Aider has many options which can be set with command line switches. Most options can also be set in an `.aider.conf.yml` file... Or by setti…”
   • [community] “I only use Aider interactively, but I really should consider Aider in the 'scriptable' sense more... I might add another step after each PR …”

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

   No evidence in the pack that Aider supports connecting to MCP servers or using MCP-provided tools; its documented extensibility is via slash commands, scripting API, linters/tests, and web/voice input, not MCP.

   ⚑ flag

   Google Antigravity✓fullclaimed8/10

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

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

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Aider
   Aider✓fullprobed9/10

   Aider is itself a CLI tool, installed via pip/curl and driven entirely through command-line invocation, flags, scripting (--message), and config files/env vars, making it a native fit for AI-native, agentic workflows. missing for 10: independent third-party benchmarking of CLI robustness/versioning beyond docs and forum mentions.

   • [claimed-docs] “python -m pip install aider-install aider-install”
   • [claimed-docs] “curl -LsSf https://aider.chat/install.sh | sh”
   • [claimed-docs] “Aider takes a `--message` argument, where you can give it a natural language instruction. It will do that one thing, apply the edits to the …”
   • [claimed-docs] “Aider has many options which can be set with command line switches. Most options can also be set in an `.aider.conf.yml` file... Or by setti…”
   • [claimed-docs] “Aider has many options which can be set with command line switches. Most options can also be set in an .aider.conf.yml file... Or by setting…”
   • [probe] “official CLI documented at https://aider.chat/docs/usage.html”

   proof ↗⚑ flag

   Google Antigravity✓fullprobed8/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Aider~partialprobed6/10

   Aider documents a scriptable Python API (Coder.create/coder.run) and a CLI --message mode for programmatic, non-interactive driving, which serves as a public API surface for AI-native automation. However, probes confirm there is no REST/OpenAPI-style API or llms.txt (404s across all candidate endpoints), so 'documented public API' is limited to the Python scripting library and CLI flags rather than a formal service API. Missing for 10: a REST/HTTP or OpenAPI-documented API, and independent/hands-on validation of the scripting API in production use beyond docs.

   • [claimed-docs] “Aider takes a `--message` argument, where you can give it a natural language instruction. It will do that one thing, apply the edits to the …”
   • [claimed-docs] “coder = Coder.create(main_model=model, fnames=fnames) # This will execute one instruction on those files and then return coder.run("make a …”
   • [claimed-docs] “aider --message "make a script that prints hello" hello.js”
   • [claimed-docs] “coder.run("make a script that prints hello world")”
   • [probe] “PROBE llms.txt: HTTP 404 at https://aider.chat/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://aider.chat/docs/usage.html.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://aider.chat/openapi.json, https://aider.chat/swagger.json, https://aider.chat/api/openapi.jso…”

   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 userBuild against official SDKs

   weight 2 · round to Google Antigravity
   Aider~partialclaimed5/10

   Aider ships a documented Python scripting interface (Coder.create/coder.run) and a --message CLI mode that let developers build automation on top of it, which functions as a de facto SDK for AI-native workflows. However, there's no dedicated multi-language SDK, versioned package for third-party integration, or independent corroboration of building products atop it beyond docs. missing for 10: dedicated SDK package/versioning beyond scripting.html snippet, independent developer reports of building against it, multi-language SDK support.

   • [claimed-docs] “Aider takes a `--message` argument, where you can give it a natural language instruction. It will do that one thing, apply the edits to the …”
   • [claimed-docs] “coder = Coder.create(main_model=model, fnames=fnames) # This will execute one instruction on those files and then return coder.run("make a …”
   • [claimed-docs] “aider --message "make a script that prints hello" hello.js”
   • [claimed-docs] “coder.run("make a script that prints hello world")”

   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

Agentic features

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

   weight 2 · round to Aider
   Aider✓fullcommunity7/10

   Aider provides AI-generated code understanding, suggestions, and edits directly from the user's codebase via /ask, /architect, repo-map, and chat-based Q&A, with community reports confirming it effectively surfaces insights about unfamiliar codebases. missing for 10: no dedicated analytics/insights dashboard, no proactive suggestion surfacing beyond chat-driven queries, and independent evidence is limited to a single HN thread rather than broad corroboration.

   • [claimed-docs] “**/ask** Ask questions about the code base without editing any files.”
   • [claimed-docs] “**/map** Print out the current repository map”
   • [claimed-docs] “Aider uses a **concise map of your whole git repository** that includes the most important classes and functions along with their types and …”
   • [community] “I've used aider to understand new codebases using technologies I don't know and it did a fantastic job; much faster than grep/find + google.”
   • [community] “Aider can answer questions I can't search for via LSP, like 'what code would process the following URL' and similar.”

   proof ↗⚑ flag

   Google Antigravity~partialcommunity6/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Google Antigravity
   Aider~partialcommunity4/10

   Aider is fundamentally an interactive/scriptable pair-programming CLI, not a background automation scheduler; it can be invoked via --message or Python API for one-shot scripted runs, and community reports mention an experimental 'navigator-mode' adding autonomy akin to Claude Code, but there is no documented persistent background daemon, scheduler, or trigger-based autonomous execution. missing for 10: no first-party support for scheduled/triggered background jobs, no persistent autonomous loop or daemon mode, no evidence of unattended multi-step task execution without a human invoking a command each time.

   • [claimed-docs] “Aider takes a `--message` argument, where you can give it a natural language instruction. It will do that one thing, apply the edits to the …”
   • [claimed-docs] “coder = Coder.create(main_model=model, fnames=fnames) # This will execute one instruction on those files and then return coder.run("make a …”
   • [community] “I only use Aider interactively, but I really should consider Aider in the 'scriptable' sense more... I might add another step after each PR …”
   • [community] “Over the last two days, I've built out support for autonomy in Aider (a lot like Claude Code) that hybridizes with the rest of the app, uplo…”
   • [community] “It's... decidedly expensive to run an LLM this way right now (Gemini 2.5 Pro is your best bet) with Aider's navigator/autonomy mode, but cos…”

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

   Aider's entire product is built around delegating coding tasks to an LLM assistant via chat commands (/ask, /architect, /run, /test), CLI --message scripting, and a scriptable Python API (coder.run), with community confirming real-world delegation use (codebase Q&A, autonomous 'navigator mode'). Missing for 10: more independent benchmarking of task delegation reliability beyond anecdotal HN comments.

   • [claimed-docs] “Aider takes a `--message` argument, where you can give it a natural language instruction. It will do that one thing, apply the edits to the …”
   • [claimed-docs] “coder = Coder.create(main_model=model, fnames=fnames) # This will execute one instruction on those files and then return coder.run("make a …”
   • [claimed-docs] “**/ask** Ask questions about the code base without editing any files.”
   • [claimed-docs] “**/architect** Enter architect/editor mode using 2 different models. If no prompt provided, switches to architect/editor mode.”
   • [claimed-docs] “/ask Ask questions about the code base without editing any files. If no prompt provided, switches to ask mode.”
   • [claimed-docs] “You can configure aider to run your test suite after each time the AI edits your code using the --test-cmd <test-command> and --auto-test sw…”
   • [community] “I've used aider to understand new codebases using technologies I don't know and it did a fantastic job; much faster than grep/find + google.”
   • [community] “I revisited Aider a couple of days ago, after going in circles with AutoGPT - which seemed to either forget or go lazy after a few prompts. …”
   • [community] “Over the last two days, I've built out support for autonomy in Aider (a lot like Claude Code) that hybridizes with the rest of the app, uplo…”

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

   Aider is fundamentally natural-language driven: users type plain-English instructions in chat, via --message CLI flag, via voice command, or via #AI comments in watched files, and it executes edits accordingly, with community reports confirming real-world natural-language usage. missing for 10: no independent third-party benchmark of NL command robustness across edge cases, and some community reports note inconsistent quality/laziness in following instructions.

   • [claimed-docs] “Aider takes a `--message` argument, where you can give it a natural language instruction. It will do that one thing, apply the edits to the …”
   • [claimed-docs] “coder = Coder.create(main_model=model, fnames=fnames) # This will execute one instruction on those files and then return coder.run("make a …”
   • [claimed-docs] “Use the in-chat `/voice` command to start recording, and press `ENTER` when you’re done speaking. Your voice coding instructions will be tra…”
   • [claimed-docs] “AI! triggers aider to make changes to your code.”
   • [claimed-docs] “Rather than using /add to add a file inside the aider chat, you can simply put an #AI comment in it and save the file.”
   • [community] “I've used aider to understand new codebases using technologies I don't know and it did a fantastic job; much faster than grep/find + google.”
   • [community] “I revisited Aider a couple of days ago, after going in circles with AutoGPT - which seemed to either forget or go lazy after a few prompts. …”
   • [community] “Aider is the only tool I use for coding now with ChatGPT... It still suffers from ChatGPT laziness sometimes, you can see it retrying severa…”

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

   Aider is a CLI coding tool, not an API service, but the story asks about a downloadable machine-readable API spec; probes explicitly confirm no OpenAPI/swagger spec exists at any expected path and no llms.txt is served.

   • [probe] “PROBE llms.txt: HTTP 404 at https://aider.chat/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://aider.chat/docs/usage.html.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://aider.chat/openapi.json, https://aider.chat/swagger.json, https://aider.chat/api/openapi.jso…”

   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

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

   weight 2 · round to Google Antigravity
   Aider~partialclaimed5/10

   Aider's scripting API lets an AI-native user drive repeated `coder.run()` calls or `--message` invocations across many files/instructions programmatically, and multiple files can be added to a single chat session for combined edits, but there is no documented native bulk/batch command (e.g., apply-to-all, multi-repo loop) built into the CLI — bulk operation requires the user to write their own looping script. missing for 10: a first-party bulk/batch command or documented pattern for applying one operation across many items automatically, and independent evidence of successful large-scale bulk runs.

   • [claimed-docs] “Aider takes a `--message` argument, where you can give it a natural language instruction. It will do that one thing, apply the edits to the …”
   • [claimed-docs] “coder = Coder.create(main_model=model, fnames=fnames) # This will execute one instruction on those files and then return coder.run("make a …”
   • [claimed-docs] “aider --message "make a script that prints hello" hello.js”
   • [claimed-docs] “coder.run("make a script that prints hello world")”
   • [claimed-docs] “To edit files, you need to “add them to the chat”. Do this by naming them on the aider command line. Or, you can use the in-chat `/add` comm…”
   • [claimed-docs] “If you run aider with `--watch-files`, it will watch all files in your repo and look for any AI coding instructions you add using your favor…”

   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
   Aider~partialcommunity5/10

   Aider offers some built-in event-triggered automation: --watch-files lets AI!/AI? comments in files trigger actions, and --auto-test/--auto-lint automatically run after edits. However, these are fixed, predefined triggers rather than a general user-definable rules/automation engine (e.g., no custom event types, schedules, or webhook triggers). Missing for 10: user-defined custom rule/event definitions, broader trigger types beyond file-watch and post-edit, and independent evidence of reliability for these triggers.

   • [claimed-docs] “If you run aider with `--watch-files`, it will watch all files in your repo and look for any AI coding instructions you add using your favor…”
   • [claimed-docs] “AI! triggers aider to make changes to your code.”
   • [claimed-docs] “AI? triggers aider to answer your question.”
   • [claimed-docs] “Rather than using /add to add a file inside the aider chat, you can simply put an #AI comment in it and save the file.”
   • [claimed-docs] “You can configure aider to run your test suite after each time the AI edits your code using the --test-cmd <test-command> and --auto-test sw…”
   • [community] “Aider has a web mode and a 'watch mode', where you can use your normal editor and if you leave a comment like '# make this darker ai!', Aide…”

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

   Aider offers one-shot scripting (--message, Python API) but there is no evidence of any built-in scheduler, cron-like trigger, or recurring workflow orchestration feature; users would need external tooling (e.g., cron) not documented as part of Aider itself.

   • [claimed-docs] “Aider takes a `--message` argument, where you can give it a natural language instruction. It will do that one thing, apply the edits to the …”
   • [claimed-docs] “coder = Coder.create(main_model=model, fnames=fnames) # This will execute one instruction on those files and then return coder.run("make a …”
   • [claimed-docs] “aider --message "make a script that prints hello" hello.js”
   • [claimed-docs] “coder.run("make a script that prints hello world")”

   proof ↗⚑ flag

   Google Antigravity✓fullclaimed8/10

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

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

   proof ↗⚑ flag

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

   weight 1 · round to Aider
   Aider✓fullcommunity8/10

   Aider auto-commits every AI edit with a descriptive commit message, tags 'aider' as the author, supports /undo, /git for raw git history management, and lets users 'go back in git history to review the changes that aider made' — directly satisfying version/review/rollback for its automations. Community feedback confirms git-based commit behavior is real but criticizes commit message quality, a minor caveat rather than a contradiction of the core capability. Missing for 10: independent hands-on verification of rollback reliability across complex multi-file changes, and richer diff/review tooling beyond git log/git commands.

   • [claimed-docs] “Whenever aider edits a file, it commits those changes with a descriptive commit message. This makes it easy to undo or review aider’s change…”
   • [claimed-docs] “You can always use the `/undo` command to undo AI changes that you don’t like.”
   • [claimed-docs] “`/git` will let you run raw git commands to do more complex management of your git history.”
   • [claimed-docs] “Go back in the git history to review the changes that aider made to your code”
   • [claimed-docs] “If aider authored the changes in a commit, they will have “(aider)” appended to the git author and git committer name metadata.”
   • [community] “It gets commit messages wrong. Commit messages should signal intent, not what the patch does. 'changing an enum' is a horrible commit messag…”

   proof ↗⚑ flag

   Google Antigravity—none0/10

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

   ⚑ flag

Background execution

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

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

   Aider is a local CLI/library pair-programming tool run against your own repo (add files, /test, /run, scripting via Coder.run) with no evidence of a cloud-hosted agent that autonomously builds, tests, and demos a feature end-to-end for asynchronous review; even community mentions of an experimental 'navigator/autonomy mode' describe local execution, not a cloud agent with a demo/review flow.

   • [claimed-docs] “Aider takes a `--message` argument, where you can give it a natural language instruction. It will do that one thing, apply the edits to the …”
   • [claimed-docs] “You can run tests with `/test <test-command>`. Aider will run the test command without any arguments. If there are test errors, aider expect…”
   • [claimed-docs] “You can use the `/run` command in the chat to run your code and optionally share the output with aider.”
   • [community] “Over the last two days, I've built out support for autonomy in Aider (a lot like Claude Code) that hybridizes with the rest of the app, uplo…”
   • [community] “It's... decidedly expensive to run an LLM this way right now (Gemini 2.5 Pro is your best bet) with Aider's navigator/autonomy mode, but cos…”

   proof ↗⚑ flag

   Google Antigravity~partialcommunity6/10

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

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

   proof ↗⚑ flag

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

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

   Aider is a local CLI/scripting tool that runs synchronously in the developer's own environment (terminal, IDE, or scripted via Coder.create); there is no evidence of a cloud-hosted, isolated execution environment or background/async task delegation. Community notes only mention an experimental 'navigator-mode' autonomy feature, not cloud/background execution.

   • [claimed-docs] “Aider takes a `--message` argument, where you can give it a natural language instruction. It will do that one thing, apply the edits to the …”
   • [claimed-docs] “coder = Coder.create(main_model=model, fnames=fnames) # This will execute one instruction on those files and then return coder.run("make a …”
   • [community] “Over the last two days, I've built out support for autonomy in Aider (a lot like Claude Code) that hybridizes with the rest of the app, uplo…”
   • [community] “It's... decidedly expensive to run an LLM this way right now (Gemini 2.5 Pro is your best bet) with Aider's navigator/autonomy mode, but cos…”

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

   Aider is designed as a single-session CLI pair-programming tool driven interactively or via one-shot scripting (--message, coder.run); there is no evidence of orchestrating multiple parallel autonomous agents running for hours/days. Community mentions a third-party experimental 'navigator-mode' for autonomy, but this is not fleet/parallel multi-agent orchestration and is explicitly noted as costly/experimental, not a documented fleet-management capability.

   • [claimed-docs] “Aider takes a `--message` argument, where you can give it a natural language instruction. It will do that one thing, apply the edits to the …”
   • [claimed-docs] “coder = Coder.create(main_model=model, fnames=fnames) # This will execute one instruction on those files and then return coder.run("make a …”
   • [community] “Over the last two days, I've built out support for autonomy in Aider (a lot like Claude Code) that hybridizes with the rest of the app, uplo…”
   • [community] “It's... decidedly expensive to run an LLM this way right now (Gemini 2.5 Pro is your best bet) with Aider's navigator/autonomy mode, but cos…”

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

   Aider's docs describe a single interactive/scripted session per invocation (add files, /run, /test, scripting API) with no mechanism to launch multiple parallel attempts on a task or compare/select among them; one community comment even suggests a user 'might add' a review-and-compare step manually, implying it's not a built-in feature.

   • [community] “I only use Aider interactively, but I really should consider Aider in the 'scriptable' sense more... I might add another step after each PR …”
   • [claimed-docs] “Aider takes a `--message` argument, where you can give it a natural language instruction. It will do that one thing, apply the edits to the …”
   • [claimed-docs] “coder = Coder.create(main_model=model, fnames=fnames) # This will execute one instruction on those files and then return coder.run("make a …”

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

   Aider offers scripting (--message, Python API), file-watch mode triggered by in-file comments, and an experimental 'navigator-mode' for autonomy, but none of this constitutes an always-on agent that runs on schedules or external triggers to autonomously maintain/fix software; it remains an interactive/one-shot CLI tool invoked by a human or script.

   • [claimed-docs] “Aider takes a `--message` argument, where you can give it a natural language instruction. It will do that one thing, apply the edits to the …”
   • [claimed-docs] “If you run aider with `--watch-files`, it will watch all files in your repo and look for any AI coding instructions you add using your favor…”
   • [claimed-docs] “AI! triggers aider to make changes to your code.”
   • [community] “Over the last two days, I've built out support for autonomy in Aider (a lot like Claude Code) that hybridizes with the rest of the app, uplo…”
   • [community] “It's... decidedly expensive to run an LLM this way right now (Gemini 2.5 Pro is your best bet) with Aider's navigator/autonomy mode, but cos…”

   proof ↗⚑ flag

   Google Antigravity✓fullcommunity7/10

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

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

   proof ↗⚑ flag

Code completion

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

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

   Aider is a chat-driven CLI/git-based pair-programming tool; even its closest feature, --watch-files mode, only triggers edits when the user writes explicit '# ... ai!' comments and saves the file, not continuous ghost-text inline completions or next-edit suggestions as the developer types. No evidence describes an IDE-integrated inline completion/autocomplete experience.

   • [claimed-docs] “If you run aider with `--watch-files`, it will watch all files in your repo and look for any AI coding instructions you add using your favor…”
   • [claimed-docs] “AI! triggers aider to make changes to your code.”
   • [claimed-docs] “AI? triggers aider to answer your question.”
   • [claimed-docs] “Rather than using /add to add a file inside the aider chat, you can simply put an #AI comment in it and save the file.”

   proof ↗⚑ flag

   Google Antigravity~partialclaimed5/10

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

   • [claimed-docs] “Google Antigravity's Editor view offers tab autocompletion, natural language code commands, and a configurable, and context-aware configurab…”
   • [claimed-docs] “offers tab autocompletion, natural language code commands, and a configurable, and context-aware configurable agent”

   proof ↗⚑ flag

Debugging

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

   weight 1 · round to Google Antigravity
   Aider—none0/10

   Aider is a terminal/CLI coding assistant focused on editing files, running tests/lint, and running local commands via /run — there is no evidence of runtime debugging capabilities like attaching to a live process, inspecting running application state, browser devtools integration, or stepping through a live web app. The /web command only scrapes static pages, not live-app debugging.

   • [claimed-docs] “You can use the `/run` command in the chat to run your code and optionally share the output with aider.”
   • [claimed-docs] “You can run tests with `/test <test-command>`. Aider will run the test command without any arguments. If there are test errors, aider expect…”
   • [claimed-docs] “**/web** Scrape a webpage, convert to markdown and send in a message”

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

   Aider supports /ask mode for querying the codebase without editing, /run and /test to surface errors, /map to inspect repo structure, and community reports confirm it's used to understand and troubleshoot unfamiliar codebases via natural language ('what code would process this URL', faster than grep/google). missing for 10: no dedicated debugging/stack-trace-analysis workflow documented, no independent benchmark of troubleshooting accuracy, and some community reports note subtle errors requiring correction.

   • [claimed-docs] “**/ask** Ask questions about the code base without editing any files.”
   • [claimed-docs] “/ask Ask questions about the code base without editing any files. If no prompt provided, switches to ask mode.”
   • [claimed-docs] “You can use the `/run` command in the chat to run your code and optionally share the output with aider.”
   • [claimed-docs] “You can use the /run command in the chat to run your code and optionally share the output with aider.”
   • [claimed-docs] “**/map** Print out the current repository map”
   • [claimed-docs] “/map Print out the current repository map”
   • [community] “I've used aider to understand new codebases using technologies I don't know and it did a fantastic job; much faster than grep/find + google.”
   • [community] “Aider can answer questions I can't search for via LSP, like 'what code would process the following URL' and similar.”

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

   Aider's documented workflow covers editing files, committing changes locally with descriptive messages, and running tests/lint — but there is no evidence of reading a tracked issue (e.g., GitHub/GitLab issue) or automatically opening a pull request. It only performs local git commits (aider-docs-4, aider-docs-29) with no PR creation or issue-tracker integration mentioned anywhere in the pack.

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

   Aider's core documented workflow is exactly this: describe a change in natural language, it edits multiple files added to chat (or auto-detects which files to edit), commits changes, and community reports confirm it works well across real codebases including multi-file navigation/modification. Missing for 10: no rigorous independent benchmark of multi-file bug-fix accuracy beyond anecdotal HN reports, and community notes occasional errors/laziness with certain models.

   • [claimed-docs] “To edit files, you need to “add them to the chat”. Do this by naming them on the aider command line. Or, you can use the in-chat `/add` comm…”
   • [claimed-docs] “Aider takes a `--message` argument, where you can give it a natural language instruction. It will do that one thing, apply the edits to the …”
   • [claimed-docs] “You can use aider without adding any files, and it will try to figure out which files need to be edited based on your requests.”
   • [claimed-docs] “Whenever aider edits a file, it commits those changes with a descriptive commit message. This makes it easy to undo or review aider’s change…”
   • [community] “I've used aider to understand new codebases using technologies I don't know and it did a fantastic job; much faster than grep/find + google.”
   • [community] “I revisited Aider a couple of days ago, after going in circles with AutoGPT - which seemed to either forget or go lazy after a few prompts. …”
   • [community] “Big fan of Aider. We are interested in integrating Aider as a tool for Dosu to help it navigate and modify a codebase on issues.”

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

   Aider documents linting (auto-lint after edits), running tests via /test or --test-cmd/--auto-test, and general code editing that could write tests or resolve conflicts via natural language instructions, plus dependency-related edits are plausible through general file editing. However, there is no explicit, dedicated documentation or evidence for automated merge-conflict resolution or automated dependency-version updates as distinct workflows, and community evidence notes reliability issues (subtle errors, retries) that temper confidence in unattended correctness. missing for 10: explicit merge-conflict-resolution feature/docs, explicit dependency-update workflow/docs, independent hands-on evidence confirming these four tasks (tests, lint, merge conflicts, dependency updates) work reliably end-to-end.

   • [claimed-docs] “By default, aider will lint any files which it edits.”
   • [claimed-docs] “You can run tests with `/test <test-command>`. Aider will run the test command without any arguments. If there are test errors, aider expect…”
   • [claimed-docs] “You can configure aider to run your test suite after each time the AI edits your code using the --test-cmd <test-command> and --auto-test sw…”
   • [claimed-docs] “You can use the `/run` command in the chat to run your code and optionally share the output with aider.”
   • [claimed-docs] “Aider takes a `--message` argument, where you can give it a natural language instruction. It will do that one thing, apply the edits to the …”
   • [community] “I just tried it and it's amazingly cool, but the quality of the output just isn't there for me yet. It makes too much subtle errors to be as…”
   • [community] “Aider is the only tool I use for coding now with ChatGPT... It still suffers from ChatGPT laziness sometimes, you can see it retrying severa…”

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

   Aider docs confirm images and web pages can be added to chat for visual context (screenshots, reference docs), which could support sketch-driven coding, but there is no evidence of PDF input support or a dedicated 'generate app from design' workflow like dedicated design-to-code tools. missing for 10: PDF input support, an explicit end-to-end sketch/PDF-to-app workflow, and any hands-on example of this being done successfully.

   • [claimed-docs] “Add images and web pages to the chat to provide visual context, screenshots, reference docs, etc.”
   • [claimed-docs] “Aider works with most popular programming languages: python, javascript, rust, ruby, go, cpp, php, html, css, and dozens more.”

   proof ↗⚑ flag

   Google Antigravity~partialclaimed4/10

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

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

   proof ↗⚑ flag

Codebase mapping

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

   weight 3 · round to Aider
   Aider✓fullcommunity9/10

   Aider builds a repo map (concise summary of key classes/functions/signatures across the whole git repo) and offers `/map` and `/ask` commands to explore and understand a codebase without editing it, which directly supports finding where to start making changes; community testimonials corroborate this working well for unfamiliar codebases and languages. Missing for 10: no independent benchmark or deeper hands-on validation of repo-map accuracy on large/complex codebases.

   • [claimed-docs] “Aider uses a **concise map of your whole git repository** that includes the most important classes and functions along with their types and …”
   • [claimed-docs] “**/map** Print out the current repository map”
   • [claimed-docs] “**/ask** Ask questions about the code base without editing any files.”
   • [community] “I've used aider to understand new codebases using technologies I don't know and it did a fantastic job; much faster than grep/find + google.”
   • [community] “Aider can answer questions I can't search for via LSP, like 'what code would process the following URL' and similar.”
   • [community] “Aider is one of my favorite AI agents, especially because it can work with existing codebases. We've seen a lot of good results from folks w…”

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

   Aider builds an automatic repo map of the whole git repository without requiring manual file selection, and the /map and /ask commands let developers query and understand the codebase without editing files or adding them manually. Community reports corroborate this: users describe using aider to understand unfamiliar codebases in unfamiliar tech stacks faster than manual grep/search methods. Missing for 10: independent benchmark/quantitative evidence on very large codebases and more detail on repo-map scaling limits.

   • [claimed-docs] “Aider uses a **concise map of your whole git repository** that includes the most important classes and functions along with their types and …”
   • [claimed-docs] “Aider uses a concise map of your whole git repository that includes the most important classes and functions along with their types and call…”
   • [claimed-docs] “**/ask** Ask questions about the code base without editing any files.”
   • [claimed-docs] “/ask Ask questions about the code base without editing any files. If no prompt provided, switches to ask mode.”
   • [claimed-docs] “**/map** Print out the current repository map”
   • [claimed-docs] “/map Print out the current repository map”
   • [community] “I've used aider to understand new codebases using technologies I don't know and it did a fantastic job; much faster than grep/find + google.”
   • [community] “Aider can answer questions I can't search for via LSP, like 'what code would process the following URL' and similar.”

   proof ↗⚑ flag

   Google Antigravity~partialclaimed5/10

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

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

   proof ↗⚑ flag

Context management

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

   weight 2 · round drawn
   Aider—none0/10

   Aider's docs describe repo mapping, git-commit history, and chat commands, but there is no evidence of automatic persistent memory that is built and recalled across separate sessions — chat history logs and repo maps are not the same as cross-session memory recall. No first-party or community evidence describes such a feature.

   ⚑ 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
   Aider~partialcommunity4/10

   Aider's docs show you can add arbitrary files to a chat session via the CLI or `/add` command, which implicitly allows pulling files from outside the current directory, and it builds a repo map for whole-repository context. However, there is no explicit documentation or community evidence describing support for multiple separate project directories/repos in one session (e.g., cross-repo repomap or multi-root workspace). missing for 10: explicit multi-directory/multi-repo session support, evidence of repomap spanning more than one git repo, and confirmation that /add works across unrelated project roots.

   • [claimed-docs] “To edit files, you need to “add them to the chat”. Do this by naming them on the aider command line. Or, you can use the in-chat `/add` comm…”
   • [claimed-docs] “Aider uses a **concise map of your whole git repository** that includes the most important classes and functions along with their types and …”
   • [community] “I've used aider to understand new codebases using technologies I don't know and it did a fantastic job; much faster than grep/find + google.”

   proof ↗⚑ flag

   Google Antigravity✓fullclaimed8/10

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

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

   proof ↗⚑ flag

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

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

   The evidence pack documents aider's config file (.aider.conf.yml) for command-line options and repo-map features, but contains no mention of a dedicated project instructions/conventions file (e.g. CONVENTIONS.md or read-only context file) for setting coding standards that the agent follows. Absence of evidence for this applicable capability means it cannot be credited.

   • [claimed-docs] “Aider has many options which can be set with command line switches. Most options can also be set in an `.aider.conf.yml` file... Or by setti…”
   • [claimed-docs] “Aider has many options which can be set with command line switches. Most options can also be set in an .aider.conf.yml file... Or by setting…”

   proof ↗⚑ flag

   Google Antigravity✓fullclaimed7/10

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

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

   proof ↗⚑ flag

Issue diagnosis

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

   weight 3 · round to Aider
   Aider~partialcommunity7/10

   Aider provides tools that support this story indirectly: `/ask` for exploring the codebase without editing, the repo-map for navigating structure, `/run` and `/test`/`--auto-test` for executing code and test suites to reproduce and verify fixes, and community reports confirm it's effective for understanding unfamiliar codebases faster than manual search. However, there's no dedicated bug-reproduction or root-cause-analysis workflow beyond these general commands, and community feedback notes subtle errors and inconsistent output quality that could undermine verification confidence. Missing for 10: dedicated debugging/tracing tooling, explicit root-cause analysis features, and independent hands-on validation specifically of fix verification.

   • [claimed-docs] “**/ask** Ask questions about the code base without editing any files.”
   • [claimed-docs] “**/map** Print out the current repository map”
   • [claimed-docs] “You can run tests with `/test <test-command>`. Aider will run the test command without any arguments. If there are test errors, aider expect…”
   • [claimed-docs] “You can use the `/run` command in the chat to run your code and optionally share the output with aider.”
   • [claimed-docs] “You can configure aider to run your test suite after each time the AI edits your code using the --test-cmd <test-command> and --auto-test sw…”
   • [claimed-docs] “Aider uses a **concise map of your whole git repository** that includes the most important classes and functions along with their types and …”
   • [community] “I've used aider to understand new codebases using technologies I don't know and it did a fantastic job; much faster than grep/find + google.”
   • [community] “Aider can answer questions I can't search for via LSP, like 'what code would process the following URL' and similar.”
   • [community] “I just tried it and it's amazingly cool, but the quality of the output just isn't there for me yet. It makes too much subtle errors to be as…”

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

   No evidence of a skills/plugin system, custom tool definitions, or extension API in Aider's docs; it exposes built-in slash commands (/architect, /web, /run) but no mechanism for developers to add custom specialized skills.

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

   Aider is a CLI/library coding assistant; there is no evidence of an ecosystem for integrating third-party partner-built agent apps (no plugin marketplace, app store, or partner integrations documented) beyond one community mention of someone wanting to embed Aider itself as a tool inside another product (Dosu), which is the reverse relationship. No evidence Aider itself supports plugging in external partner agent apps.

   • [community] “Big fan of Aider. We are interested in integrating Aider as a tool for Dosu to help it navigate and modify a codebase on issues.”

   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

Tool integration

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

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

   Aider's documented features cover file editing, git integration, web scraping, and voice input, but there is no evidence of any integration with workflow tools like Jira, Slack, or Google Drive.

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

   No evidence of any GitHub/GitLab/Linear/Slack integration that lets users trigger Aider agent tasks from those platforms; Aider is a CLI/scriptable tool invoked locally or via its own scripting API, with no mention of issue-tracker or chat-platform triggers.

   ⚑ flag

   Google Antigravity—none0/10

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

   ⚑ flag

Cross device continuity

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

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

   Aider is a local CLI/git-based tool with an experimental local browser UI, but there's no evidence of any account, session, or cloud state that would let a user resume a task on a different device/browser—chat history and repo map are local to the machine running aider. Git commits persist code changes but don't constitute a portable 'continue where I left off' session across devices.

   • [claimed-docs] “Use aider’s new experimental browser UI to collaborate with LLMs to edit code in your local git repo.”
   • [claimed-docs] “Use aider's new experimental browser UI to collaborate with LLMs to edit code in your local git repo.”
   • [claimed-docs] “Whenever aider edits a file, it commits those changes with a descriptive commit message. This makes it easy to undo or review aider’s change…”
   • [claimed-docs] “Aider uses a **concise map of your whole git repository** that includes the most important classes and functions along with their types and …”

   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
   Aider~partialcommunity5/10

   Aider is fundamentally a terminal/CLI chat tool, but its --watch-files mode lets developers trigger AI edits from within their own IDE/editor by leaving '# ... ai!' comments, which the docs frame as IDE-integrated workflow. There's no evidence of a native embedded chat panel or official IDE extension providing conversational context inside the editor itself. missing for 10: dedicated IDE plugin/panel for direct chat, evidence of contextual chat UI inside an IDE rather than terminal+file-watch workaround.

   • [claimed-docs] “If you run aider with `--watch-files`, it will watch all files in your repo and look for any AI coding instructions you add using your favor…”
   • [claimed-docs] “AI! triggers aider to make changes to your code.”
   • [claimed-docs] “AI? triggers aider to answer your question.”
   • [claimed-docs] “Rather than using /add to add a file inside the aider chat, you can simply put an #AI comment in it and save the file.”
   • [community] “Aider has a web mode and a 'watch mode', where you can use your normal editor and if you leave a comment like '# make this darker ai!', Aide…”

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

   Aider is a CLI/terminal tool (with an experimental browser UI for chat), not a desktop app with visual diff review or multi-session side-by-side management; evidence shows no such GUI capability. Missing for 10: any desktop application, visual diff viewer, or multi-session UI evidence.

   • [claimed-docs] “Use aider’s new experimental browser UI to collaborate with LLMs to edit code in your local git repo.”
   • [claimed-docs] “Use aider's new experimental browser UI to collaborate with LLMs to edit code in your local git repo.”

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

   Aider is a single-session CLI/terminal pair-programming tool; the evidence shows no unified workspace/dashboard for managing multiple concurrent agent sessions, no session orchestration, or multi-project management UI. It's designed for one developer driving one chat session at a time in a repo, with no evidence of a workspace for engineering leads to oversee multiple agent sessions.

   ⚑ flag

   Google Antigravity✓fullcommunity8/10

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

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

   proof ↗⚑ flag

Terminal workflow

1. developerRun a coding agent locally from my terminal

   weight 3 · round to Aider
   Aider✓fullcommunity9/10

   Aider is a terminal-based coding assistant, installed via pip/curl script and run directly from the command line with rich in-chat commands, file editing, git integration, and local model support, all extensively documented and corroborated by hands-on community reports. Missing for 10: independent benchmarking of terminal UX quality and no first-party video/demo evidence beyond docs and forum posts.

   • [claimed-docs] “python -m pip install aider-install aider-install”
   • [claimed-docs] “curl -LsSf https://aider.chat/install.sh | sh”
   • [claimed-docs] “To edit files, you need to “add them to the chat”. Do this by naming them on the aider command line. Or, you can use the in-chat `/add` comm…”
   • [claimed-docs] “Aider takes a `--message` argument, where you can give it a natural language instruction. It will do that one thing, apply the edits to the …”
   • [claimed-docs] “Aider has many options which can be set with command line switches. Most options can also be set in an `.aider.conf.yml` file... Or by setti…”
   • [community] “I revisited Aider a couple of days ago, after going in circles with AutoGPT - which seemed to either forget or go lazy after a few prompts. …”
   • [community] “Big fan of Aider. We are interested in integrating Aider as a tool for Dosu to help it navigate and modify a codebase on issues.”

   proof ↗⚑ flag

   Google Antigravity✓fullprobed8/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Aider
   Aider✓fullcommunity8/10

   Aider has a documented scripting mode with a --message flag to run one instruction non-interactively and exit, plus a Python API (Coder.create/coder.run) for programmatic/scripted invocation, both explicitly designed for automation workflows. missing for 10: independent hands-on evidence of scripted/CI usage at scale, and more detail on exit codes/error handling for pipeline integration.

   • [claimed-docs] “Aider takes a `--message` argument, where you can give it a natural language instruction. It will do that one thing, apply the edits to the …”
   • [claimed-docs] “coder = Coder.create(main_model=model, fnames=fnames) # This will execute one instruction on those files and then return coder.run("make a …”
   • [claimed-docs] “aider --message "make a script that prints hello" hello.js”
   • [claimed-docs] “coder.run("make a script that prints hello world")”
   • [community] “I only use Aider interactively, but I really should consider Aider in the 'scriptable' sense more... I might add another step after each PR …”

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

   Aider exposes a scripting/Python API (`Coder.create`/`coder.run`) and a `--message` CLI mode for programmatic single-instruction execution, but this is far narrower than the interactive chat/browser UI, which offers many features (e.g. /architect, /voice, /web, /map, /test, /run, /model, watch-files) not exposed through the scripting API. No REST/OpenAPI surface exists (confirmed 404s), so API parity with the UI is only partial. missing for 10: programmatic access to slash-commands like /architect, /voice, /web, /map, /test, /run via the scripting API; a documented REST/OpenAPI interface; independent confirmation of API-UI feature parity.

   • [claimed-docs] “Aider takes a `--message` argument, where you can give it a natural language instruction. It will do that one thing, apply the edits to the …”
   • [claimed-docs] “coder = Coder.create(main_model=model, fnames=fnames) # This will execute one instruction on those files and then return coder.run("make a …”
   • [claimed-docs] “aider --message "make a script that prints hello" hello.js”
   • [claimed-docs] “coder.run("make a script that prints hello world")”
   • [claimed-docs] “Use aider’s new experimental browser UI to collaborate with LLMs to edit code in your local git repo.”
   • [claimed-docs] “**/architect** Enter architect/editor mode using 2 different models. If no prompt provided, switches to architect/editor mode.”
   • [claimed-docs] “**/web** Scrape a webpage, convert to markdown and send in a message”
   • [claimed-docs] “Use the in-chat `/voice` command to start recording, and press `ENTER` when you’re done speaking. Your voice coding instructions will be tra…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://aider.chat/openapi.json, https://aider.chat/swagger.json, https://aider.chat/api/openapi.jso…”

   proof ↗⚑ flag

   Google Antigravity~partialprobed4/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Aider
   Aider~partialclaimed5/10

   Aider operates entirely on local files and git repos, committing all AI edits as standard git commits (plain text, open format) rather than locking data in a proprietary store, and config is a plain YAML file — so there's little vendor lock-in by design. However, there is no explicit documentation of a data-export feature, chat/session history format, or any messaging about portability/'leaving' the product. Missing for 10: explicit chat/session export documentation, statement on session data formats, and any first-party 'no lock-in/data portability' claim.

   • [claimed-docs] “Whenever aider edits a file, it commits those changes with a descriptive commit message. This makes it easy to undo or review aider’s change…”
   • [claimed-docs] “Whenever aider edits a file, it commits those changes with a descriptive commit message. This makes it easy to undo or review aider's change…”
   • [claimed-docs] “`/git` will let you run raw git commands to do more complex management of your git history.”
   • [claimed-docs] “/git will let you run raw git commands to do more complex management of your git history.”
   • [claimed-docs] “Aider has many options which can be set with command line switches. Most options can also be set in an `.aider.conf.yml` file... Or by setti…”
   • [claimed-docs] “Aider has many options which can be set with command line switches. Most options can also be set in an .aider.conf.yml file... Or by setting…”

   proof ↗⚑ flag

   Google Antigravity—none0/10

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

   ⚑ flag

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

   weight 2 · round drawn
   Aider—none0/10

   The evidence pack contains only usage/feature docs and community discussion of Aider's coding capabilities; none of the citations mention a public source repository, license, or any statement about open licensing. Without evidence of an accessible, openly-licensed source, this axis cannot be credited as delivered.

   ⚑ flag

   Google Antigravity—none0/10

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

   ⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to Aider
   Aider✓fullclaimed7/10

   Aider is a local CLI/Python tool installed via pip or a script, runs entirely on the user's machine, and can operate with fully local LLMs (Ollama or any OpenAI-compatible local endpoint), meaning the entire core product can be self-hosted with no vendor cloud dependency. missing for 10: explicit self-hosting/deployment guide (e.g. Docker/server setup), independent confirmation of running fully offline with local models, and discussion of self-hosting a team-shared instance

   • [claimed-docs] “python -m pip install aider-install aider-install”
   • [claimed-docs] “curl -LsSf https://aider.chat/install.sh | sh”
   • [claimed-docs] “Aider can work also with local models, for example using [Ollama]”
   • [claimed-docs] “Aider can work also with local models, for example using Ollama. It can also access local models that provide an Open AI compatible API.”
   • [claimed-docs] “Aider has many options which can be set with command line switches. Most options can also be set in an `.aider.conf.yml` file... Or by setti…”

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

   Aider's docs describe configuration via command-line switches, an `.aider.conf.yml` file, and environment variables like `AIDER_xxx`, which is the standard mechanism for supplying LLM provider API keys, and Aider has no account-login system of its own — it authenticates purely through provider API keys. However, the evidence pack never explicitly shows an API-key setup example or names an env var like OPENAI_API_KEY, so the authentication story is implied rather than directly documented. missing for 10: explicit documentation/example of setting an API key (e.g., OPENAI_API_KEY) and confirmation that no account-login alternative exists.

   • [claimed-docs] “Aider has many options which can be set with command line switches. Most options can also be set in an `.aider.conf.yml` file... Or by setti…”
   • [claimed-docs] “Aider has many options which can be set with command line switches. Most options can also be set in an .aider.conf.yml file... Or by setting…”
   • [claimed-docs] “Aider can work also with local models, for example using [Ollama]”
   • [claimed-docs] “Aider can work also with local models, for example using Ollama. It can also access local models that provide an Open AI compatible API.”

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

   Aider is a local CLI coding tool with no evidence of SSO/SAML, enterprise identity provider integration, or cloud-platform authentication for compliance; only API key based LLM auth is documented, which does not address enterprise identity/compliance needs.

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

   Aider is a BYO-API-key CLI tool that connects to LLM providers (or local models); there's no evidence of a subscription-based sign-in (e.g., ChatGPT Plus/Claude Pro login) to use Aider itself. No mention of OAuth/subscription sign-in flow anywhere in docs or community evidence.

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

   Aider is a local CLI tool requiring users to supply their own LLM API keys (or local models); there is no evidence of an account sign-in or free-tier hosted access mechanism. No mention of OAuth login, hosted free tier, or account-based access in any evidence.

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

   Aider lets users manually switch models via /model or choose two different models for architect/editor mode, but there is no evidence of any automatic selection of 'best model for each task' — the choice is always explicit and user-driven.

   • [claimed-docs] “During your chat you can switch models with the in-chat /model command.”
   • [claimed-docs] “**/architect** Enter architect/editor mode using 2 different models. If no prompt provided, switches to architect/editor mode.”
   • [claimed-docs] “/architect Enter architect/editor mode using 2 different models. If no prompt provided, switches to architect/editor mode.”

   proof ↗⚑ flag

   Google Antigravity—none0/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Aider✓fullcommunity8/10

   Aider explicitly supports switching models via the in-chat /model command and documents compatibility with OpenAI, Anthropic (Claude), Ollama, and other OpenAI-API-compatible local models; community threads confirm developers actively switching between GPT-4, Claude Opus, and Gemini within Aider. Minor friction is noted (e.g., a tokenizer error for a specific Claude alias, cost/latency tradeoffs across providers) but the core multi-provider capability is clearly delivered. Missing for 10: a comprehensive first-party list of all supported providers and independent benchmarking of switching reliability across the full provider set.

   • [claimed-docs] “During your chat you can switch models with the in-chat /model command.”
   • [claimed-docs] “Aider can work also with local models, for example using [Ollama]”
   • [claimed-docs] “Aider can work also with local models, for example using Ollama. It can also access local models that provide an Open AI compatible API.”
   • [community] “Have been having too many problems with the diffs from gpt-4-turbo in aider... if aider supports Opus then will switch.”
   • [community] “From the Aider blog post discussion: Claude 3 Opus and Sonnet are both slower and more expensive than OpenAI's models; you can get almost th…”
   • [community] “does anyone know how to run aider with claude 3 opus? aider --model anthropic/claude-3-opus gives ValueError: No known tokenizer for model: …”
   • [community] “It's... decidedly expensive to run an LLM this way right now (Gemini 2.5 Pro is your best bet) with Aider's navigator/autonomy mode, but cos…”

   proof ↗⚑ flag

   Google Antigravity✓fullcommunity8/10

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

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

   proof ↗⚑ flag

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

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

   No evidence in the pack addresses data usage/training opt-outs, privacy policy, or data retention controls for Aider or the LLM providers it connects to; Aider primarily relies on third-party LLM APIs whose training-data policies aren't documented here.

   ⚑ 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

2. ai-native userControl data retention and deletion

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

   The evidence pack covers usage, git integration, and LLM configuration but contains no mention of data retention, storage, or deletion policies for user code, chat history, or LLM interactions. While Aider is local-first (using git and local models), no docs address how conversation/data sent to LLM providers is retained or how a user can delete it.

   ⚑ 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

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

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

   No evidence in the pack addresses telemetry, usage tracking, or opt-out settings for Aider; documentation covers usage, git integration, config files, and models but nothing about analytics/telemetry controls. missing for 10: any mention of telemetry collection, privacy policy, or an opt-out flag/env var.

   ⚑ 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

Pr review

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

   weight 3 · round to Aider
   Aider~partialcommunity4/10

   Aider auto-commits every AI edit with a descriptive commit message and supports /git for raw git commands and git-history review/undo, covering the 'stage changes + commit messages' part of the story. However, there is no documented feature for creating branches or opening pull requests — these would require manual use of /git or external tools, and one community report even criticizes the quality of auto-generated commit messages. missing for 10: dedicated branch-creation workflow, native PR-opening capability, and evidence of reliable commit-message quality.

   • [claimed-docs] “Whenever aider edits a file, it commits those changes with a descriptive commit message. This makes it easy to undo or review aider’s change…”
   • [claimed-docs] “`/git` will let you run raw git commands to do more complex management of your git history.”
   • [claimed-docs] “Whenever aider edits a file, it commits those changes with a descriptive commit message. This makes it easy to undo or review aider's change…”
   • [claimed-docs] “Go back in the git history to review the changes that aider made to your code”
   • [claimed-docs] “/git will let you run raw git commands to do more complex management of your git history.”
   • [community] “It gets commit messages wrong. Commit messages should signal intent, not what the patch does. 'changing an enum' is a horrible commit messag…”

   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. developerInspect diffs and run checks to catch problems before merging

   weight 3 · round to Aider
   Aider✓fullcommunity8/10

   Aider auto-commits every change with a descriptive message, letting developers review diffs via normal git tooling and use /undo or /git to inspect or roll back history; it also supports linting by default, /test and --auto-test for running test suites, and /run for executing code before accepting changes. This directly covers inspecting diffs and running checks pre-merge. Missing for 10: no built-in diff viewer/PR-style review UI (relies on external git tools) and no independent hands-on corroboration of the review workflow specifically (one community comment notes users still bolt on separate review agents).

   • [claimed-docs] “Whenever aider edits a file, it commits those changes with a descriptive commit message. This makes it easy to undo or review aider’s change…”
   • [claimed-docs] “Whenever aider edits a file, it commits those changes with a descriptive commit message. This makes it easy to undo or review aider's change…”
   • [claimed-docs] “Go back in the git history to review the changes that aider made to your code”
   • [claimed-docs] “`/git` will let you run raw git commands to do more complex management of your git history.”
   • [claimed-docs] “/git will let you run raw git commands to do more complex management of your git history.”
   • [claimed-docs] “By default, aider will lint any files which it edits.”
   • [claimed-docs] “You can run tests with `/test <test-command>`. Aider will run the test command without any arguments. If there are test errors, aider expect…”
   • [claimed-docs] “You can configure aider to run your test suite after each time the AI edits your code using the --test-cmd <test-command> and --auto-test sw…”
   • [claimed-docs] “You can use the `/run` command in the chat to run your code and optionally share the output with aider.”
   • [community] “I only use Aider interactively, but I really should consider Aider in the 'scriptable' sense more... I might add another step after each PR …”

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

   Aider's docs describe config files, command-line switches, and model selection, but there is no evidence of a permissions/allowlist system for controlling which external tools, plugins, or integrations (e.g., MCP servers, web scraping, code execution) the agent may access. Given Aider does have features like /web, /run, and file editing that could pose access-control concerns, an engineering-lead's ability to gate these is a fair question, but no such control mechanism is documented.

   • [claimed-docs] “Aider has many options which can be set with command line switches. Most options can also be set in an `.aider.conf.yml` file... Or by setti…”
   • [claimed-docs] “**/web** Scrape a webpage, convert to markdown and send in a message”
   • [claimed-docs] “You can use the `/run` command in the chat to run your code and optionally share the output with aider.”

   proof ↗⚑ flag

   Google Antigravity!disputedcontradicted5/10

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

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

   proof ↗⚑ flag

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

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

   No evidence that Aider provides sandboxed execution for code, tools, or network interactions—docs describe git-based commit/undo safety nets, linting, and test running directly on the host, but nothing about containerization, sandboxing, or isolated execution environments; instead Aider runs commands, edits files, and executes tests directly in the local repo/environment.

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

   No evidence that Aider provides license compliance checks or public-code/match provenance detection for AI-suggested code; the docs cover editing, git commits, linting, and testing but nothing about license or code-matching references.

   ⚑ flag

   Google Antigravity—none0/10

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

   ⚑ flag

2. developerGet contextual explanations and automatic fixes for security vulnerabilities

   weight 2 · round drawn
   Aider—none0/10

   No evidence that Aider detects, explains, or auto-fixes security vulnerabilities; it is a general-purpose AI pair-programming/coding tool with linting/testing/git features, but no dedicated security-scanning or vulnerability-remediation capability is documented.

   ⚑ flag

   Google Antigravity—none0/10

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

   ⚑ flag