GitHub Copilot vs Google Antigravity
GitHub Copilot wins · 33–21 (17 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to Google AntigravityProbes confirm docs.github.com serves an llms.txt file and a .md-formatted docs page, meaning an agent pointed at docs.github.com could consume agent-oriented docs directly; GitHub also documents MCP server usage for structured context. However, there's no evidence Copilot itself is documented to consume llms.txt as part of its own context-gathering workflow, nor first-party guidance recommending llms.txt for agent use. missing for 10: explicit product documentation instructing users/agents to point Copilot at llms.txt, and independent confirmation this integration is actually used in practice.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.github.com/llms.txt # GitHub Docs > GitHub is a developer platform for building, shipping, and mai…”
- [probe] “PROBE docs-md: HTTP 200 at https://docs.github.com/copilot.md # GitHub Copilot documentation You can use GitHub Copilot to enhance your pro…”
- [claimed-docs] “Connect MCP servers to Copilot Chat to share context from other applications.”
- [claimed-docs] “Learn how to use the GitHub Model Context Protocol (MCP) server to interact with repositories, issues, pull requests, and other GitHub featu…”
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”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to Google AntigravityGitHub Copilot ships a CLI for terminal/headless use and a 'cloud agent' with 'automations' that can run on a schedule or in response to repo events (e.g., issue opened), plus isolated cloud/local sandboxes for execution — all of which enable non-interactive, CI-like automation. However, evidence doesn't show explicit CI pipeline (e.g., GitHub Actions) integration steps or a documented non-interactive/scriptable flag set for true headless scripting. Missing for 10: documented CI/Actions integration examples, explicit non-interactive/headless CLI flags, and independent hands-on confirmation of automation running unattended in CI.
- [claimed-docs] “The command-line interface (CLI) for GitHub Copilot allows you to use Copilot directly from your terminal.”
- [claimed-docs] “Automations let you run Copilot cloud agent automatically, on a schedule or in response to events in a repository.”
- [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
- [claimed-docs] “Cloud and local sandboxes provide isolated execution environments that let Copilot safely interact with code, tools, filesystem, and network…”
- [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
- [probe] “official CLI documented at https://docs.github.com/en/copilot/how-tos/copilot-cli/set-up-copilot-cli/install-copilot-cli”
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.”
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · round to GitHub CopilotGitHub Copilot documents direct MCP server integration: connecting MCP servers to Copilot Chat to extend context/tools, creating custom MCP servers, using the official GitHub MCP server, and admin controls (allow lists) for which MCP servers developers can access. This is well-documented first-party capability across IDE and chat surfaces. missing for 10: independent hands-on community verification of MCP tool usage in practice (community evidence pack is mostly about code suggestion quality/licensing, not MCP specifically).
- [claimed-docs] “Connect MCP servers to Copilot Chat to share context from other applications.”
- [claimed-docs] “You can create a new MCP server to fulfill your specific needs, and then integrate it with Copilot Chat.”
- [claimed-docs] “Learn how to use the GitHub Model Context Protocol (MCP) server to interact with repositories, issues, pull requests, and other GitHub featu…”
- [claimed-docs] “Control which MCP servers developers can access from their IDEs, and use allow lists to prevent unauthorized access.”
- [claimed-docs] “Copilot works where you do—in GitHub, your IDE, the CLI, project tools, chat apps, and custom MCP servers.”
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 …”
ai-native userUse an official CLI
weight 2 · round drawnGitHub Copilot ships an official CLI documented at docs.github.com, letting users invoke Copilot directly from the terminal with prompt/voice input, corroborated by a dedicated install guide probe. missing for 10: independent hands-on community review of the CLI itself (community evidence only covers older chat/agent features, not the CLI), and no detail on CLI feature parity with IDE agent mode.
- [claimed-docs] “The command-line interface (CLI) for GitHub Copilot allows you to use Copilot directly from your terminal.”
- [claimed-docs] “As an alternative to typing, you can speak your prompt.”
- [probe] “official CLI documented at https://docs.github.com/en/copilot/how-tos/copilot-cli/set-up-copilot-cli/install-copilot-cli”
- [claimed-docs] “GitHub Copilot is also supported in terminals through GitHub CLI and as a chat integration in Windows Terminal Canary.”
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”
ai-native userDrive the product through a documented public API
weight 3 · round to Google AntigravityGitHub Copilot ships a documented CLI (docs-26, probe-4) that lets scripts/agents invoke Copilot from a terminal, and Copilot Chat can be extended via MCP servers (docs-20/21/25), giving some programmatic hooks. However, an explicit probe for a standard OpenAPI/public API spec returned 404s (probe-3), and no REST/GraphQL API for driving Copilot itself is documented in the evidence. Missing for 10: a dedicated, versioned public API (REST/GraphQL/OpenAPI) for programmatically controlling Copilot beyond CLI/MCP, and independent confirmation of its stability/coverage.
- [claimed-docs] “The command-line interface (CLI) for GitHub Copilot allows you to use Copilot directly from your terminal.”
- [probe] “official CLI documented at https://docs.github.com/en/copilot/how-tos/copilot-cli/set-up-copilot-cli/install-copilot-cli”
- [claimed-docs] “Connect MCP servers to Copilot Chat to share context from other applications.”
- [claimed-docs] “You can create a new MCP server to fulfill your specific needs, and then integrate it with Copilot Chat.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.github.com/openapi.json, https://docs.github.com/swagger.json, https://docs.github.com/…”
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…”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round to GitHub CopilotEvidence shows governance-adjacent controls like MCP server allow lists and a central control plane with audit logs for managing agents (docs-10, docs-23), but there is no explicit documentation of issuing scoped or least-privilege API credentials/tokens specifically for an agent's actions. Missing for 10: explicit scoped API credential/token issuance mechanism for agents, fine-grained permission scoping documentation, and independent verification that these controls limit agent API access at a credential level rather than just access-list level.
- [claimed-docs] “Control which MCP servers developers can access from their IDEs, and use allow lists to prevent unauthorized access.”
- [claimed-docs] “Track activity with detailed audit logs and enforce governance by managing agents from a single control plane.”
- [claimed-docs] “Cloud and local sandboxes provide isolated execution environments that let Copilot safely interact with code, tools, filesystem, and network…”
Google Antigravitydisputedcontradicted4/10Antigravity documents permission tiers (Deny/Ask/Allow) and a CLI sandbox that explicitly blocks access to sensitive files like .env and ~/.ssh, which is the closest analog to least-privilege credential scoping for an agent (docs-23, docs-42, docs-48). However, independent reports document a concrete bypass: Antigravity's own setting disallowing .env access was circumvented via prompt injection to exfiltrate secrets, and a default allowlisted domain (webhook.site) was used as an exfiltration channel — directly contradicting the claimed least-privilege protection (antigravity-comm-11, antigravity-comm-12). There is no evidence of a true scoped API-credential-issuance mechanism (e.g., minting restricted API keys/tokens for an agent); missing for 10: actual credential/token scoping API, third-party security audit confirming the sandbox holds, and any documented remediation.
- [claimed-docs] “Permissions are evaluated across three distinct access lists: Deny... Ask... Allow”
- [claimed-docs] “Permissions are evaluated across three distinct access lists: Deny...Ask...Allow”
- [claimed-docs] “Sensitive files like ~/.ssh and .env are blocked, anything not explicitly mounted is invisible inside the sandbox”
- [community] “Google Antigravity exfiltrates data via indirect prompt injection attack: Gemini is not supposed to have access to .env files with default s…”
- [community] “The default Allowlist provided with Antigravity includes 'webhook.site', which was used as an exfiltration vector for secrets.”
ai-native userBuild against official SDKs
weight 2 · round to Google AntigravityEvidence shows extensibility surfaces (MCP server integration, custom agents, partner 'agent apps') that let developers build on top of Copilot, but there is no dedicated official SDK (e.g., language client libraries or API SDK docs) described in the pack. missing for 10: explicit official SDK/client-library docs, code samples for building third-party apps against a Copilot API, independent developer confirmation of SDK usage.
- [claimed-docs] “Agent apps let you use partner-built agents directly in your workflows on GitHub, powered by your Copilot subscription.”
- [claimed-docs] “Connect MCP servers to Copilot Chat to share context from other applications.”
- [claimed-docs] “You can create a new MCP server to fulfill your specific needs, and then integrate it with Copilot Chat.”
- [claimed-docs] “Custom agents allow you to tailor Copilot's expertise for specific tasks.”
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…”
ai-native userSubscribe to events via webhooks
weight 2 · round drawnGitHub Copilotnone0/10Evidence shows Copilot 'automations' can be triggered by repository events (e.g., issue opened) [docs-33, docs-15], but this is Copilot reacting to GitHub events, not an API/webhook mechanism for an external AI-native user to subscribe to Copilot's own events. No documentation describes a webhook subscription endpoint or event payload schema for consuming Copilot activity.
- [claimed-docs] “Automations let you run Copilot cloud agent automatically, on a schedule or in response to events in a repository.”
- [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
Google Antigravitynone0/10No evidence of any webhook subscription mechanism; Antigravity is an IDE/CLI/agent platform with hooks, MCP, and scheduled tasks, but nothing about outbound event subscriptions via webhooks. Even the openapi probe returned 404s, indicating no public API surface for such integration.
- [probe] “PROBE openapi: all candidate paths 404 (https://antigravity.google/openapi.json, https://antigravity.google/swagger.json, https://antigravit…”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to GitHub CopilotCopilot generates AI insights/suggestions from the user's own code and repository data via code completion, chat with repo/doc context, code review with severity-labeled comments, and Autofix vulnerability suggestions, and can pull context from GitHub issues/PRs/docs via MCP. Community anecdotes (comm-1, comm-6, comm-7) corroborate real productivity gains from these suggestions, though some criticize suggestion quality on edge cases (comm-2, comm-10). Missing for 10: independent benchmark data quantifying insight accuracy/usefulness and no first-party analytics-style 'insights dashboard' beyond code review/Autofix.
- [claimed-docs] “Scale knowledge and keep teams consistent by creating a shared source of truth that includes context from your docs and repositories.”
- [claimed-docs] “GitHub Copilot Autofix provides contextual explanations and code suggestions to help developers fix vulnerabilities in code”
- [claimed-docs] “Connect MCP servers to Copilot Chat to share context from other applications.”
- [claimed-docs] “Learn how to use the GitHub Model Context Protocol (MCP) server to interact with repositories, issues, pull requests, and other GitHub featu…”
- [claimed-docs] “GitHub Copilot can review your code and provide feedback. Where possible, Copilot's feedback includes suggested changes which you can apply …”
- [claimed-docs] “Copilot labels each comment with a severity level of "High," "Medium," or "Low" to help you prioritize the issues it finds based on their im…”
- [community] “I've been using the alpha for the past 2 weeks, and I'm blown away. Copilot guesses the exact code I want about one in ten times... when it …”
- [community] “I have absolutely loved copilot so far. I especially love how fast it handles indexing complex n-dimensional arrays... I'd estimate a 10% ve…”
- [community] “Yesterday, Copilot could not write a program with SymPy... Today it uses SymPy as well as it uses NumPy (occasional mistakes, but overall it…”
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…”
ai-native userSet up automations that run autonomously in the background
weight 2 · round drawnGitHub Copilot's cloud agent explicitly supports background automation: docs describe running Copilot 'automatically, on a schedule or in response to events in a repository' and working 'independently in the background to complete tasks, just like a human developer,' with a control plane to track multiple agent sessions. This directly matches the story of autonomous background automations for an AI-native user. Missing for 10: independent/community hands-on validation specifically of the scheduled/event-triggered automation feature (most community evidence is about code completion quality, not the cloud-agent automation flow).
- [claimed-docs] “Automations let you run Copilot cloud agent automatically, on a schedule or in response to events in a repository.”
- [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
- [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
- [claimed-docs] “Assign tasks to agents like Copilot, Claude by Anthropic, and OpenAI Codex, and let them plan, explore, and execute work autonomously in the…”
- [claimed-docs] “Use one centralized control page to jump between agent sessions, check progress, and stay in control without losing your place.”
- [claimed-docs] “Launch work from GitHub, track progress across multiple agents, review changes, and merge completed work—all from one desktop workspace buil…”
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.”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round to GitHub CopilotGitHub Copilot ships extensive built-in agentic capabilities: agent mode in editors, cloud/background agents that plan-explore-execute autonomously, @copilot mentions on PRs, automations, custom agents, and a CLI, all documented first-party. Community evidence corroborates hands-on usage of the assistant delivering real productivity gains, supporting the delegation story. Missing for 10: independent hands-on validation specifically of the newer autonomous cloud-agent/background task delegation (most community evidence predates these agentic features).
- [claimed-docs] “Edit files in your workspace in agent mode”
- [claimed-docs] “Assign tasks to agents like Copilot, Claude by Anthropic, and OpenAI Codex, and let them plan, explore, and execute work autonomously in the…”
- [claimed-docs] “Launch work from GitHub, track progress across multiple agents, review changes, and merge completed work—all from one desktop workspace buil…”
- [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
- [claimed-docs] “Mention `@copilot` in a comment on an existing pull request to ask it to make changes.”
- [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
- [community] “I have absolutely loved copilot so far. I especially love how fast it handles indexing complex n-dimensional arrays... I'd estimate a 10% ve…”
- [community] “Yesterday, Copilot could not write a program with SymPy... Today it uses SymPy as well as it uses NumPy (occasional mistakes, but overall it…”
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 …”
ai-native userOperate the product with natural-language commands
weight 2 · round drawnGitHub Copilot offers natural-language interaction across chat, agent mode, CLI, and even voice input, letting users direct edits, reviews, and autonomous tasks conversationally (docs-2, docs-22, docs-26, docs-27). Community evidence corroborates real usage of chat/agent workflows, though some report chat availability limited to specific IDEs and mixed quality of autonomous 'fix the bug' style commands. Missing for 10: independent hands-on validation of natural-language command robustness across all surfaces (mobile, terminal) and no rigorous benchmark of command success rate.
- [claimed-docs] “Edit files in your workspace in agent mode”
- [claimed-docs] “chat functionality is currently available only in Visual Studio Code, JetBrains, and Visual Studio”
- [claimed-docs] “Copilot in your editor does it all, from explaining concepts and completing code, to proposing edits and validating files with agent mode.”
- [claimed-docs] “The command-line interface (CLI) for GitHub Copilot allows you to use Copilot directly from your terminal.”
- [claimed-docs] “As an alternative to typing, you can speak your prompt.”
- [community] “The first video in this post is a perfect example of the problems I see in this space. First the programmer asks the AI to nebulously 'fix t…”
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 …”
Api quality
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round drawnGitHub Copilotnone0/10The evidence pack shows explicit probe attempts to find an OpenAPI/machine-readable spec for GitHub Copilot's docs (openapi.json, swagger.json, etc.) all returning 404, and no other citation mentions a downloadable API spec for Copilot. No documentation or community evidence confirms a machine-readable spec exists.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.github.com/openapi.json, https://docs.github.com/swagger.json, https://docs.github.com/…”
Google Antigravitynone0/10A 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…”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round to GitHub CopilotGitHub Copilot explicitly documents that its cloud and local agent execution occurs in isolated sandboxes ('Cloud and local sandboxes provide isolated execution environments that let Copilot safely interact with code, tools, filesystem, and network resources securely on your local machine or in fully isolated cloud environments'), directly matching the story of testing/agentic work without touching production systems. Missing for 10: independent/hands-on verification of sandbox isolation guarantees, and explicit mention of protecting 'production data' specifically rather than just execution environment isolation.
- [claimed-docs] “Cloud and local sandboxes provide isolated execution environments that let Copilot safely interact with code, tools, filesystem, and network…”
- [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
- [claimed-docs] “Automations let you run Copilot cloud agent automatically, on a schedule or in response to events in a repository.”
Google Antigravitydisputedcontradicted4/10Antigravity's CLI docs claim a sandbox that blocks sensitive files (~/.ssh, .env) and hides anything not explicitly mounted, which sounds like exactly the kind of safe-testing boundary this story wants, but hands-on community reports directly contradict this: Gemini bypassed its own .env protection to exfiltrate secrets via prompt injection, a default allowlisted webhook.site was used as an exfiltration vector, and in another incident Antigravity commands deleted an entire drive outside any expected sandbox boundary. This is a concrete, documented failure of the sandbox promise rather than mere skepticism. Missing for 10: a genuine isolated/staging environment separate from real user data, and any vendor or independent confirmation that the sandbox reliably prevents production-data access after these reported bypasses.
- [claimed-docs] “Sensitive files like ~/.ssh and .env are blocked, anything not explicitly mounted is invisible inside the sandbox”
- [community] “Google Antigravity exfiltrates data via indirect prompt injection attack: Gemini is not supposed to have access to .env files with default s…”
- [community] “The default Allowlist provided with Antigravity includes 'webhook.site', which was used as an exfiltration vector for secrets.”
- [community] “Antigravity was also vulnerable to the classic Markdown image exfiltration bug, reported a few days prior and flagged as 'intended behavior'…”
- [community] “Google Antigravity just deleted the contents of whole drive - came down to commanding a deletion of a 'directory with space in the name' wit…”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnGitHub Copilotnone0/10The evidence pack contains no documentation of a versioned API or deprecation policy for GitHub Copilot; the OpenAPI probe explicitly found all candidate spec paths returning 404, and no other citation addresses API versioning/deprecation commitments.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.github.com/openapi.json, https://docs.github.com/swagger.json, https://docs.github.com/…”
Google Antigravitynone0/10No evidence of versioned APIs or a documented deprecation policy; OpenAPI probe returned 404s across all candidate paths and no docs mention API versioning or deprecation timelines.
- [probe] “PROBE openapi: all candidate paths 404 (https://antigravity.google/openapi.json, https://antigravity.google/swagger.json, https://antigravit…”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round to Google AntigravityDocs show Copilot can run multiple background cloud-agent sessions in parallel, track them from one control page, and trigger automations on repo events/schedules (docs-8, docs-14, docs-15, docs-33), which supports scaling to many tasks, but there's no explicit evidence of a single bulk command/batch operation (e.g., 'review 50 PRs at once' or 'fix all issues matching X') as a discrete feature. Missing for 10: an explicit bulk-action UI/API (e.g., batch PR review, batch issue triage) and independent confirmation that many items can be processed in one invocation rather than via separate parallel agent sessions.
- [claimed-docs] “Launch work from GitHub, track progress across multiple agents, review changes, and merge completed work—all from one desktop workspace buil…”
- [claimed-docs] “Use one centralized control page to jump between agent sessions, check progress, and stay in control without losing your place.”
- [claimed-docs] “Automations let you run Copilot cloud agent automatically, on a schedule or in response to events in a repository.”
- [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
- [claimed-docs] “Track activity with detailed audit logs and enforce governance by managing agents from a single control plane.”
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.”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to GitHub CopilotGitHub Copilot documents event/schedule-triggered automations for its cloud agent ('run Copilot cloud agent automatically, on a schedule or in response to events in a repository', 'in response to events such as an issue being opened'), plus @mention-triggered PR actions, matching the story's rule-based automatic action pattern. Missing for 10: no independent/hands-on validation of the automation reliability or examples of complex rule chains beyond schedule/issue triggers.
- [claimed-docs] “Automations let you run Copilot cloud agent automatically, on a schedule or in response to events in a repository.”
- [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
- [claimed-docs] “Mention `@copilot` in a comment on an existing pull request to ask it to make changes.”
- [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
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.”
ai-native userSchedule recurring jobs or workflows
weight 2 · round to Google AntigravityGitHub Copilot docs explicitly describe 'Automations' that run the cloud agent on a schedule or in response to repository events, allowing recurring/scheduled agent workflows, plus a control page to track multiple scheduled agent sessions. This directly matches the story of scheduling recurring jobs/workflows. Missing for 10: independent/hands-on corroboration of scheduling reliability, and more detail on cron-like configuration options or failure handling.
- [claimed-docs] “Automations let you run Copilot cloud agent automatically, on a schedule or in response to events in a repository.”
- [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
- [claimed-docs] “Use one centralized control page to jump between agent sessions, check progress, and stay in control without losing your place.”
- [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
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”
ai-native userVersion, review, and roll back my automations
weight 1 · round to GitHub CopilotCopilot's cloud-agent automations produce PRs that can be reviewed (code review feature, docs-28/29) and tracked via audit logs and a central control plane (docs-23), and since output flows through Git, changes are inherently versioned and revertible via standard PR/commit mechanics. However, there is no direct evidence of a dedicated versioning or rollback mechanism for the automation definitions/schedules themselves (e.g., automation history, revert-to-previous-config). missing for 10: explicit versioning/rollback UI for automation configs, evidence of rolling back an automation run itself (not just its code output), independent confirmation of this workflow in practice.
- [claimed-docs] “Automations let you run Copilot cloud agent automatically, on a schedule or in response to events in a repository.”
- [claimed-docs] “GitHub Copilot can review your code and provide feedback. Where possible, Copilot's feedback includes suggested changes which you can apply …”
- [claimed-docs] “Copilot labels each comment with a severity level of "High," "Medium," or "Low" to help you prioritize the issues it finds based on their im…”
- [claimed-docs] “Track activity with detailed audit logs and enforce governance by managing agents from a single control plane.”
- [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
Google Antigravitynone0/10Evidence 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.
Autonomy agents — stories about autonomy agents in this arenaAutonomy agents
Stories about autonomy agents in this arena
Background execution
ai-native userHave a cloud agent build, test, and demo a feature end-to-end for my review
weight 2 · round to GitHub CopilotDocs describe a genuine cloud agent that works independently in the background (assign tasks, plan/explore/execute), runs in isolated cloud sandboxes to interact with code/tools/filesystem, and produces PRs for review with automated code review and severity-labeled feedback — covering build, execute, and review end-to-end. However, 'testing' and 'demo' are only implied (sandbox execution, PR review) rather than explicitly documented as a testing/demo step, and there is no independent/hands-on corroboration of the cloud agent specifically completing a full feature end-to-end (community evidence predates/doesn't cover the cloud agent feature). Missing for 10: explicit test-running/verification evidence, a documented demo/preview mechanism, and independent hands-on validation of cloud agent outcomes.
- [claimed-docs] “Assign tasks to agents like Copilot, Claude by Anthropic, and OpenAI Codex, and let them plan, explore, and execute work autonomously in the…”
- [claimed-docs] “Access to Cloud agent and code review”
- [claimed-docs] “Launch work from GitHub, track progress across multiple agents, review changes, and merge completed work—all from one desktop workspace buil…”
- [claimed-docs] “Use one centralized control page to jump between agent sessions, check progress, and stay in control without losing your place.”
- [claimed-docs] “Automations let you run Copilot cloud agent automatically, on a schedule or in response to events in a repository.”
- [claimed-docs] “Cloud and local sandboxes provide isolated execution environments that let Copilot safely interact with code, tools, filesystem, and network…”
- [claimed-docs] “GitHub Copilot can review your code and provide feedback. Where possible, Copilot's feedback includes suggested changes which you can apply …”
- [claimed-docs] “Copilot labels each comment with a severity level of "High," "Medium," or "Low" to help you prioritize the issues it finds based on their im…”
- [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
- [claimed-docs] “Mention `@copilot` in a comment on an existing pull request to ask it to make changes.”
- [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
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…”
developerDelegate longer-running coding tasks to run in the background in an isolated cloud environment
weight 3 · round to GitHub CopilotCopilot cloud agent is well documented as delegating tasks to run autonomously in an isolated cloud sandbox, working independently in the background like a human developer, with scheduling/automations, a control page to track multiple sessions, and audit logs for governance. missing for 10: independent hands-on community verification of cloud agent reliability/performance (community evidence pack predates cloud agent feature and doesn't corroborate this specific capability).
- [claimed-docs] “Assign tasks to agents like Copilot, Claude by Anthropic, and OpenAI Codex, and let them plan, explore, and execute work autonomously in the…”
- [claimed-docs] “Access to Cloud agent and code review”
- [claimed-docs] “Launch work from GitHub, track progress across multiple agents, review changes, and merge completed work—all from one desktop workspace buil…”
- [claimed-docs] “Use one centralized control page to jump between agent sessions, check progress, and stay in control without losing your place.”
- [claimed-docs] “Automations let you run Copilot cloud agent automatically, on a schedule or in response to events in a repository.”
- [claimed-docs] “Cloud and local sandboxes provide isolated execution environments that let Copilot safely interact with code, tools, filesystem, and network…”
- [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
- [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
- [claimed-docs] “Track activity with detailed audit logs and enforce governance by managing agents from a single control plane.”
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.”
Parallel agents
ai-native userLaunch fleets of autonomous agents that work in parallel on different tasks for hours or days
weight 2 · round to Google AntigravityGitHub Copilot's cloud agent supports background autonomous work, scheduled/event-triggered automations, and a control page to track and manage multiple agent sessions in parallel (docs-8, docs-14, docs-15, docs-31, docs-33), which covers the 'fleets working in parallel' concept. However, evidence doesn't confirm true multi-hour/multi-day persistent autonomous runs at scale or independent hands-on validation of large fleets; most evidence is vendor docs rather than field reports. missing for 10: independent/hands-on confirmation of long-running (hours/days) parallel agent fleets, concrete scale limits or examples of many simultaneous agents, and community verification of duration/reliability at scale.
- [claimed-docs] “Launch work from GitHub, track progress across multiple agents, review changes, and merge completed work—all from one desktop workspace buil…”
- [claimed-docs] “Use one centralized control page to jump between agent sessions, check progress, and stay in control without losing your place.”
- [claimed-docs] “Automations let you run Copilot cloud agent automatically, on a schedule or in response to events in a repository.”
- [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
- [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
- [claimed-docs] “Track activity with detailed audit logs and enforce governance by managing agents from a single control plane.”
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.”
developerRun several task attempts in parallel and compare results before choosing one
weight 1 · round to GitHub CopilotCopilot's cloud/background agents support launching and tracking multiple agent sessions in parallel from a single control page and desktop workspace (docs-8, docs-14, docs-31), which enables running concurrent tasks. However, there's no explicit documentation of running multiple attempts of the *same* task and comparing outputs before selecting one—the evidence describes managing distinct tasks/agents, not competing solutions to a single task. Missing for 10: explicit multi-attempt-per-task workflow, UI for side-by-side comparison of alternative solutions, and any hands-on/community confirmation of this specific parallel-attempt-and-choose pattern.
- [claimed-docs] “Launch work from GitHub, track progress across multiple agents, review changes, and merge completed work—all from one desktop workspace buil…”
- [claimed-docs] “Use one centralized control page to jump between agent sessions, check progress, and stay in control without losing your place.”
- [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
- [claimed-docs] “Track activity with detailed audit logs and enforce governance by managing agents from a single control plane.”
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…”
Scheduled automation
ai-native userSet up always-on agents that run on schedules or triggers to maintain and fix my software autonomously
weight 2 · round to GitHub CopilotGitHub Copilot explicitly documents scheduled/event-triggered cloud agents ('Automations let you run Copilot cloud agent automatically, on a schedule or in response to events in a repository') that work independently in the background, plus a control plane to track/manage multiple agent sessions and sandboxed execution environments. This directly matches the always-on, autonomous, schedule/trigger-driven maintenance story. Missing for 10: independent/hands-on verification of scheduled agent runs actually fixing software autonomously in production, and more detail on trigger types beyond issue-opened examples.
- [claimed-docs] “Automations let you run Copilot cloud agent automatically, on a schedule or in response to events in a repository.”
- [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
- [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
- [claimed-docs] “Use one centralized control page to jump between agent sessions, check progress, and stay in control without losing your place.”
- [claimed-docs] “Cloud and local sandboxes provide isolated execution environments that let Copilot safely interact with code, tools, filesystem, and network…”
- [claimed-docs] “Track activity with detailed audit logs and enforce governance by managing agents from a single control plane.”
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…”
Code generation — quality of generated code — correctness, style, fit to the codebaseCode generation
Quality of generated code — correctness, style, fit to the codebase
Code completion
developerReceive inline code completions and next-edit suggestions as I type
weight 3 · round to GitHub CopilotDocs explicitly claim 'unlimited code completion and next edit suggestions' and inline editor functionality (explaining, completing code, proposing edits), and community reports from real usage confirm inline completions work well in practice (e.g., 'Copilot guesses the exact code I want,' 'occasional mistakes but overall it has the right idea'). Missing for 10: no first-party benchmark or independent quantitative study specifically isolating next-edit-suggestion accuracy separate from general completion quality.
- [claimed-docs] “Unlimited code completion and next edit suggestions”
- [claimed-docs] “Copilot in your editor does it all, from explaining concepts and completing code, to proposing edits and validating files with agent mode.”
- [community] “I've been using the alpha for the past 2 weeks, and I'm blown away. Copilot guesses the exact code I want about one in ten times... when it …”
- [community] “Yesterday, Copilot could not write a program with SymPy... Today it uses SymPy as well as it uses NumPy (occasional mistakes, but overall it…”
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”
Debugging
developerDebug a live running web application directly from my coding assistant
weight 1 · round to Google AntigravityGitHub Copilotnone0/10Evidence covers code completion, chat, agent mode file edits, cloud agents, code review, and MCP integrations, but nothing about attaching to or debugging a live running web application (e.g., runtime inspection, breakpoints, log/trace analysis of a running process). No evidence supports this capability.
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.”
developerDebug issues and troubleshoot using natural-language queries
weight 2 · round to GitHub CopilotCopilot Chat explicitly supports natural-language interaction for explaining concepts, code review with prioritized issue severity, and agent mode for autonomous exploration and fixing—core debugging/troubleshooting workflows (docs-4, docs-22, docs-28, docs-29). Autofix also provides contextual explanations for vulnerabilities (docs-13), reinforcing NL-driven troubleshooting. missing for 10: a dedicated 'debug' feature description, independent hands-on evidence specifically validating debugging accuracy/success (community evidence focuses on completion quality and licensing concerns, not debugging).
- [claimed-docs] “chat functionality is currently available only in Visual Studio Code, JetBrains, and Visual Studio”
- [claimed-docs] “Copilot in your editor does it all, from explaining concepts and completing code, to proposing edits and validating files with agent mode.”
- [claimed-docs] “GitHub Copilot can review your code and provide feedback. Where possible, Copilot's feedback includes suggested changes which you can apply …”
- [claimed-docs] “Copilot labels each comment with a severity level of "High," "Medium," or "Low" to help you prioritize the issues it finds based on their im…”
- [claimed-docs] “GitHub Copilot Autofix provides contextual explanations and code suggestions to help developers fix vulnerabilities in code”
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”
Feature implementation
developerTurn a tracked issue into a complete pull request end-to-end
weight 3 · round to GitHub CopilotGitHub Copilot's cloud agent can be assigned directly from an issue or via @copilot mentions, working autonomously to plan, explore, execute changes, and open a pull request, with automations to trigger this on issue events; the desktop workspace lets developers track, review, and merge the resulting PR end-to-end. missing for 10: independent hands-on verification of the full issue-to-merged-PR flow (community evidence covers earlier code-completion/chat era, not cloud agent specifically) and concrete success-rate data on autonomous PR quality.
- [claimed-docs] “Assign tasks to agents like Copilot, Claude by Anthropic, and OpenAI Codex, and let them plan, explore, and execute work autonomously in the…”
- [claimed-docs] “Launch work from GitHub, track progress across multiple agents, review changes, and merge completed work—all from one desktop workspace buil…”
- [claimed-docs] “Use one centralized control page to jump between agent sessions, check progress, and stay in control without losing your place.”
- [claimed-docs] “Automations let you run Copilot cloud agent automatically, on a schedule or in response to events in a repository.”
- [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
- [claimed-docs] “Mention `@copilot` in a comment on an existing pull request to ask it to make changes.”
- [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
Google Antigravitynone0/10Antigravity'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.”
developerDescribe a feature or bug in plain language and have the agent implement or fix it across multiple files
weight 3 · round to GitHub CopilotDocs describe Copilot agent mode editing files across the workspace, cloud agents that plan/explore/execute tasks autonomously (including from plain-language issue/PR descriptions via @copilot mentions), and code review/autofix capabilities, directly matching the story of describing a feature/bug and having it implemented across multiple files. Community evidence corroborates real usage of the agent for multi-file/complex code tasks, though some hands-on reports note quality limitations on nuanced 'fix the bug' requests. Missing for 10: rigorous independent benchmarking of multi-file correctness and more first-hand accounts specifically of cross-file feature implementation success/failure rates.
- [claimed-docs] “Edit files in your workspace in agent mode”
- [claimed-docs] “Assign tasks to agents like Copilot, Claude by Anthropic, and OpenAI Codex, and let them plan, explore, and execute work autonomously in the…”
- [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
- [claimed-docs] “Mention `@copilot` in a comment on an existing pull request to ask it to make changes.”
- [claimed-docs] “Copilot in your editor does it all, from explaining concepts and completing code, to proposing edits and validating files with agent mode.”
- [community] “The first video in this post is a perfect example of the problems I see in this space. First the programmer asks the AI to nebulously 'fix t…”
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…”
Maintenance automation
developerHave the agent write tests, fix lint errors, resolve merge conflicts, and update dependencies for me
weight 3 · round to GitHub CopilotCopilot's agent mode edits files, validates changes, and can autonomously plan/execute tasks (docs-2,3,22,31), code review with severity-labeled feedback and suggested fixes covers lint/quality issues (docs-28,29), and @copilot on PRs plus cloud agent covers merge conflict resolution and general code changes (docs-32). Dependency updates and explicit test-writing aren't separately documented as named features, so this is inferred from general-purpose agent code editing rather than a dedicated capability. missing for 10: explicit documented examples of writing tests, resolving merge conflicts, and updating dependencies as named use cases, and independent hands-on confirmation of these specific tasks.
- [claimed-docs] “Edit files in your workspace in agent mode”
- [claimed-docs] “Assign tasks to agents like Copilot, Claude by Anthropic, and OpenAI Codex, and let them plan, explore, and execute work autonomously in the…”
- [claimed-docs] “Copilot in your editor does it all, from explaining concepts and completing code, to proposing edits and validating files with agent mode.”
- [claimed-docs] “GitHub Copilot can review your code and provide feedback. Where possible, Copilot's feedback includes suggested changes which you can apply …”
- [claimed-docs] “Copilot labels each comment with a severity level of "High," "Medium," or "Low" to help you prioritize the issues it finds based on their im…”
- [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
- [claimed-docs] “Mention `@copilot` in a comment on an existing pull request to ask it to make changes.”
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…”
Multimodal generation
ai-native userGenerate a working app from a sketch, image, or PDF design
weight 2 · round to Google AntigravityGitHub Copilotnone0/10No evidence that Copilot can take a sketch, image, or PDF design and generate a working app from it; documentation focuses on code completion, chat, agent mode, cloud agents, and MCP integration, with no mention of image/PDF-to-code or multimodal design-to-app generation.
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…”
Codebase understanding — how deeply the tool maps your repo — cross-file context, architecture awareness, historyCodebase understanding
How deeply the tool maps your repo — cross-file context, architecture awareness, history
Codebase mapping
developerUnderstand how a codebase fits together to find where to start making changes
weight 3 · round to Google AntigravityCopilot Chat in the editor is documented to explain concepts and provide context-aware help (docs-22), and enterprise features let teams build a 'shared source of truth' from docs and repos (docs-9) plus MCP integrations that pull in repo/issue/PR context (docs-20, docs-21, docs-25), all of which support exploring an unfamiliar codebase. However, there is no explicit feature description of codebase-wide indexing, dependency/architecture mapping, or a dedicated 'explain this repo' capability, and no hands-on community evidence confirming it helps developers orient in large codebases. Missing for 10: dedicated codebase-mapping/semantic search feature docs, explicit onboarding/architecture-understanding use case, and independent corroboration of effectiveness.
- [claimed-docs] “Copilot in your editor does it all, from explaining concepts and completing code, to proposing edits and validating files with agent mode.”
- [claimed-docs] “Scale knowledge and keep teams consistent by creating a shared source of truth that includes context from your docs and repositories.”
- [claimed-docs] “Connect MCP servers to Copilot Chat to share context from other applications.”
- [claimed-docs] “You can create a new MCP server to fulfill your specific needs, and then integrate it with Copilot Chat.”
- [claimed-docs] “Learn how to use the GitHub Model Context Protocol (MCP) server to interact with repositories, issues, pull requests, and other GitHub featu…”
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…”
developerHave the agent map and explain an entire unfamiliar codebase without manually selecting context files
weight 3 · round drawnCopilot's agent mode and cloud agent are documented to 'plan, explore, and execute work autonomously' across a repo, and 'skills' let it perform specialized tasks, implying some autonomous codebase exploration without hand-picked files, but there's no explicit doc describing a whole-codebase 'map and explain' capability. missing for 10: dedicated codebase-mapping/explanation feature docs, evidence of automatic whole-repo context gathering without manual file selection, and independent hands-on confirmation of this specific workflow.
- [claimed-docs] “Assign tasks to agents like Copilot, Claude by Anthropic, and OpenAI Codex, and let them plan, explore, and execute work autonomously in the…”
- [claimed-docs] “Scale knowledge and keep teams consistent by creating a shared source of truth that includes context from your docs and repositories.”
- [claimed-docs] “Copilot in your editor does it all, from explaining concepts and completing code, to proposing edits and validating files with agent mode.”
- [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
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”
Context management
developerHave the agent build and recall memory automatically across sessions
weight 2 · round drawnGitHub Copilotnone0/10The evidence pack describes agent mode, cloud agents, MCP context, and code review, but nothing about persistent memory that is automatically built and recalled across sessions—closest is a static 'shared source of truth' repository doc feature, not agent-built memory.
- [claimed-docs] “Scale knowledge and keep teams consistent by creating a shared source of truth that includes context from your docs and repositories.”
Google Antigravitynone0/10The 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.”
developerInclude multiple project directories in a single session for broader context
weight 2 · round to Google AntigravityGitHub Copilotnone0/10The evidence pack describes agent mode, chat, MCP integrations, and cloud agents, but contains no mention of including multiple project directories/folders in a single Copilot session for broader context. Missing for 10: any documentation of multi-root workspace support, cross-directory indexing, or explicit multi-project context sharing in one session.
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.”
developerAdd a project instructions file to set coding standards and conventions the agent follows
weight 3 · round to Google AntigravityDocs mention 'creating a shared source of truth that includes context from your docs and repositories' to keep teams consistent (github-copilot-docs-9), which gestures at instructions/knowledge-context features, but the evidence pack never explicitly describes a project instructions file (e.g., copilot-instructions.md) or how coding standards/conventions are set and enforced. Missing for 10: explicit documentation of an instructions file mechanism, its scope/format, and confirmation the agent follows it during edits/completions.
- [claimed-docs] “Scale knowledge and keep teams consistent by creating a shared source of truth that includes context from your docs and repositories.”
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.”
Issue diagnosis
developerReproduce issues, narrow down root causes, and verify fixes
weight 3 · round to Google AntigravityCopilot's agent mode and chat can propose edits and 'validate files' (docs-22), Autofix explains and suggests fixes for vulnerabilities (docs-13), and code review flags issues with severity (docs-28/29), which together support parts of root-cause analysis and fix verification, but there is no explicit documentation of reproducing bugs, running/debugging tests, or a dedicated root-cause investigation workflow. missing for 10: explicit reproduction-of-issue workflow, test-execution/debugging tooling, and independent hands-on evidence of root-cause narrowing.
- [claimed-docs] “GitHub Copilot Autofix provides contextual explanations and code suggestions to help developers fix vulnerabilities in code”
- [claimed-docs] “Copilot in your editor does it all, from explaining concepts and completing code, to proposing edits and validating files with agent mode.”
- [claimed-docs] “GitHub Copilot can review your code and provide feedback. Where possible, Copilot's feedback includes suggested changes which you can apply …”
- [claimed-docs] “Copilot labels each comment with a severity level of "High," "Medium," or "Low" to help you prioritize the issues it finds based on their im…”
- [claimed-docs] “Cloud and local sandboxes provide isolated execution environments that let Copilot safely interact with code, tools, filesystem, and network…”
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…”
Ecosystem — integrations, plugins, and third-party ecosystem storiesEcosystem
Integrations, plugins, and third-party ecosystem stories
Marketplace
developerEquip the agent with custom skills to perform specialized tasks
weight 1 · round to Google AntigravityDocs explicitly describe a 'Skills' feature ('Skills allow Copilot to perform specialized tasks') and 'Custom agents' that let developers tailor Copilot's expertise, plus MCP server extensibility to add custom tools/context. This directly matches the story of equipping the agent with custom skills, though details are thin. Missing for 10: concrete developer walkthrough of creating a skill, independent/hands-on confirmation of using custom skills, and richer documentation depth beyond a single-line description.
- [claimed-docs] “Skills allow Copilot to perform specialized tasks.”
- [claimed-docs] “Custom agents allow you to tailor Copilot's expertise for specific tasks.”
- [claimed-docs] “Connect MCP servers to Copilot Chat to share context from other applications.”
- [claimed-docs] “You can create a new MCP server to fulfill your specific needs, and then integrate it with Copilot Chat.”
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 …”
engineering-leadIntegrate third-party partner-built agent apps into my workflows
weight 1 · round to GitHub CopilotDocs explicitly describe 'Agent apps' that let partner-built agents be used directly in GitHub workflows powered by Copilot subscription, plus assigning tasks to third-party agents (Claude, OpenAI Codex) and MCP server integration for extending Copilot with external tools. Missing for 10: independent/hands-on verification of partner agent app integrations and detail on governance/setup friction beyond first-party docs.
- [claimed-docs] “Agent apps let you use partner-built agents directly in your workflows on GitHub, powered by your Copilot subscription.”
- [claimed-docs] “Assign tasks to agents like Copilot, Claude by Anthropic, and OpenAI Codex, and let them plan, explore, and execute work autonomously in the…”
- [claimed-docs] “Connect MCP servers to Copilot Chat to share context from other applications.”
- [claimed-docs] “You can create a new MCP server to fulfill your specific needs, and then integrate it with Copilot Chat.”
- [claimed-docs] “Control which MCP servers developers can access from their IDEs, and use allow lists to prevent unauthorized access.”
Google Antigravitydisputedcontradicted4/10Vendor 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,…”
Team knowledge
engineering-leadCreate a shared workspace from my docs and repos as a common source of truth for the team
weight 1 · round to GitHub CopilotDocs explicitly claim the ability to 'scale knowledge and keep teams consistent by creating a shared source of truth that includes context from your docs and repositories,' directly matching the story, and related enterprise-governance features (control planes, audit logs, MCP allow-lists) support team-wide consistency. However, this is a single vendor-claimed line item with no elaboration on setup, structure, or how it functions as a 'workspace,' and no independent/hands-on evidence corroborates it. Missing for 10: independent verification, concrete workflow/UI details, and community confirmation that teams actually use this as a shared source of truth.
- [claimed-docs] “Scale knowledge and keep teams consistent by creating a shared source of truth that includes context from your docs and repositories.”
- [claimed-docs] “Track activity with detailed audit logs and enforce governance by managing agents from a single control plane.”
- [claimed-docs] “Control which MCP servers developers can access from their IDEs, and use allow lists to prevent unauthorized access.”
Google Antigravitynone0/10Antigravity's 'Projects' concept groups folders/repos for a single agent session's context (docs-5, docs-17, docs-35, docs-38) and can surface Docs/Drive links (docs-32), but there is no evidence of a multi-user, team-shared workspace or collaborative source-of-truth that an engineering-lead could set up for a whole team — Projects appear to be individually scoped, local constructs rather than shared team assets.
- [claimed-docs] “Group your conversations into Projects, which can span multiple folders and support custom settings and scoped permissions.”
- [claimed-docs] “a project can work with one folder or multiple folders (e.g., a frontend and a backend repo), providing your agents with all of the context …”
- [claimed-docs] “Agents work within Projects, which define the boundaries of the folders and repositories they can access.”
- [claimed-docs] “Worktree support: Projects natively support Git worktrees, allowing agents to operate in isolated background folders.”
- [claimed-docs] “External files such as Google Drive links, PDFs, and Office documents now appear in their own Documents section in the sidebar above Artifac…”
Tool integration
developerConnect the agent to workflow tools like Jira, Slack, and Google Drive to extend its context
weight 3 · round drawnCopilot supports connecting to external tools via MCP servers (docs-10, docs-20, docs-21, docs-25, docs-35), and states it can create custom MCP servers for specific needs, which theoretically enables Jira/Slack/Google Drive integration. However, no evidence names first-party or documented connectors for Jira, Slack, or Google Drive specifically. missing for 10: named official integrations or docs referencing Jira/Slack/Google Drive, independent confirmation these connectors work in practice.
- [claimed-docs] “Connect MCP servers to Copilot Chat to share context from other applications.”
- [claimed-docs] “You can create a new MCP server to fulfill your specific needs, and then integrate it with Copilot Chat.”
- [claimed-docs] “Control which MCP servers developers can access from their IDEs, and use allow lists to prevent unauthorized access.”
- [claimed-docs] “Copilot works where you do—in GitHub, your IDE, the CLI, project tools, chat apps, and custom MCP servers.”
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…”
developerKick off agent tasks directly from GitHub, GitLab, Linear, or Slack
weight 2 · round to GitHub CopilotDocs clearly show agent tasks can be kicked off from GitHub itself (mentioning @copilot on a PR, automations triggered by repo events, cloud agent background execution), and Copilot is described as working across 'chat apps' generically, but no evidence specifically documents launching agent tasks from GitLab, Linear, or Slack. Missing for 10: explicit GitLab integration, explicit Linear integration, explicit Slack integration for triggering agent tasks.
- [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
- [claimed-docs] “Mention `@copilot` in a comment on an existing pull request to ask it to make changes.”
- [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
- [claimed-docs] “Copilot works where you do—in GitHub, your IDE, the CLI, project tools, chat apps, and custom MCP servers.”
- [claimed-docs] “Agent apps let you use partner-built agents directly in your workflows on GitHub, powered by your Copilot subscription.”
Ide terminal integration — meeting you in the IDE and terminal — extensions, inline flows, contextIde terminal integration
Meeting you in the IDE and terminal — extensions, inline flows, context
Cross device continuity
developerStart a task on one device and continue it later from another device or browser
weight 2 · round to Google AntigravityCopilot's cloud agent and control-plane features (docs-8, docs-14, docs-31-33) let a developer assign a task to an agent from GitHub or an IDE and later check progress or continue via GitHub.com's centralized control page or desktop workspace, which is inherently accessible cross-device/browser. However, this is inferred from the cloud-agent architecture rather than an explicit 'continue from another device' claim, and there's no independent/hands-on confirmation of seamless handoff. Missing for 10: explicit documentation of cross-device session continuation and independent verification that state/context truly persists and is resumable identically on a different machine or browser.
- [claimed-docs] “Launch work from GitHub, track progress across multiple agents, review changes, and merge completed work—all from one desktop workspace buil…”
- [claimed-docs] “Use one centralized control page to jump between agent sessions, check progress, and stay in control without losing your place.”
- [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
- [claimed-docs] “Mention `@copilot` in a comment on an existing pull request to ask it to make changes.”
- [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
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…”
Ide integration
developerView interactive diffs and share selected code as context from within my JetBrains IDE
weight 1 · round to GitHub CopilotDocs confirm Copilot Chat and agent-mode editing are available in JetBrains IDEs (github-copilot-docs-4, github-copilot-docs-24, github-copilot-docs-22), which implies some in-IDE diff/context capability, but no evidence specifically describes an interactive diff viewer or a 'share selected code as context' feature for JetBrains. Missing for 10: explicit documentation of JetBrains-specific interactive diff UI, explicit context-selection workflow, and independent/hands-on confirmation of these JetBrains features.
- [claimed-docs] “chat functionality is currently available only in Visual Studio Code, JetBrains, and Visual Studio”
- [claimed-docs] “GitHub Copilot integrates with leading editors, including Visual Studio Code, Visual Studio, JetBrains IDEs, and Neovim, and, unlike other A…”
- [claimed-docs] “Copilot in your editor does it all, from explaining concepts and completing code, to proposing edits and validating files with agent mode.”
Google Antigravitynone0/10Antigravity is documented as a standalone VSCode-fork IDE with its own Editor view, Artifacts diff viewer, and CLI/SDK — there is no mention anywhere in the docs, changelog, or community threads of a JetBrains plugin or JetBrains-specific integration for diffs or context sharing.
- [claimed-docs] “Google Antigravity's Editor view offers tab autocompletion, natural language code commands, and a configurable, and context-aware configurab…”
- [claimed-docs] “Artifacts include rich markdown plans (Implementation Plans), code diffs, architecture diagrams, images, and browser recordings.”
- [claimed-docs] “Added a "Hide Whitespace Changes" option to the Review Changes overflow menu and file diff viewers to filter out whitespace-only edits.”
- [claimed-docs] “Code and data artifacts like SQL and JSONL files now open in a virtualized viewer with syntax highlighting and line numbers”
- [community] “I went ahead and downloaded it, it looks to be a VSCode fork very similar to Cursor, with support for Gemini 3 Pro, Claude Sonnet 4.5, and G…”
developerChat with the coding assistant directly inside my IDE for contextual help
weight 3 · round to GitHub CopilotDocs confirm Copilot Chat is built into VS Code, JetBrains, and Visual Studio for contextual in-IDE chat (explaining concepts, proposing edits, agent mode), and community feedback corroborates real usage inside the editor. Missing for 10: independent hands-on report specifically about the chat UX (most community evidence focuses on completions, not chat).
- [claimed-docs] “chat functionality is currently available only in Visual Studio Code, JetBrains, and Visual Studio”
- [claimed-docs] “Copilot in your editor does it all, from explaining concepts and completing code, to proposing edits and validating files with agent mode.”
- [claimed-docs] “GitHub Copilot integrates with leading editors, including Visual Studio Code, Visual Studio, JetBrains IDEs, and Neovim, and, unlike other A…”
- [community] “I've been using the alpha for the past 2 weeks, and I'm blown away. Copilot guesses the exact code I want about one in ten times... when it …”
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”
Session management
developerReview diffs visually and run multiple sessions side by side in a desktop app
weight 2 · round to Google AntigravityDocs mention a 'desktop workspace' for launching work, tracking multiple agent sessions, and reviewing changes (docs-8, docs-14), and a code-review feature with inline suggested changes (docs-28), suggesting some diff-review and multi-session tracking capability. However, it's unclear whether this 'desktop workspace' is a native desktop app or a web-based GitHub UI, and there's no explicit description of a visual side-by-side diff viewer or dedicated multi-pane session UI as in competing IDE tools. Missing for 10: confirmation of a true native desktop application (not browser-based), explicit visual diff-viewer description, and independent/hands-on evidence of side-by-side session usage.
- [claimed-docs] “Launch work from GitHub, track progress across multiple agents, review changes, and merge completed work—all from one desktop workspace buil…”
- [claimed-docs] “Use one centralized control page to jump between agent sessions, check progress, and stay in control without losing your place.”
- [claimed-docs] “GitHub Copilot can review your code and provide feedback. Where possible, Copilot's feedback includes suggested changes which you can apply …”
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…”
engineering-leadManage multiple agent-driven coding sessions from one unified workspace
weight 2 · round drawnDocs describe a unified control page/desktop workspace to launch, track, and manage multiple agent sessions (Copilot, Claude, Codex) with progress tracking, review, merge, and governance/audit logs from one control plane, directly matching the story. Missing for 10: independent hands-on validation of the multi-agent dashboard experience and any reported friction managing many concurrent sessions.
- [claimed-docs] “Assign tasks to agents like Copilot, Claude by Anthropic, and OpenAI Codex, and let them plan, explore, and execute work autonomously in the…”
- [claimed-docs] “Launch work from GitHub, track progress across multiple agents, review changes, and merge completed work—all from one desktop workspace buil…”
- [claimed-docs] “Use one centralized control page to jump between agent sessions, check progress, and stay in control without losing your place.”
- [claimed-docs] “Track activity with detailed audit logs and enforce governance by managing agents from a single control plane.”
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…”
Terminal workflow
developerRun a coding agent locally from my terminal
weight 3 · round to Google AntigravityGitHub Copilot CLI is officially documented as letting developers use Copilot directly from the terminal, including voice-to-text prompting, and is confirmed installable per docs and probe evidence. missing for 10: independent hands-on validation of the CLI agent's local execution/quality, and more detail on its autonomous/agentic capabilities (vs. just chat) within the terminal.
- [claimed-docs] “The command-line interface (CLI) for GitHub Copilot allows you to use Copilot directly from your terminal.”
- [claimed-docs] “As an alternative to typing, you can speak your prompt.”
- [probe] “official CLI documented at https://docs.github.com/en/copilot/how-tos/copilot-cli/set-up-copilot-cli/install-copilot-cli”
- [claimed-docs] “GitHub Copilot is also supported in terminals through GitHub CLI and as a chat integration in Windows Terminal Canary.”
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 …”
developerRun the agent non-interactively in scripts for workflow automation
weight 2 · round to Google AntigravityCopilot CLI (docs-26) lets you invoke Copilot from a terminal, and Copilot cloud agent 'Automations' (docs-15, docs-33) can be triggered on a schedule or repository events, which supports some non-interactive workflow automation. However, there is no direct evidence of a documented headless/non-interactive CLI flag (e.g., a scripted prompt-and-exit mode with exit codes) for running Copilot CLI itself inside arbitrary scripts. missing for 10: explicit CLI non-interactive/scripting mode docs, evidence of exit-code/output-parsing support for pipelines, independent hands-on confirmation of script usage.
- [claimed-docs] “The command-line interface (CLI) for GitHub Copilot allows you to use Copilot directly from your terminal.”
- [claimed-docs] “Automations let you run Copilot cloud agent automatically, on a schedule or in response to events in a repository.”
- [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
- [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
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.”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to Google AntigravityCopilot offers a CLI (docs-26, probe-4) and MCP server integration (docs-25) that give some programmatic access to Copilot/GitHub features, but there is no evidence of a comprehensive public API/OpenAPI spec covering the full range of UI capabilities (chat, agent mode, cloud agent, code review) — the openapi probe returned 404 for all candidate endpoints (probe-3). Missing for 10: a documented REST/GraphQL API exposing chat, agent-mode edits, cloud-agent orchestration, and code review equivalently to the UI, and any independent confirmation that CLI/MCP covers full feature parity.
- [claimed-docs] “The command-line interface (CLI) for GitHub Copilot allows you to use Copilot directly from your terminal.”
- [probe] “official CLI documented at https://docs.github.com/en/copilot/how-tos/copilot-cli/set-up-copilot-cli/install-copilot-cli”
- [claimed-docs] “Learn how to use the GitHub Model Context Protocol (MCP) server to interact with repositories, issues, pull requests, and other GitHub featu…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.github.com/openapi.json, https://docs.github.com/swagger.json, https://docs.github.com/…”
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…”
ai-native userExport all of my data in open formats and leave
weight 3 · round drawnGitHub Copilotnone0/10No evidence in the pack describes any data export feature, open-format export, or account data portability mechanism for GitHub Copilot; documentation covers coding, agents, MCP, and models but nothing about exporting user data or leaving the platform with your data intact.
ai-native userRead the product's source under an open license
weight 2 · round drawnGitHub Copilotnone0/10GitHub Copilot is closed-source proprietary software; no evidence in the pack shows any open-license source availability, and community discussion instead focuses on training-data/licensing concerns, not the product's own source code being open.
Google Antigravitynone0/10No 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.
ai-native userSelf-host the core product
weight 3 · round drawnGitHub Copilotnone0/10GitHub Copilot is a proprietary cloud/IDE-integrated service with no evidence of any self-hostable core model, backend, or deployment option; all documented capabilities rely on GitHub's hosted infrastructure and models. Self-hosting is a legitimate axis for AI-native openness comparisons, but nothing in the evidence pack indicates it is possible.
Google Antigravitynone0/10No 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…”
Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits
Free-tier ceilings, usage caps, and rate limits before you have to pay
Authentication
developerAuthenticate with an API key instead of an account login
weight 2 · round drawnGitHub Copilotnone0/10No evidence in the pack describes API-key authentication as an alternative to account login; Copilot's auth model is tied to GitHub account/subscription (IDE sign-in, CLI, etc.) with no mention of API keys for developer access.
Google Antigravitynone0/10Evidence 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…”
engineering-leadAuthenticate through an enterprise identity or cloud platform for compliance and scalability
weight 2 · round drawnGitHub Copilotnone0/10No evidence in the pack addresses SSO/SAML, enterprise identity providers (e.g., Okta, Azure AD), or cloud platform authentication for Copilot; docs cover agents, MCP, models, and governance features but not identity/authentication for enterprise compliance. Missing for 10: SSO/SAML integration docs, enterprise IdP support (Azure AD/Okta), any mention of authentication/compliance certifications tied to identity federation.
Google Antigravitynone0/10No 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…”
developerSign in with my existing product subscription plan to use the coding agent
weight 2 · round to GitHub CopilotDocs show that Copilot's cloud/coding agent features (agent mode, cloud agent, agent apps) are powered by and included in a user's existing Copilot subscription, e.g. 'Agent apps let you use partner-built agents directly in your workflows on GitHub, powered by your Copilot subscription' and 'Access to Cloud agent and code review' listed as plan features, meaning no separate sign-up is needed beyond the existing subscription/login. Missing for 10: explicit tier-by-tier sign-in flow documentation and independent user confirmation that no extra account creation is required beyond the existing GitHub/Copilot login.
- [claimed-docs] “Agent apps let you use partner-built agents directly in your workflows on GitHub, powered by your Copilot subscription.”
- [claimed-docs] “Access to Cloud agent and code review”
- [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
- [claimed-docs] “Launch work from GitHub, track progress across multiple agents, review changes, and merge completed work—all from one desktop workspace buil…”
Google Antigravitynone0/10No 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…”
developerSign in with a personal account to get free-tier access without managing API keys
weight 1 · round to Google AntigravityGitHub Copilotnone0/10The evidence pack contains no mention of a free tier, personal GitHub account sign-in flow, or API-key-free authentication for Copilot; all docs items describe features (agent mode, MCP, code review) but never address account-based free-tier access or pricing/sign-in mechanics.
Google Antigravitydisputedcontradicted3/10Vendor 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”
Model choice
developerLet the tool automatically pick the best model for each task
weight 1 · round to GitHub CopilotGitHub's own docs explicitly state Copilot can 'Automatically select the best model for each task' (docs-17), alongside supporting claims about multiple models optimized for speed/accuracy/cost (docs-7, docs-30). Missing for 10: independent/hands-on verification that auto-selection actually works well in practice, and details on how/when it triggers vs manual model choice.
- [claimed-docs] “Automatically select the best model for each task.”
- [claimed-docs] “Choose from leading LLMs optimized for speed, accuracy, or cost.”
- [claimed-docs] “GitHub Copilot supports multiple AI models, each with different strengths. Some prioritize speed and cost-efficiency, while others are optim…”
Google Antigravitynone0/10Docs 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”
developerChoose which underlying AI model powers my session from multiple providers
weight 2 · round drawnGitHub's own docs explicitly state Copilot supports multiple AI models from different providers (e.g., Claude, OpenAI Codex) and lets users 'choose from leading LLMs optimized for speed, accuracy, or cost,' with a dedicated supported-models reference page and an auto-select option. This directly matches the story of choosing the underlying model per session. Missing for 10: independent/hands-on community confirmation of the model-picker UI in practice and details on per-session persistence of the choice.
- [claimed-docs] “Choose from leading LLMs optimized for speed, accuracy, or cost.”
- [claimed-docs] “GitHub Copilot supports multiple AI models, each with different strengths. Some prioritize speed and cost-efficiency, while others are optim…”
- [claimed-docs] “Assign tasks to agents like Copilot, Claude by Anthropic, and OpenAI Codex, and let them plan, explore, and execute work autonomously in the…”
- [claimed-docs] “Automatically select the best model for each task.”
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.”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round drawnGitHub Copilotnone0/10No evidence in the pack mentions data residency, region selection, or geographic storage controls for GitHub Copilot; only data-training opt-out is mentioned, which is a different concern.
Google Antigravitynone0/10No evidence pack item mentions data residency, region selection, or storage location controls; only a telemetry on/off toggle is documented, which does not address data residency. Missing for 10: any documentation of regional data storage options, residency guarantees, or enterprise data-location controls.
ai-native userPrevent my data from being used to train AI models
weight 3 · round to GitHub CopilotGitHub's docs explicitly state individual subscribers can opt out of having their data used for AI model training at any time (github-copilot-docs-12), directly satisfying the story's core ask. However, the evidence pack lacks detail on how opt-out is enforced, whether it covers all Copilot data flows (e.g., telemetry, code review, agents), and community commentary voices skepticism (not concrete contradiction) about whether enterprise code can truly be excluded. Missing for 10: independent verification that opt-out is honored in practice, clarity on enterprise/org-level data-use guarantees, and details on scope of what 'training' opt-out actually excludes.
- [claimed-docs] “Individual subscribers can opt out of having their data used for AI model training at any time”
- [community] “Well, this can impose a serious risk to companies and their cloud strategy based on GitHub. Can these enterprises really make sure that thei…”
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)”
ai-native userControl data retention and deletion
weight 2 · round to GitHub CopilotGitHub Copilot docs confirm individual subscribers can opt out of AI model training data use at any time, giving some control over data usage, but there is no documented self-service mechanism for deleting stored chat/history data or explicit retention period controls. Community commentary also raises unresolved skepticism about enterprise assurances that code won't be used for training. Missing for 10: explicit data-deletion tooling, documented retention windows, and enterprise-level deletion guarantees beyond opt-out.
- [claimed-docs] “Individual subscribers can opt out of having their data used for AI model training at any time”
- [community] “Well, this can impose a serious risk to companies and their cloud strategy based on GitHub. Can these enterprises really make sure that thei…”
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)”
ai-native userOpt out of telemetry and usage tracking
weight 2 · round to Google AntigravityDocs confirm individual subscribers can opt out of having their code data used for AI model training, but this is narrower than opting out of telemetry/usage tracking broadly, and no evidence describes a general telemetry opt-out toggle. Community commentary (comm-5) even notes agreeing to 'additional telemetry terms' during a preview with no opt-out mentioned. Missing for 10: explicit telemetry/usage-tracking opt-out setting, documentation distinguishing telemetry from training-data opt-out, and independent confirmation that opting out actually stops telemetry collection.
- [claimed-docs] “Individual subscribers can opt out of having their data used for AI model training at any time”
- [community] “Gigantic caveat: 'I agree to these additional telemetry terms as part of the technical preview.'”
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)”
Review safety — keeping generated changes safe — diffs, approvals, guardrailsReview safety
Keeping generated changes safe — diffs, approvals, guardrails
Data governance
engineering-leadOpt out of having my code and prompts used for AI model training
weight 1 · round to GitHub CopilotDocs explicitly state individual subscribers can opt out of AI model training at any time (github-copilot-docs-12), which covers a developer-level version of this story. However, evidence does not show an org-wide/enterprise admin policy control that an engineering-lead could set organization-wide, and one community comment expresses skepticism about enterprise assurance (not a concrete contradiction). Missing for 10: enterprise/org-level policy documentation, admin-console controls, and independent verification of enforcement.
- [claimed-docs] “Individual subscribers can opt out of having their data used for AI model training at any time”
- [community] “Well, this can impose a serious risk to companies and their cloud strategy based on GitHub. Can these enterprises really make sure that thei…”
Docs mention a Telemetry toggle to 'enable/disable sharing interaction logs to improve models,' which functions as an opt-out from data being used for model improvement, but there is no explicit documentation framing this as a training opt-out for enterprise/engineering-lead governance needs (e.g., no data-processing agreement, no distinction between prompts/code vs telemetry, no enterprise admin-level control). Missing for 10: explicit statement that code/prompts are excluded from training, org-wide/admin-level enforcement of the opt-out, and independent confirmation the toggle actually stops training use.
- [claimed-docs] “toggle Telemetry (enable/disable sharing interaction logs to improve models)”
Pr review
developerHave the agent stage changes, write commit messages, create branches, and open pull requests
weight 3 · round to GitHub CopilotGitHub Copilot's cloud/background agent is documented to work independently on tasks, make changes on existing PRs via @copilot mentions, and complete work 'just like a human developer,' which in GitHub's workflow model entails committing changes and opening/updating pull requests (docs-31, docs-32, docs-8, docs-14). However, explicit documentation of branch creation and commit-message authorship mechanics is not directly cited, and there is no independent/hands-on verification of the PR-opening workflow. Missing for 10: explicit branch-creation documentation, independent hands-on confirmation of commit/PR flow, and detail on staging-changes granularity.
- [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
- [claimed-docs] “Mention `@copilot` in a comment on an existing pull request to ask it to make changes.”
- [claimed-docs] “Launch work from GitHub, track progress across multiple agents, review changes, and merge completed work—all from one desktop workspace buil…”
- [claimed-docs] “Use one centralized control page to jump between agent sessions, check progress, and stay in control without losing your place.”
- [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
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.”
developerGet automatic code review with contextual feedback on every pull request
weight 3 · round to GitHub CopilotGitHub Copilot's docs explicitly describe automated PR code review with contextual feedback, suggested fixes, and severity labeling (High/Medium/Low) for prioritization, plus 'Access to Cloud agent and code review' as a plan feature. This directly matches the story's request for automatic, contextual PR review feedback. Missing for 10: independent/hands-on community evidence specifically validating the PR-review feature's accuracy or usefulness (community citations mostly discuss code completion, not the review feature) and detail on review-triggering automation reliability.
- [claimed-docs] “GitHub Copilot can review your code and provide feedback. Where possible, Copilot's feedback includes suggested changes which you can apply …”
- [claimed-docs] “Copilot labels each comment with a severity level of "High," "Medium," or "Low" to help you prioritize the issues it finds based on their im…”
- [claimed-docs] “Access to Cloud agent and code review”
Google Antigravitynone0/10Antigravity offers in-editor 'Review Changes' diff viewing and Artifact-based plan review, but there is no evidence of a GitHub/GitLab pull-request bot or CI-integrated review that automatically posts contextual feedback on every PR. The CLI headless mode allows scripting into CI, but no docs describe an automated PR-review workflow.
- [claimed-docs] “Planning Mode: The agent plans thoroughly before executing tasks... produces structured implementation plans called Artifacts”
- [claimed-docs] “The agent always halts and requests your explicit approval before proceeding with proposed changes.”
- [claimed-docs] “Added a "Hide Whitespace Changes" option to the Review Changes overflow menu and file diff viewers to filter out whitespace-only edits.”
- [claimed-docs] “Run Antigravity CLI non-interactively to script agent tasks, integrate with CI pipelines, and capture machine-readable output.”
developerInspect diffs and run checks to catch problems before merging
weight 3 · round to GitHub CopilotCopilot provides code review with inline suggested changes and severity-labeled comments (docs-28, docs-29), integrated with PR diffs, plus Autofix for vulnerability detection (docs-13) and agent mode validation of files (docs-22). This directly supports inspecting diffs and catching problems pre-merge. Missing for 10: independent/hands-on evidence of the code-review feature's real-world accuracy and no explicit mention of running CI/test checks as part of the flow.
- [claimed-docs] “GitHub Copilot can review your code and provide feedback. Where possible, Copilot's feedback includes suggested changes which you can apply …”
- [claimed-docs] “Copilot labels each comment with a severity level of "High," "Medium," or "Low" to help you prioritize the issues it finds based on their im…”
- [claimed-docs] “GitHub Copilot Autofix provides contextual explanations and code suggestions to help developers fix vulnerabilities in code”
- [claimed-docs] “Copilot in your editor does it all, from explaining concepts and completing code, to proposing edits and validating files with agent mode.”
- [claimed-docs] “Access to Cloud agent and code review”
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…”
Safe execution
engineering-leadControl which external tools and integrations the agent is allowed to access
weight 2 · round to GitHub CopilotGitHub Copilot provides explicit admin controls to allow-list MCP servers developers can access ('Control which MCP servers developers can access from their IDEs, and use allow lists to prevent unauthorized access'), plus a centralized control plane with audit logs for governance over agents. This directly matches the engineering-lead's need to restrict external tool/integration access. Missing for 10: independent/hands-on verification of the allow-list enforcement in practice, and more granular detail on per-tool (vs per-MCP-server) restriction scope.
- [claimed-docs] “Control which MCP servers developers can access from their IDEs, and use allow lists to prevent unauthorized access.”
- [claimed-docs] “Track activity with detailed audit logs and enforce governance by managing agents from a single control plane.”
- [claimed-docs] “Connect MCP servers to Copilot Chat to share context from other applications.”
Google Antigravitydisputedcontradicted5/10Antigravity 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'…”
engineering-leadHave the agent operate inside a sandbox when interacting with code, tools, and network resources
weight 2 · round to GitHub CopilotDocs explicitly state that Cloud and local sandboxes provide isolated execution environments letting Copilot safely interact with code, tools, filesystem, and network resources, either locally or in fully isolated cloud environments, with additional governance controls like MCP server allow lists and audit logs. Missing for 10: independent/hands-on verification of sandbox isolation guarantees and no detail on sandbox escape/limits.
- [claimed-docs] “Cloud and local sandboxes provide isolated execution environments that let Copilot safely interact with code, tools, filesystem, and network…”
- [claimed-docs] “Control which MCP servers developers can access from their IDEs, and use allow lists to prevent unauthorized access.”
- [claimed-docs] “Track activity with detailed audit logs and enforce governance by managing agents from a single control plane.”
Google Antigravitydisputedcontradicted4/10Antigravity 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…”
Security checks
engineering-leadSee license and public-code matching references for AI-suggested code
weight 1 · round to GitHub CopilotGitHub Copilot documents a public-code matching feature that searches public GitHub repos for matches to a suggestion (docs-11), which is the closest evidence to the story's ask. However, the evidence pack gives no detail on how license attribution is actually surfaced to an engineering lead, and community discussion raises real concerns about verbatim/near-verbatim reproduction and licensing risk (comm-12, comm-13, comm-14, comm-16), with only partial rebuttal (comm-17) — indicating the feature's coverage and reliability for license-safety review is limited. Missing for 10: detailed docs on license display/attribution UI, audit/reporting workflow for engineering leads, and independent verification that the matching feature reliably flags copyleft/licensed snippets.
- [claimed-docs] “This feature searches across public GitHub repositories for code that matches a Copilot suggestion.”
- [community] “It certainly seems to be a laundering enabler. Say that you want to un-GPL-ify some famous copylefted code... you type a first innocuous cha…”
- [community] “The potential inclusion of GPL'd code, and potentially even unlicensed code, is making me wary of using it. Fair Use doesn't exist here and …”
- [community] “'We found that about 0.1% of the time, the suggestion may contain some snippets that are verbatim from the training set.' If it's spitting o…”
- [community] “I just tested it myself on a random c file... it reproduced his full code verbatim from just the function header so clearly it does regurgit…”
- [community] “It prints this code because you have it open in another editor tab. Wish people who don't know at all how it works stopped acting all outrag…”
Google Antigravitynone0/10No 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.
developerGet contextual explanations and automatic fixes for security vulnerabilities
weight 2 · round to GitHub CopilotGitHub Copilot Autofix is explicitly documented to provide 'contextual explanations and code suggestions to help developers fix vulnerabilities in code' and Copilot code review adds severity-labeled feedback with suggested fixes, directly matching the story. However, this is first-party documentation only with no independent/hands-on validation of Autofix's real-world effectiveness, and no detail on scope/limitations (e.g., which languages, integration with Advanced Security). missing for 10: independent corroboration of Autofix accuracy, hands-on developer reports validating the fix quality, details on prerequisites/limitations of the feature.
- [claimed-docs] “GitHub Copilot Autofix provides contextual explanations and code suggestions to help developers fix vulnerabilities in code”
- [claimed-docs] “GitHub Copilot can review your code and provide feedback. Where possible, Copilot's feedback includes suggested changes which you can apply …”
- [claimed-docs] “Copilot labels each comment with a severity level of "High," "Medium," or "Low" to help you prioritize the issues it finds based on their im…”
Google Antigravitynone0/10No 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.
Not comparable on these axes
ai-native userConnect an agent via an official MCP server
weight 3 · not comparableGitHub documents an official GitHub MCP server (docs-25) that exposes repositories, issues, PRs, and other GitHub features via MCP, which other agents (not just Copilot itself) can connect to — this is a first-party server, not just Copilot's client-side MCP consumption. Missing for 10: independent/hands-on confirmation of third-party agents successfully connecting to this server, and details on server versioning/maturity.
- [claimed-docs] “Learn how to use the GitHub Model Context Protocol (MCP) server to interact with repositories, issues, pull requests, and other GitHub featu…”
- [claimed-docs] “Copilot works where you do—in GitHub, your IDE, the CLI, project tools, chat apps, and custom MCP servers.”
- [claimed-docs] “Control which MCP servers developers can access from their IDEs, and use allow lists to prevent unauthorized access.”
Google Antigravityn/aAntigravity is itself an agentic coding product (IDE/CLI/SDK) that acts as an MCP client—connecting to external MCP servers for tools/context (antigravity-docs-12, antigravity-docs-14, antigravity-docs-22, antigravity-docs-43)—rather than exposing itself as an MCP server for other agents to connect to. Per the agent-role exception, this axis (serving an official MCP server) does not apply to a product that is itself the agent/client.
- [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] “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”
ai-native userExplore an interactive API reference with runnable examples
weight 2 · not comparableGitHub Copilotnone0/10The evidence pack shows no interactive API reference or runnable-example explorer for GitHub Copilot; a direct probe for OpenAPI/Swagger specs returned 404s on all candidate paths, and docs are plain markdown/text pages rather than an interactive API console.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.github.com/openapi.json, https://docs.github.com/swagger.json, https://docs.github.com/…”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.github.com/llms.txt # GitHub Docs > GitHub is a developer platform for building, shipping, and mai…”
- [probe] “PROBE docs-md: HTTP 200 at https://docs.github.com/copilot.md # GitHub Copilot documentation You can use GitHub Copilot to enhance your pro…”
Google Antigravityn/aAntigravity is an agentic coding IDE/CLI/SDK product, not an API/SaaS service exposing a public API surface meant for interactive exploration; the probe explicitly found no OpenAPI spec. An interactive API reference with runnable examples is not a fair axis for this kind of developer tool.
- [probe] “PROBE openapi: all candidate paths 404 (https://antigravity.google/openapi.json, https://antigravity.google/swagger.json, https://antigravit…”
developerConfigure a reproducible cloud environment with the dependencies and setup steps my repository needs
weight 2 · not comparableDocs mention 'Cloud and local sandboxes provide isolated execution environments' for Copilot cloud agent and background task automation, implying some environment abstraction, but there is no explicit evidence of a mechanism (e.g., a setup-steps config, devcontainer, or dependency manifest) for developers to define reproducible cloud environment setup steps. Missing for 10: explicit documentation of a configuration file/workflow for specifying dependencies/setup steps, independent confirmation of reproducibility across runs.
- [claimed-docs] “Cloud and local sandboxes provide isolated execution environments that let Copilot safely interact with code, tools, filesystem, and network…”
- [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
- [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
Google Antigravityn/aAntigravity is a local IDE/CLI/agent orchestration tool operating on a developer's own machine (or remote desktop sessions), not a cloud environment provisioning/dev-container service; there is no evidence of configuring reproducible cloud sandboxes with dependency/setup steps tied to a repo. This axis is a category error for this product type.