Cursor vs Gemini CLI

Agent access

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

   weight 2 · round drawn
   Cursor—none0/10

   No evidence pack item mentions llms.txt, agent-oriented documentation ingestion, or a mechanism to point Cursor's agent at such files; only generic doc/MCP/tooling references are present. missing for 10: any mention of llms.txt support, crawling agent-oriented doc formats, or a documented feature for feeding external agent docs to Cursor's agent.

   ⚑ flag

   Gemini CLI—none0/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Gemini CLI
   Cursor~partialprobed6/10

   Cursor ships an official CLI (cursor.com/cli, curl installer) and background/cloud agents that run 'on schedules or triggers' to build and fix software autonomously, which implies non-interactive/headless automation. However, there is no explicit documentation of CI pipeline integration, exit codes, or scripting examples for pipelines. Missing for 10: explicit CI/CD integration docs (e.g., GitHub Actions example), documented headless flags/exit-code behavior, and independent confirmation of CLI use in automated pipelines.

   • [probe] “official CLI documented at https://cursor.com/cli”
   • [claimed-docs] “curl https://cursor.com/install -fsS | bash”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Gemini CLI✓fullclaimed9/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Cursor✓fullclaimed8/10

   Cursor's docs explicitly describe MCP support: connecting to external tools/data sources, marketplace one-click install with OAuth, custom JSON server configuration, toggling servers, and enterprise admin controls over allowed servers. This directly matches the story of plugging in MCP servers so the agent can use their tools. Missing for 10: independent hands-on verification of MCP tool usage in practice and no community corroboration of the feature's reliability.

   • [claimed-docs] “Model Context Protocol (MCP) enables Cursor to connect to external tools and data sources.”
   • [claimed-docs] “Click "Add to Cursor" on a marketplace entry to install it and authenticate with OAuth.”
   • [claimed-docs] “Configure custom MCP servers with a JSON file”
   • [claimed-docs] “Enterprise admins can control which MCP servers users may run from the Cursor dashboard.”
   • [claimed-docs] “Toggle servers on/off without removing them”

   proof ↗⚑ flag

   Gemini CLI✓fullclaimed8/10

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

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

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Gemini CLI
   Cursor✓fullprobed8/10

   Cursor documents an official CLI with an install command (curl https://cursor.com/install) and a dedicated CLI docs page (cursor.com/cli), confirming a first-party terminal tool for AI-native workflows. Missing for 10: independent/hands-on corroboration of CLI capabilities and depth of documentation beyond install instructions.

   • [claimed-docs] “curl https://cursor.com/install -fsS | bash”
   • [claimed-docs] “Cursor runs in your terminal, collaborates in Slack, and reviews PRs in GitHub.”
   • [probe] “official CLI documented at https://cursor.com/cli”

   proof ↗⚑ flag

   Gemini CLI✓fullprobed9/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Gemini CLI
   Cursor~partialprobed3/10

   Evidence shows an official CLI (cursor.com/cli) that lets users invoke Cursor from scripts, which partially satisfies 'driving the product programmatically,' but there is no documented public REST/SDK API, authentication scheme, or endpoint reference — MCP docs describe Cursor consuming external tools, not exposing itself as an API. Missing for 10: documented REST/GraphQL API, SDK/client libraries, API authentication and rate-limit docs, independent corroboration of programmatic usage.

   • [probe] “official CLI documented at https://cursor.com/cli”
   • [claimed-docs] “curl https://cursor.com/install -fsS | bash”

   proof ↗⚑ flag

   Gemini CLI~partialprobed5/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Cursor—none0/10

   No evidence Cursor lets users mint scoped or least-privilege API credentials for agents; docs cover MCP server toggling and enterprise admin control of which servers can run, but nothing about issuing scoped/limited API keys or credentials specifically for agent use.

   ⚑ flag

   Gemini CLI—none0/10

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

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

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Cursor—none0/10

   Evidence shows Cursor offers a CLI, MCP integration, and marketplace extensions, but there is no mention of any official SDK (e.g., a documented library/API package) for developers to build against Cursor itself.

   ⚑ flag

   Gemini CLI—none0/10

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

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

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Cursor—none0/10

   Evidence covers MCP integration, background agents, and IDE integrations, but there is no mention of a webhook subscription mechanism for external event notifications.

   ⚑ flag

   Gemini CLI—none0/10

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

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

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to Cursor
   Cursor✓fullclaimed7/10

   Cursor's core value proposition is analyzing the user's codebase to surface AI-generated insights (tracing repo structure, finding root causes, reviewing diffs) and suggestions for next actions, as documented across multiple first-party docs. Missing for 10: independent/hands-on evidence validating the accuracy or depth of these insights, and no detail on insight types beyond code-centric suggestions (e.g., data analytics or business data outside code).

   • [claimed-docs] “Trace how a repo fits together and find the right places to start”
   • [claimed-docs] “Scope changes, use Plan Mode, and ship bigger work with confidence”
   • [claimed-docs] “Reproduce issues, narrow the root cause, and verify the fix”
   • [claimed-docs] “Inspect diffs, run checks, and catch problems before you merge”

   proof ↗⚑ flag

   Gemini CLI!disputedcontradicted5/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Cursor
   Cursor✓fullclaimed8/10

   Cursor explicitly documents 'always-on agents that run on schedules or triggers to build, maintain, and fix your software' and 'fleets of agents that work in parallel for hours or days,' directly matching autonomous background automation. This is first-party vendor documentation without independent hands-on corroboration of scheduling/triggers working reliably. Missing for 10: independent/community verification that scheduled/triggered background agents work reliably in practice, and more detail on trigger configuration options.

   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Gemini CLI~partialcommunity6/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Cursor
   Cursor✓fullclaimed9/10

   Cursor's docs clearly describe delegating tasks to built-in agents that plan, code, test, and demo work end-to-end while the user focuses on review/decisions, including background/parallel agents and always-on scheduled agents. This is a core, heavily documented capability of the product, though independent hands-on validation of agent task quality is thin (only general community commentary, some critical, exists). Missing for 10: deeper independent verification of agent task success rates beyond vendor docs.

   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Accelerate development by handing off tasks to Cursor, while you focus on making decisions.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”
   • [claimed-docs] “Scope changes, use Plan Mode, and ship bigger work with confidence”

   proof ↗⚑ flag

   Gemini CLI!disputedcontradicted5/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Cursor
   Cursor✓fullclaimed8/10

   Cursor's core interaction model is natural-language driven agents that plan, code, test, and operate across terminal/Slack/GitHub (cursor-docs-2, cursor-docs-8, cursor-docs-9, cursor-docs-10, cursor-docs-11), consistent with an AI-native product. Missing for 10: independent hands-on evidence specifically validating natural-language command reliability/accuracy (community evidence focuses on bugginess/pricing complaints unrelated to NL command capability itself).

   • [claimed-docs] “Scope changes, use Plan Mode, and ship bigger work with confidence”
   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Cursor runs in your terminal, collaborates in Slack, and reviews PRs in GitHub.”
   • [claimed-docs] “Accelerate development by handing off tasks to Cursor, while you focus on making decisions.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Gemini CLI!disputedcontradicted5/10

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

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

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Cursor—none0/10

   No evidence of an interactive API reference with runnable examples for Cursor; docs entries describe product features and MCP setup but nothing about an API reference or executable code samples.

   ⚑ flag

   Gemini CLI—none0/10

   No evidence of an interactive API reference with runnable examples; probes explicitly show no llms.txt or OpenAPI spec found, and no docs describe an interactive reference tool.

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Cursor—none0/10

   No evidence of Cursor publishing a downloadable OpenAPI or equivalent machine-readable API spec; docs reference MCP config and CLI but not an API spec.

   ⚑ flag

   Gemini CLI—none0/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Cursor—none0/10

   No evidence in the pack mentions API versioning or a deprecation policy for Cursor's APIs (CLI, extensions, or MCP config); docs cover features like MCP setup, agents, and integrations but nothing about version stability guarantees or deprecation timelines.

   ⚑ flag

   Gemini CLI—none0/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Gemini CLI
   Cursor~partialclaimed5/10

   Cursor supports launching 'fleets of agents' in parallel and always-on scheduled/triggered agents, which enables some multi-item automation, but there's no direct evidence of bulk operations across many discrete items (e.g., bulk file edits, batch refactors, or multi-repo operations) as a first-class feature. missing for 10: explicit documentation or hands-on evidence of bulk/batch operations across many items (files, tickets, repos), user-facing UI for selecting many items at once, and independent corroboration of this working in practice.

   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”

   proof ↗⚑ flag

   Gemini CLI~partialcommunity6/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Cursor
   Cursor~partialclaimed6/10

   Cursor docs describe 'always-on agents that run on schedules or triggers' and a way to 'add rules' from one place, matching the idea of rule-based automation triggered by events. However the evidence pack doesn't detail how rules are authored/scoped to specific events beyond the marketing blurb, and there's no independent/hands-on confirmation of this automation working as described. Missing for 10: concrete rule-definition syntax/examples, independent verification that scheduled/triggered agents reliably fire on events, and detail on event types supported.

   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Add plugins, skills, MCPs, and rules from one place”

   proof ↗⚑ flag

   Gemini CLI~partialclaimed5/10

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

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

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Cursor
   Cursor✓fullclaimed7/10

   Cursor documents 'always-on agents that run on schedules or triggers to build, maintain, and fix your software,' directly matching recurring scheduled workflow automation, alongside parallel agent fleets for ambitious tasks. Missing for 10: independent hands-on verification of scheduling reliability, details on trigger configuration options, and any community corroboration of this specific feature working in practice.

   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”

   proof ↗⚑ flag

   Gemini CLI~partialclaimed4/10

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

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

   proof ↗⚑ flag

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

   weight 1 · round to Gemini CLI
   Cursor—none0/10

   Evidence shows Cursor can inspect diffs and review changes before merge, but there is no documented capability to version, review, or roll back the automations themselves (e.g., scheduled/always-on agents, rules, MCP configs) as distinct artifacts with history/rollback support.

   ⚑ flag

   Gemini CLI~partialclaimed4/10

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

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

   proof ↗⚑ flag

Background execution

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

   weight 2 · round to Cursor
   Cursor✓fullclaimed7/10

   Cursor's docs explicitly describe cloud/background agents that 'use their own computers to build, test, and demo features end to end for you to review,' plus the ability to launch fleets of agents working in parallel for hours/days, and always-on scheduled agents — directly matching the story. Corroboration is entirely first-party marketing/docs rather than independent hands-on verification of an actual demo workflow. Missing for 10: independent/hands-on evidence confirming the build-test-demo loop works reliably end-to-end, and detail on what 'demo' concretely produces (e.g., preview links, recordings).

   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Accelerate development by handing off tasks to Cursor, while you focus on making decisions.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Gemini CLI~partialcommunity4/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Cursor
   Cursor✓fullclaimed8/10

   Cursor documents cloud/background agents ('Agents use their own computers to build, test, and demo features end to end', 'Launch fleets of agents that work in parallel on ambitious tasks for hours or days', and hand-off delegation while the developer focuses elsewhere), matching the isolated cloud-background-task story. Missing for 10: independent hands-on verification of the background agent's isolation/reliability and details on session duration limits or failure modes.

   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”
   • [claimed-docs] “Accelerate development by handing off tasks to Cursor, while you focus on making decisions.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”

   proof ↗⚑ flag

   Gemini CLI~partialclaimed4/10

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

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

   proof ↗⚑ flag

3. developerConfigure a reproducible cloud environment with the dependencies and setup steps my repository needs

   weight 2 · round to Cursor
   Cursor~partialclaimed4/10

   Cursor's docs mention cloud/background agents that 'use their own computers to build, test, and demo features' and can be launched in fleets or run on schedules, implying some cloud execution environment, but there's no evidence pack detail on how a developer configures dependencies, install scripts, or a reproducible environment spec (e.g. Dockerfile/environment.json) for these agents. Missing for 10: explicit documentation of environment configuration format, dependency/setup step definition, and evidence of reproducibility across runs.

   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Gemini CLI—none0/10

   Evidence shows Gemini CLI can run in Cloud Shell without extra setup and supports GEMINI.md context files, but there is no evidence of a configurable, reproducible cloud environment (e.g., dependency/setup scripts, devcontainer-style config) that a developer can define for their repo. Missing for 10: any documented environment/setup-script configuration mechanism, evidence of reproducibility across runs, and independent confirmation it works as such.

   • [claimed-docs] “The Gemini CLI is available without additional setup in Cloud Shell”
   • [github] “Custom context files (GEMINI.md) to tailor behavior for your projects”

   proof ↗⚑ flag

Parallel agents

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

   weight 2 · round to Cursor
   Cursor✓fullclaimed8/10

   First-party marketing/docs explicitly state the exact capability: "Launch fleets of agents that work in parallel on ambitious tasks for hours or days," plus supporting evidence of background/always-on agents and agents using their own compute to build/test/demo. No independent hands-on verification of multi-day parallel fleet execution is present, and no community corroboration confirms this specific feature works at scale. Missing for 10: independent/hands-on validation of parallel agent fleets running for hours/days, details on concurrency limits or reliability over long runs.

   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”
   • [claimed-docs] “Accelerate development by handing off tasks to Cursor, while you focus on making decisions.”

   proof ↗⚑ flag

   Gemini CLI—none0/10

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

   ⚑ flag

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

   weight 1 · round to Cursor
   Cursor~partialclaimed6/10

   Cursor's docs describe launching 'fleets of agents that work in parallel on ambitious tasks for hours or days,' directly supporting parallel task execution, and agents run in isolated environments for review before merging changes. However, there is no explicit documentation of a UI/workflow for comparing multiple parallel attempts side-by-side before choosing one, and no independent/hands-on evidence corroborating this specific comparison workflow. Missing for 10: dedicated compare/diff-across-attempts feature documentation, independent verification of parallel-agent comparison in practice.

   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Gemini CLI—none0/10

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

   ⚑ flag

Scheduled automation

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

   weight 2 · round to Cursor
   Cursor✓fullclaimed8/10

   Cursor's own site directly states the capability: "Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software," plus related background-agent features (parallel fleets, agents running on their own machines) that support this workflow. Missing for 10: independent/hands-on confirmation of scheduled/triggered agents actually running reliably in practice, and more detail on trigger types/configuration.

   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Gemini CLI~partialcommunity4/10

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

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

   proof ↗⚑ flag

Debugging

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

   weight 1 · round to Gemini CLI
   Cursor—none0/10

   No evidence pack item describes attaching a debugger, inspecting runtime state, or interacting with a live running web app from Cursor; docs mention reproducing issues and root-causing bugs conceptually, but not live-app debugging integration (e.g., breakpoints, browser dev tools, runtime inspection). missing for 10: evidence of live debugger attach/breakpoints, browser/runtime inspection tooling, or integration with running app state.

   • [claimed-docs] “Reproduce issues, narrow the root cause, and verify the fix”
   • [claimed-docs] “Inspect diffs, run checks, and catch problems before you merge”

   proof ↗⚑ flag

   Gemini CLI~partialcommunity3/10

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

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

   proof ↗⚑ flag

2. developerDebug issues and troubleshoot using natural-language queries

   weight 2 · round to Cursor
   Cursor~partialcommunity6/10

   cursor-docs-3 directly claims support for reproducing issues, narrowing root cause, and verifying fixes via natural-language-driven agent workflows, and docs-1 supports tracing how a repo fits together to find bug locations. However, there's no independent/hands-on evidence corroborating debugging quality, and community evidence highlights buginess and unreliability concerns (cursor-comm-2, cursor-comm-8) that add caveats without directly contradicting the specific debugging workflow claim. Missing for 10: independent verification of debugging accuracy, concrete examples of NL-driven troubleshooting sessions, and resolution of buggy-product complaints.

   • [claimed-docs] “Trace how a repo fits together and find the right places to start”
   • [claimed-docs] “Reproduce issues, narrow the root cause, and verify the fix”
   • [community] “"Cursor is weird. They have a basically unused GitHub with a thousand unanswered Issues. It's so buggy in ways that VSCode isn't. I hate it.…”
   • [community] “"That's a lot of money for a buggy product that is at best slightly better than its competitors."”

   proof ↗⚑ flag

   Gemini CLI!disputedcontradicted5/10

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

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

   proof ↗⚑ flag

Feature implementation

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

   weight 3 · round to Cursor
   Cursor~partialclaimed7/10

   Cursor's docs describe agents that trace repos, plan changes, reproduce issues, inspect diffs/run checks, and integrate with issue trackers (GitHub, Linear) and PR review, which together support a full issue-to-PR workflow (cursor-docs-1 through cursor-docs-4, cursor-docs-6, cursor-docs-8–cursor-docs-12). However, there's no explicit first-party or independent case study showing a single tracked issue being turned into a merged PR end-to-end without manual intervention, and community evidence focuses on unrelated bugs/pricing complaints rather than this workflow. Missing for 10: a concrete end-to-end example/case study of issue→PR automation and independent verification that the full pipeline works reliably.

   • [claimed-docs] “Trace how a repo fits together and find the right places to start”
   • [claimed-docs] “Scope changes, use Plan Mode, and ship bigger work with confidence”
   • [claimed-docs] “Reproduce issues, narrow the root cause, and verify the fix”
   • [claimed-docs] “Inspect diffs, run checks, and catch problems before you merge”
   • [claimed-docs] “Work with GitHub, GitLab, Azure DevOps, Bitbucket, JetBrains, Slack, Linear, and more”
   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Cursor runs in your terminal, collaborates in Slack, and reviews PRs in GitHub.”
   • [claimed-docs] “Accelerate development by handing off tasks to Cursor, while you focus on making decisions.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Gemini CLI!disputedcontradicted5/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Cursor
   Cursor✓fullcommunity8/10

   Cursor's docs describe an agent that traces repo structure, plans and scopes multi-file changes, implements features/fixes end-to-end, runs checks, and produces diffs for review — directly matching plain-language feature/bug requests across multiple files. Community evidence corroborates the product is used daily for this purpose (albeit with complaints about bugginess), without disputing the core multi-file agentic editing capability. Missing for 10: independent hands-on benchmarks showing successful multi-file fixes, and no first-party demo/case study detailing a concrete before/after example.

   • [claimed-docs] “Trace how a repo fits together and find the right places to start”
   • [claimed-docs] “Scope changes, use Plan Mode, and ship bigger work with confidence”
   • [claimed-docs] “Reproduce issues, narrow the root cause, and verify the fix”
   • [claimed-docs] “Inspect diffs, run checks, and catch problems before you merge”
   • [claimed-docs] “Accelerate development by handing off tasks to Cursor, while you focus on making decisions.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”
   • [community] “"Cursor is weird. They have a basically unused GitHub with a thousand unanswered Issues. It's so buggy in ways that VSCode isn't. I hate it.…”
   • [community] “"That's a lot of money for a buggy product that is at best slightly better than its competitors."”

   proof ↗⚑ flag

   Gemini CLI!disputedcontradicted5/10

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

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

   proof ↗⚑ flag

Maintenance automation

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

   weight 3 · round to Cursor
   Cursor~partialclaimed6/10

   Cursor's docs describe agents that write code, run tests/checks, and 'build, maintain, and fix' software autonomously (cursor-docs-3, cursor-docs-4, cursor-docs-9, cursor-docs-12), which implies test-writing and general maintenance tasks, but there is no explicit documentation of lint-error fixing, merge-conflict resolution, or dependency-update workflows specifically. missing for 10: explicit lint-fixing examples, explicit merge-conflict-resolution examples, explicit dependency-update examples, independent hands-on verification of these specific tasks.

   • [claimed-docs] “Reproduce issues, narrow the root cause, and verify the fix”
   • [claimed-docs] “Inspect diffs, run checks, and catch problems before you merge”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Gemini CLI!disputedcontradicted5/10

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

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

   proof ↗⚑ flag

Multimodal generation

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

   weight 2 · round to Gemini CLI
   Cursor—none0/10

   No evidence in the pack describes image/sketch/PDF-to-app generation, multimodal design input, or any UI-from-design workflow; the docs snippets cover repo navigation, plan mode, agents, MCP, and integrations but nothing about visual design inputs.

   ⚑ flag

   Gemini CLI~partialcommunity6/10

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

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

   proof ↗⚑ flag

Codebase mapping

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

   weight 3 · round to Cursor
   Cursor~partialclaimed6/10

   Cursor's docs explicitly claim the ability to 'trace how a repo fits together and find the right places to start,' directly matching the story, but this is a single marketing-style doc line with no detailed walkthrough, feature docs (e.g., codebase indexing/@codebase chat), or independent corroboration of how it actually surfaces architecture understanding. Missing for 10: detailed documentation of the codebase-mapping/indexing feature itself, concrete examples of it locating relevant code, and independent/hands-on validation of accuracy.

   • [claimed-docs] “Trace how a repo fits together and find the right places to start”

   proof ↗⚑ flag

   Gemini CLI!disputedcontradicted5/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Cursor
   Cursor~partialclaimed4/10

   First-party docs claim Cursor can 'trace how a repo fits together and find the right places to start' (cursor-docs-1), implying automatic codebase mapping, but there's no detail on how context is auto-gathered (e.g., codebase indexing/@codebase) nor any independent/hands-on confirmation that it explains an unfamiliar codebase without manual file selection. Missing for 10: technical explanation of automatic context retrieval, independent user validation of whole-codebase explanation, and comparison to manual context selection workflows.

   • [claimed-docs] “Trace how a repo fits together and find the right places to start”

   proof ↗⚑ flag

   Gemini CLI!disputedcontradicted5/10

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

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

   proof ↗⚑ flag

Context management

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

   weight 2 · round to Gemini CLI
   Cursor—none0/10

   No evidence describes persistent memory that automatically builds and recalls context across sessions; docs mention repo tracing, plan mode, and MCP integrations but nothing about cross-session memory recall.

   ⚑ flag

   Gemini CLI!disputedcontradicted3/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Gemini CLI
   Cursor—none0/10

   No evidence in the pack mentions multi-root workspaces or including multiple project directories in a single Cursor session; docs cover repo navigation, MCP, agents, and integrations but not multi-directory context.

   ⚑ flag

   Gemini CLI✓fullclaimed8/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Cursor
   Cursor~partialclaimed3/10

   Cursor's docs mention adding 'rules' as one of its features (alongside plugins, skills, MCPs) which aligns with the project-instructions concept, but the evidence pack gives no detail on how project rule files work, their scope, or how the agent applies them to enforce coding standards. missing for 10: documentation of the rules file format/location, examples of coding standards enforcement, independent confirmation the agent actually follows these instructions consistently.

   • [claimed-docs] “Add plugins, skills, MCPs, and rules from one place”

   proof ↗⚑ flag

   Gemini CLI!disputedcontradicted5/10

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

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

   proof ↗⚑ flag

Issue diagnosis

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

   weight 3 · round to Cursor
   Cursor~partialclaimed6/10

   cursor-docs-3 directly claims the exact capability ('Reproduce issues, narrow the root cause, and verify the fix'), and supporting docs on codebase tracing, diffs/checks, and agents running their own environments (cursor-docs-1, cursor-docs-4, cursor-docs-12) plausibly back this workflow. However, this is a first-party marketing/docs claim only, with no independent or hands-on corroboration of actual debugging workflows, and community evidence highlights general bugginess/quality concerns rather than validating this specific capability. Missing for 10: independent verification or hands-on case studies of reproduce/root-cause/verify-fix workflows, more detail on how reproduction (e.g., test running, log inspection) is concretely supported.

   • [claimed-docs] “Reproduce issues, narrow the root cause, and verify the fix”
   • [claimed-docs] “Trace how a repo fits together and find the right places to start”
   • [claimed-docs] “Inspect diffs, run checks, and catch problems before you merge”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Gemini CLI!disputedcontradicted4/10

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

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

   proof ↗⚑ flag

Marketplace

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

   weight 1 · round drawn
   Cursor~partialclaimed6/10

   Cursor's docs mention a marketplace to 'Add plugins, skills, MCPs, and rules from one place' and detailed MCP support (custom servers, marketplace install, enterprise controls), enabling developers to extend the agent with specialized tool integrations. However, there's no dedicated documentation on a 'skills' framework distinct from MCP/rules, no examples of custom skill creation workflow, and no independent/community corroboration of this specific capability. Missing for 10: detailed skills documentation/tutorial, examples of custom skill authoring, independent hands-on validation.

   • [claimed-docs] “Add plugins, skills, MCPs, and rules from one place”
   • [claimed-docs] “Model Context Protocol (MCP) enables Cursor to connect to external tools and data sources.”
   • [claimed-docs] “Click "Add to Cursor" on a marketplace entry to install it and authenticate with OAuth.”
   • [claimed-docs] “Configure custom MCP servers with a JSON file”
   • [claimed-docs] “Enterprise admins can control which MCP servers users may run from the Cursor dashboard.”

   proof ↗⚑ flag

   Gemini CLI~partialcommunity6/10

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

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

   proof ↗⚑ flag

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

   weight 1 · round to Cursor
   Cursor✓fullclaimed7/10

   Cursor documents a marketplace for adding third-party plugins, skills, and MCP servers with OAuth authentication, plus native integrations with GitHub, GitLab, Slack, Linear, and more, letting teams plug partner-built tools/agents into their workflows, with enterprise admin controls over which servers are allowed. Missing for 10: independent/hands-on corroboration of using specific partner-built agent apps (vs. generic tool connectors) and clearer distinction between simple MCP data-tools and full third-party 'agent apps'.

   • [claimed-docs] “Add plugins, skills, MCPs, and rules from one place”
   • [claimed-docs] “Work with GitHub, GitLab, Azure DevOps, Bitbucket, JetBrains, Slack, Linear, and more”
   • [claimed-docs] “Model Context Protocol (MCP) enables Cursor to connect to external tools and data sources.”
   • [claimed-docs] “Click "Add to Cursor" on a marketplace entry to install it and authenticate with OAuth.”
   • [claimed-docs] “Configure custom MCP servers with a JSON file”
   • [claimed-docs] “Enterprise admins can control which MCP servers users may run from the Cursor dashboard.”

   proof ↗⚑ flag

   Gemini CLI~partialclaimed5/10

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

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

   proof ↗⚑ flag

Team knowledge

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

   weight 1 · round drawn
   Cursor—none0/10

   Evidence shows integrations (GitHub, Slack, Linear), MCP/plugins, and rules configuration, but nothing describes a dedicated 'shared workspace' feature that unifies docs and repos into a common team source of truth — this is a fair ask for a team-oriented dev tool but unaddressed in the pack.

   ⚑ flag

   Gemini CLI—none0/10

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

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

   proof ↗⚑ flag

Tool integration

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

   weight 3 · round to Cursor
   Cursor✓fullclaimed8/10

   Cursor documents MCP support that connects to external tools/data sources, an MCP marketplace with OAuth install, and explicit integration with Slack alongside GitHub/GitLab/Linear/Jira-style trackers, plus Slack-based agent collaboration—covering the story's workflow-tool extension use case. Missing for 10: explicit first-party Jira/Google Drive connector documentation and independent hands-on verification of these integrations working end-to-end.

   • [claimed-docs] “Model Context Protocol (MCP) enables Cursor to connect to external tools and data sources.”
   • [claimed-docs] “Click "Add to Cursor" on a marketplace entry to install it and authenticate with OAuth.”
   • [claimed-docs] “Configure custom MCP servers with a JSON file”
   • [claimed-docs] “Work with GitHub, GitLab, Azure DevOps, Bitbucket, JetBrains, Slack, Linear, and more”
   • [claimed-docs] “Cursor runs in your terminal, collaborates in Slack, and reviews PRs in GitHub.”

   proof ↗⚑ flag

   Gemini CLI~partialclaimed5/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Cursor
   Cursor~partialclaimed7/10

   Cursor's docs explicitly list integrations with GitHub, GitLab, Slack, and Linear, and describe agents that run on triggers/schedules and collaborate in Slack or review PRs in GitHub, supporting the story's core claim. However, there's no detailed first-party documentation of the exact trigger mechanics per platform (e.g., a Linear ticket auto-spawning an agent) nor independent/hands-on confirmation that this works reliably. Missing for 10: platform-specific trigger documentation for each of GitHub/GitLab/Linear/Slack, and independent verification of the workflow in practice.

   • [claimed-docs] “Work with GitHub, GitLab, Azure DevOps, Bitbucket, JetBrains, Slack, Linear, and more”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Cursor runs in your terminal, collaborates in Slack, and reviews PRs in GitHub.”

   proof ↗⚑ flag

   Gemini CLI~partialclaimed4/10

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

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

   proof ↗⚑ flag

Cross device continuity

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

   weight 2 · round to Cursor
   Cursor~partialclaimed5/10

   Cursor's Background Agents run remotely and can be monitored/interacted with via terminal, Slack, and GitHub PRs, implying a task could be checked or continued from different surfaces, but there is no explicit documentation of resuming a specific in-progress task from a different device or browser session. Missing for 10: explicit cross-device/browser session handoff documentation, hands-on confirmation of resuming a task started elsewhere, and details on state syncing across clients.

   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Cursor runs in your terminal, collaborates in Slack, and reviews PRs in GitHub.”
   • [claimed-docs] “Accelerate development by handing off tasks to Cursor, while you focus on making decisions.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Gemini CLI—none0/10

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

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

   proof ↗⚑ flag

Ide integration

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

   weight 1 · round drawn
   Cursor—none0/10

   The only evidence touching JetBrains is a single line listing JetBrains among integrations (cursor-docs-6), with no detail on interactive diffs or context-sharing features within a JetBrains IDE specifically. No documentation, screenshots, or community reports confirm this JetBrains-specific capability.

   • [claimed-docs] “Work with GitHub, GitLab, Azure DevOps, Bitbucket, JetBrains, Slack, Linear, and more”

   proof ↗⚑ flag

   Gemini CLI—none0/10

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

   ⚑ flag

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

   weight 3 · round to Cursor
   Cursor✓fullcommunity7/10

   Cursor's docs describe an IDE-integrated assistant that traces repo structure, scopes changes via Plan Mode, reproduces issues, and hands off tasks while the developer reviews — all consistent with in-IDE contextual chat, and community commentary confirms it functions as a VS Code-based assistant with prompts/harness. missing for 10: no explicit citation naming a dedicated 'chat panel' UI or independent praise of chat quality/context-awareness specifically.

   • [claimed-docs] “Trace how a repo fits together and find the right places to start”
   • [claimed-docs] “Scope changes, use Plan Mode, and ship bigger work with confidence”
   • [claimed-docs] “Reproduce issues, narrow the root cause, and verify the fix”
   • [claimed-docs] “Accelerate development by handing off tasks to Cursor, while you focus on making decisions.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”
   • [community] “"Cursor is an extension for VS Code, a harness and a bunch of prompts. They have their own model (Composer 2) which is based on Kimi K2.5, b…”

   proof ↗⚑ flag

   Gemini CLI—none0/10

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

   ⚑ flag

Session management

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

   weight 2 · round to Cursor
   Cursor✓fullclaimed7/10

   Cursor's docs explicitly describe launching 'fleets of agents that work in parallel on ambitious tasks for hours or days' and setting up always-on agents on schedules/triggers, all accessible from Cursor's interface spanning terminal, Slack, and GitHub — directly matching a unified multi-session agent workspace for a lead overseeing parallel work. Missing for 10: independent/hands-on corroboration of the multi-agent dashboard UX, and no detail on cross-session visibility/coordination features specifically framed for engineering-lead oversight.

   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Cursor runs in your terminal, collaborates in Slack, and reviews PRs in GitHub.”
   • [claimed-docs] “Accelerate development by handing off tasks to Cursor, while you focus on making decisions.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Gemini CLI—none0/10

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

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

   proof ↗⚑ flag

Terminal workflow

1. developerRun a coding agent locally from my terminal

   weight 3 · round to Gemini CLI
   Cursor✓fullprobed7/10

   Cursor ships an official CLI (cursor.com/cli) with a documented install command (curl ... | bash) and docs explicitly state 'Cursor runs in your terminal', confirming a local terminal-based agent capability alongside its IDE. Missing for 10: independent/hands-on verification of terminal agent usage and deeper CLI usage documentation beyond the install step.

   • [probe] “official CLI documented at https://cursor.com/cli”
   • [claimed-docs] “curl https://cursor.com/install -fsS | bash”
   • [claimed-docs] “Cursor runs in your terminal, collaborates in Slack, and reviews PRs in GitHub.”

   proof ↗⚑ flag

   Gemini CLI✓fullcommunity8/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Gemini CLI
   Cursor~partialprobed6/10

   Cursor ships an official CLI (cursor-probe-1, cursor-docs-14) and documents 'always-on agents that run on schedules or triggers to build, maintain, and fix your software' (cursor-docs-9), which implies non-interactive/automated agent execution suitable for scripts/CI. However, there is no concrete documentation of CLI flags, headless/print modes, exit codes, or scripting examples, nor independent hands-on confirmation of this workflow. Missing for 10: explicit CLI non-interactive flag/usage docs, examples of piping/scripting the agent, and independent verification that scheduled/triggered agents work as scripted automation.

   • [probe] “official CLI documented at https://cursor.com/cli”
   • [claimed-docs] “curl https://cursor.com/install -fsS | bash”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”

   proof ↗⚑ flag

   Gemini CLI✓fullclaimed9/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Gemini CLI
   Cursor—none0/10

   The evidence pack shows no public API for Cursor; it mentions an official CLI and MCP (for connecting external tools INTO Cursor), but nothing about a programmatic interface exposing Cursor's own UI capabilities (agents, plan mode, review, etc.) for external control.

   ⚑ flag

   Gemini CLI~partialprobed5/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Cursor—none0/10

   No evidence in the pack addresses data export, portability, or open-format data extraction from Cursor; being built on VS Code (a fork) doesn't itself guarantee user data/settings export tooling is documented anywhere here.

   ⚑ flag

   Gemini CLI—none0/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Gemini CLI
   Cursor—none0/10

   Cursor is known to be closed-source (a proprietary VS Code fork), and the evidence pack contains no mention of any open-source license or public repository for Cursor's source code; all references are to product docs, features, or community complaints unrelated to licensing.

   ⚑ flag

   Gemini CLI~partialprobed5/10

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

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

   proof ↗⚑ flag

Authentication

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

   weight 2 · round to Gemini CLI
   Cursor—none0/10

   No evidence in the pack describes API key authentication as an alternative to account login for Cursor; docs reference OAuth-based MCP authentication and account-based login flows only.

   ⚑ flag

   Gemini CLI~partialclaimed4/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Gemini CLI
   Cursor—none0/10

   The evidence pack shows Cursor has enterprise admin controls for MCP servers but contains no evidence of SSO/SAML integration, enterprise identity provider authentication (e.g., Okta, Azure AD, Google Workspace), or cloud platform login for compliance purposes. This is a fair and applicable axis for a widely-adopted dev tool sold to enterprises, so absence of evidence yields 'none' rather than 'na'.

   • [claimed-docs] “Enterprise admins can control which MCP servers users may run from the Cursor dashboard.”

   proof ↗⚑ flag

   Gemini CLI!disputedcontradicted4/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Gemini CLI
   Cursor—none0/10

   The evidence pack describes Cursor's agent features, MCP integrations, and installation steps, but contains no documentation or confirmation that users authenticate with an existing subscription plan to access the coding agent (only tangential community chatter about login policy hallucinations). Missing for 10: explicit account/subscription sign-in flow docs, plan-tier access confirmation, and any first-party statement linking subscription plan to agent usage.

   • [community] “Cursor's AI support agent hallucinated a single-device login policy, telling a user this was intentional. A Cursor developer later clarified…”

   proof ↗⚑ flag

   Gemini CLI!disputedcontradicted4/10

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

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

   proof ↗⚑ flag

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

   weight 1 · round to Gemini CLI
   Cursor—none0/10

   The evidence pack contains no documentation or first-party description of a sign-in flow that grants free-tier access without requiring API keys; only tangential community mentions of account workarounds for usage limits exist. Missing for 10: any docs on account creation/sign-in, free-tier terms, or explicit no-API-key requirement.

   • [community] “Cursor is caught in a cat-and-mouse game against workarounds where users create new accounts to get unlimited use; a repo enabling this (cur…”

   proof ↗⚑ flag

   Gemini CLI✓fullcommunity7/10

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

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

   proof ↗⚑ flag

Model choice

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

   weight 1 · round drawn
   Cursor—none0/10

   The evidence shows Cursor lets developers manually choose among multiple models (OpenAI, Anthropic, Gemini, etc.) but nothing indicates an automatic 'best model for the task' selection feature. missing for 10: any documentation or claim of an auto-select/router feature that picks models per task, evidence of cost/performance-based automatic routing.

   • [claimed-docs] “Choose between every cutting-edge model from OpenAI, Anthropic, Gemini, SpaceXAI, and Cursor.”

   proof ↗⚑ flag

   Gemini CLI—none0/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Cursor
   Cursor✓fullclaimed8/10

   cursor-docs-7 confirms Cursor lets developers choose between models from multiple providers (OpenAI, Anthropic, Gemini, and Cursor's own), directly matching the story. Missing for 10: independent hands-on verification of per-session model switching UI/behavior and pricing implications tied to model choice.

   • [claimed-docs] “Choose between every cutting-edge model from OpenAI, Anthropic, Gemini, SpaceXAI, and Cursor.”

   proof ↗⚑ flag

   Gemini CLI—none0/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Cursor—none0/10

   No evidence in the pack mentions data residency, region selection, or storage location controls for Cursor; the docs snippets cover agents, MCP, and integrations but nothing about choosing data storage region. Missing for 10: any mention of regional data residency options, enterprise data location controls, or compliance documentation addressing storage jurisdiction.

   ⚑ flag

   Gemini CLI—none0/10

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

   ⚑ flag

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

   weight 3 · round drawn
   Cursor—none0/10

   The evidence pack contains no documentation of a privacy mode, opt-out of training, or data-retention controls for Cursor; all cited docs cover unrelated features (agents, MCP, integrations) and community threads are unrelated to training-data privacy.

   ⚑ flag

   Gemini CLI—none0/10

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

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Cursor—none0/10

   The evidence pack contains no documentation of data retention settings, deletion controls, privacy dashboard, or data handling policies for Cursor; only unrelated docs on features (MCP, agents, integrations) and community complaints about bugs/pricing are present. Missing for 10: any first-party privacy policy docs, retention period settings, data deletion request mechanism, or enterprise data controls.

   ⚑ flag

   Gemini CLI—none0/10

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

   ⚑ flag

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

   weight 2 · round drawn
   Cursor—none0/10

   The evidence pack contains no mention of telemetry settings, privacy controls, or usage-tracking opt-out mechanisms; docs only cover unrelated features like MCP, agents, and integrations. Missing for 10: any privacy policy or settings documentation, telemetry opt-out toggle, or usage data collection disclosure.

   ⚑ flag

   Gemini CLI—none0/10

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

   ⚑ flag

Data governance

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

   weight 1 · round drawn
   Cursor—none0/10

   The evidence pack contains no mention of privacy settings, opt-out of training, or data usage policies for Cursor; all docs entries relate to unrelated features (agents, MCP, integrations) and community items focus on bugs/pricing/model sourcing, not training data controls.

   ⚑ flag

   Gemini CLI—none0/10

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

   ⚑ flag

Pr review

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

   weight 3 · round drawn
   Cursor~partialclaimed4/10

   Docs show GitHub/GitLab integration and agents that build/test/demo work end-to-end for review (cursor-docs-6, cursor-docs-10, cursor-docs-12), implying some git-workflow automation, but there's no explicit documentation of the agent staging changes, writing commit messages, creating branches, or opening pull requests. missing for 10: explicit commit-message generation, branch creation, PR-opening workflow documentation, and any hands-on confirmation these steps work end-to-end.

   • [claimed-docs] “Work with GitHub, GitLab, Azure DevOps, Bitbucket, JetBrains, Slack, Linear, and more”
   • [claimed-docs] “Cursor runs in your terminal, collaborates in Slack, and reviews PRs in GitHub.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”
   • [claimed-docs] “Inspect diffs, run checks, and catch problems before you merge”

   proof ↗⚑ flag

   Gemini CLI~partialclaimed4/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Gemini CLI
   Cursor✓fullclaimed7/10

   Cursor's docs explicitly claim it 'reviews PRs in GitHub' and can 'inspect diffs, run checks, and catch problems before you merge,' directly matching automated PR review with contextual feedback, backed by GitHub/GitLab/Bitbucket integration claims. missing for 10: independent/hands-on verification of review quality, details on triggering on every PR automatically, and no community corroboration of this specific feature.

   • [claimed-docs] “Cursor runs in your terminal, collaborates in Slack, and reviews PRs in GitHub.”
   • [claimed-docs] “Inspect diffs, run checks, and catch problems before you merge”
   • [claimed-docs] “Work with GitHub, GitLab, Azure DevOps, Bitbucket, JetBrains, Slack, Linear, and more”

   proof ↗⚑ flag

   Gemini CLI✓fullcommunity8/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Gemini CLI
   Cursor~partialclaimed5/10

   cursor-docs-4 explicitly claims the capability ('Inspect diffs, run checks, and catch problems before you merge') and cursor-docs-10/12 support a broader PR review workflow, but there is no independent or hands-on corroboration of diff inspection or check-running in practice, and community evidence focuses on unrelated bugs/pricing rather than this feature. missing for 10: independent verification of diff review UI, details on what 'checks' run (tests/linters/CI), and hands-on confirmation of pre-merge workflow.

   • [claimed-docs] “Inspect diffs, run checks, and catch problems before you merge”
   • [claimed-docs] “Cursor runs in your terminal, collaborates in Slack, and reviews PRs in GitHub.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Gemini CLI~partialcommunity6/10

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

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

   proof ↗⚑ flag

Safe execution

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

   weight 2 · round to Cursor
   Cursor✓fullclaimed8/10

   Docs show enterprise admins can restrict which MCP servers users may run from the Cursor dashboard, and users can toggle individual servers on/off, giving engineering leads direct control over external tool/integration access. Missing for 10: independent/hands-on corroboration of the admin dashboard controls and finer-grained per-tool permission examples beyond MCP servers.

   • [claimed-docs] “Enterprise admins can control which MCP servers users may run from the Cursor dashboard.”
   • [claimed-docs] “Toggle servers on/off without removing them”
   • [claimed-docs] “Model Context Protocol (MCP) enables Cursor to connect to external tools and data sources.”
   • [claimed-docs] “Configure custom MCP servers with a JSON file”

   proof ↗⚑ flag

   Gemini CLI~partialcommunity5/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Cursor—none0/10

   The evidence pack contains no mention of sandboxing, isolated execution environments, or network/tool restriction controls for the agent; docs describe agents using 'their own computers' but give no detail on containment/sandboxing mechanisms. Missing for 10: any documentation of a sandbox/isolation feature, network egress controls, or filesystem restriction for agent actions.

   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Gemini CLI—none0/10

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

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

   proof ↗⚑ flag

Security checks

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

   weight 1 · round drawn
   Cursor—none0/10

   No evidence anywhere in the pack mentions license detection, public code matching, provenance references, or IP attribution for AI-suggested code; docs focus on repo navigation, diffs, agents, and integrations, none of which addresses license/code-match transparency.

   ⚑ flag

   Gemini CLI—none0/10

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

   ⚑ flag

2. developerGet contextual explanations and automatic fixes for security vulnerabilities

   weight 2 · round to Gemini CLI
   Cursor—none0/10

   The evidence pack shows general code review/diff-inspection features (cursor-docs-4) and broad agent capabilities, but nothing specifically documents contextual security vulnerability explanations or automated security fixes. Missing for 10: any mention of vulnerability detection, security scanning integration, or CVE/security-specific fix suggestions.

   ⚑ flag

   Gemini CLI~partialclaimed4/10

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

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

   proof ↗⚑ flag