Claude Code vs Cursor

Agent access

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

   weight 2 · round to Claude Code
   Claude Code~partialprobed5/10

   Claude Code itself ships llms.txt files (docs.claude.com/llms.txt, code.claude.com/docs/llms.txt) confirming it is agent-oriented-docs-aware for its own product, and its agentic search/MCP tooling means it can fetch and consume arbitrary web docs including llms.txt if pointed at them via URL fetch or MCP. However, there is no explicit documented feature or first-party guidance describing 'point Claude Code at llms.txt of a third-party site' as a supported workflow. missing for 10: explicit product feature/docs describing consuming arbitrary llms.txt/agent-oriented docs as a first-class capability, independent hands-on confirmation of this specific use case.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.claude.com/llms.txt # Anthropic Developer Documentation This file provides an overview of the Anth…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.claude.com/en/docs/claude-code/overview.md > ## Documentation Index > Fetch the complete documentati…”
   • [claimed-docs] “Claude Code maps and explains entire codebases in a few seconds. It uses agentic search to understand project structure and dependencies wit…”
   • [claimed-docs] “Claude Code can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Claude Code
   Claude Code✓fullclaimed9/10

   Docs explicitly describe running Claude Code in CI (GitHub Actions/GitLab CI/CD) for automated code review and issue triage, piping logs into it, and scheduled/headless runs for repeated automation tasks, plus GitHub Action integration for automatic PR review. This directly matches the headless/CI automation story with strong first-party documentation. Missing for 10: independent/hands-on confirmation of a working CI pipeline (community evidence is silent on CI usage specifically).

   • [claimed-docs] “Claude Code is composable and follows the Unix philosophy. Pipe logs into it, run it in CI, or chain it with other tools”
   • [claimed-docs] “Run Claude on a schedule to automate work that repeats: morning PR reviews, overnight CI failure analysis, weekly dependency audits, or sync…”
   • [claimed-docs] “In CI, you can automate code review and issue triage with GitHub Actions or GitLab CI/CD.”
   • [claimed-docs] “Get automatic code review on every PR | GitHub Code Review”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Claude Code
   Claude Code✓fullclaimed9/10

   Claude Code has extensive first-party MCP documentation showing users can add MCP servers (e.g. `claude mcp add --transport http notion ...`), supporting stdio/HTTP transports, connecting to hundreds of external tools like Jira, Slack, Google Drive, Postgres, and even scaffolding new servers via a dev plugin. This is well corroborated across multiple doc pages with concrete CLI examples and use cases. Missing for 10: independent/hands-on community confirmation specifically of MCP tool usage (community evidence covers other topics, not MCP plugging in).

   • [claimed-docs] “With MCP, Claude Code can read your design docs in Google Drive, update tickets in Jira, pull data from Slack, or use your own custom toolin…”
   • [claimed-docs] “Claude Code can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”
   • [claimed-docs] “Implement features from issue trackers: "Add the feature described in JIRA issue ENG-4521 and create a PR on GitHub."”
   • [claimed-docs] “claude mcp add --transport http notion https://mcp.notion.com/mcp”
   • [claimed-docs] “Stdio servers run as local processes on your machine. They're ideal for tools that need direct system access or custom scripts.”
   • [claimed-docs] “You can also have Claude scaffold a server for you with the official mcp-server-dev plugin”
   • [claimed-docs] “an MCP server can also act as a channel that pushes messages into your session, so Claude reacts to Telegram messages, Discord chats, or web…”

   proof ↗⚑ flag

   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

4. ai-native userUse an official CLI

   weight 2 · round to Claude Code
   Claude Code✓fullprobed9/10

   Claude Code is itself an official CLI tool with documented install (curl install script), usage (`cd project && claude`), cross-platform support (macOS/Linux/Windows), and deep terminal-native workflows (git, MCP, hooks, CI). GitHub repo and docs confirm first-party CLI status with active community usage corroborating real-world use. Missing for 10: independent benchmarking of CLI robustness/UX beyond mixed community sentiment.

   • [claimed-docs] “cd your-project claude”
   • [claimed-docs] “curl -fsSL https://claude.ai/install.sh | bash”
   • [claimed-docs] “Available for macOS, Linux, and Windows.”
   • [github] “Use it in your terminal, IDE, or tag @claude on Github.”
   • [github] “helps you code faster by executing routine tasks, explaining complex code, and handling git workflows -- all through natural language comman…”
   • [probe] “official CLI documented at https://code.claude.com/docs/en/setup”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Claude Code
   Claude Code✓fullclaimed8/10

   Claude Code exposes multiple documented programmatic surfaces: the Agent SDK for building custom agents with full control over orchestration/tools/permissions, a CLI (claude, claude mcp serve) that can be scripted/piped/run in CI, and ANTHROPIC_API_KEY-based direct API access, all documented in first-party docs. This goes beyond a closed UI and gives AI-native users documented, programmatic control paths. Missing for 10: independent/hands-on validation of the Agent SDK's API surface and no explicit REST/OpenAPI reference beyond the SDK and CLI docs.

   • [claimed-docs] “the Agent SDK lets you build your own agents powered by Claude Code's tools and capabilities, with full control over orchestration, tool acc…”
   • [claimed-docs] “Use Claude Code as an MCP server. You can use Claude Code itself as an MCP server that other applications can connect to: claude mcp serve (…”
   • [claimed-docs] “If you've set the ANTHROPIC_API_KEY environment variable, Claude Code skips the login prompt and asks you to approve the key instead.”
   • [claimed-docs] “ANTHROPIC_API_KEY environment variable. Sent as the X-Api-Key header. Use this for direct Anthropic API access with a key from the Claude Co…”
   • [claimed-docs] “Claude Code is composable and follows the Unix philosophy. Pipe logs into it, run it in CI, or chain it with other tools”
   • [claimed-docs] “Claude Code can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Claude Code
   Claude Code~partialclaimed4/10

   Enterprise IAM docs mention role-based permissions, managed policy settings, and SSO/domain capture for org-wide configurations, plus sandboxing controls that restrict file/network access at runtime, suggesting some least-privilege controls exist. However, there is no explicit documentation of issuing scoped or limited-permission API keys/credentials specifically for an agent's use. Missing for 10: explicit scoped API key creation/management flow, granular credential scoping documentation, and independent verification of least-privilege credential issuance.

   • [claimed-docs] “Claude for Enterprise: adds SSO, domain capture, role-based permissions, compliance API, and managed policy settings for organization-wide C…”
   • [claimed-docs] “Single sign-on (SSO/SAML) and domain capture”
   • [claimed-docs] “Learn how Claude Code's sandboxed Bash tool provides filesystem and network isolation for safer, more autonomous agent execution. The Bash s…”
   • [claimed-docs] “If you've set the ANTHROPIC_API_KEY environment variable, Claude Code skips the login prompt and asks you to approve the key instead.”
   • [claimed-docs] “You can sign in to your Console account without creating an API key, even when your organization doesn't let developers create them.”

   proof ↗⚑ flag

   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

7. ai-native userBuild against official SDKs

   weight 2 · round to Claude Code
   Claude Code✓fullclaimed8/10

   Claude Code offers the official Agent SDK, letting developers build their own agents with full control over orchestration, tool access, and permissions, on top of Claude Code's tools/capabilities — a direct SDK for AI-native builders. This is backed by first-party docs and complemented by API-key-based programmatic access (ANTHROPIC_API_KEY) for direct integration. Missing for 10: independent/hands-on developer reports building production apps with the Agent SDK, and deeper docs on SDK language coverage/versioning.

   • [claimed-docs] “the Agent SDK lets you build your own agents powered by Claude Code's tools and capabilities, with full control over orchestration, tool acc…”
   • [claimed-docs] “If you've set the ANTHROPIC_API_KEY environment variable, Claude Code skips the login prompt and asks you to approve the key instead.”
   • [claimed-docs] “ANTHROPIC_API_KEY environment variable. Sent as the X-Api-Key header. Use this for direct Anthropic API access with a key from the Claude Co…”

   proof ↗⚑ flag

   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

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to Claude Code
   Claude Code~partialclaimed4/10

   Claude Code doesn't offer a first-party webhook subscription feature, but docs note that an MCP server can act as a channel pushing events—including webhook events—into a Claude Code session while the user is away, enabling indirect event subscription via custom MCP tooling. Missing for 10: a native/first-party webhook subscription mechanism, official documentation or example of setting up webhook-triggered sessions, and independent confirmation this works in practice.

   • [claimed-docs] “an MCP server can also act as a channel that pushes messages into your session, so Claude reacts to Telegram messages, Discord chats, or web…”
   • [claimed-docs] “an MCP server can also act as a channel that pushes messages into your session, so Claude reacts to Telegram messages, Discord chats, or web…”
   • [claimed-docs] “Claude Code can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”

   proof ↗⚑ flag

   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

Agentic features

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

   weight 2 · round drawn
   Claude Code✓fullclaimed7/10

   Claude Code generates AI-driven insights and suggestions from a user's data: it maps/explains entire codebases automatically, reviews code and PRs for security issues with explanations, and via MCP can query databases (e.g., PostgreSQL) or pull data from Slack/Jira/Google Drive to answer questions and suggest actions. This is all documented first-party capability with concrete examples (codebase mapping, automatic PR/security review, data queries via MCP). missing for 10: independent/hands-on corroboration specifically validating the quality of data-driven insights (community evidence is mostly about coding reliability, not insight generation), and no dedicated analytics/dashboard-style insight feature beyond code/data-source querying.

   • [claimed-docs] “Claude Code maps and explains entire codebases in a few seconds. It uses agentic search to understand project structure and dependencies wit…”
   • [claimed-docs] “Claude helps security teams and developers by reviewing code for security issues, drafts patches, and explains the risk in language your who…”
   • [claimed-docs] “Get automatic code review on every PR | GitHub Code Review”
   • [claimed-docs] “Find emails of 10 random users who used feature ENG-4521, based on our PostgreSQL database.”
   • [claimed-docs] “With MCP, Claude Code can read your design docs in Google Drive, update tickets in Jira, pull data from Slack, or use your own custom toolin…”
   • [claimed-docs] “Claude Code can read your design docs in Google Drive, update tickets in Jira, pull data from Slack, or use your own custom tooling.”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Claude Code✓fullclaimed8/10

   Docs describe explicit background-automation features: scheduled runs for recurring tasks (morning PR reviews, overnight CI analysis, weekly audits), cloud/web sessions for long-running tasks you check back on, GitHub Actions/GitLab CI integration for automated review/triage, and MCP servers that push events (Telegram/Discord/webhooks) into a session while the user is away. Missing for 10: independent/hands-on corroboration that scheduled or background jobs run reliably unattended over time (only first-party docs cited).

   • [claimed-docs] “Run Claude on a schedule to automate work that repeats: morning PR reviews, overnight CI failure analysis, weekly dependency audits, or sync…”
   • [claimed-docs] “Step away from your desk and keep working from your phone or any browser with Remote Control”
   • [claimed-docs] “Kick off a long-running task on the web or the Claude mobile app, then pull it into your terminal with `claude --teleport`.”
   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”
   • [claimed-docs] “Kick off long-running tasks and check back when they're done, work on repos you don't have locally, or run multiple tasks in parallel.”
   • [claimed-docs] “Run Claude Code in your browser with no local setup. Kick off long-running tasks and check back when they're done, work on repos you don't h…”
   • [claimed-docs] “In CI, you can automate code review and issue triage with GitHub Actions or GitLab CI/CD.”
   • [claimed-docs] “an MCP server can also act as a channel that pushes messages into your session, so Claude reacts to Telegram messages, Discord chats, or web…”
   • [claimed-docs] “an MCP server can also act as a channel that pushes messages into your session, so Claude reacts to Telegram messages, Discord chats, or web…”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Cursor
   Claude Code✓fullcommunity8/10

   Claude Code's entire premise is delegating tasks to a built-in AI agent: docs describe it planning approaches, writing code across files, running tests, handling git workflows, and autonomously completing multi-step tasks (docs-2, docs-3, docs-20, docs-28, gh-3). This is corroborated by extensive first-party documentation and some community confirmation that it performs well as a coding assistant, though other community reports describe reliability issues and failure modes in autonomous execution. Missing for 10: independent benchmark-level validation of consistent task delegation success and stronger consensus on reliability (community reports show notable failure cases).

   • [claimed-docs] “Describe what you want in plain language. Claude Code plans the approach, writes the code across multiple files, and verifies it works.”
   • [claimed-docs] “Claude Code works directly with git. It stages changes, writes commit messages, creates branches, and opens pull requests.”
   • [claimed-docs] “Claude Code handles the tedious tasks that eat up your day: writing tests for untested code, fixing lint errors across a project, resolving …”
   • [claimed-docs] “Claude Code plans the approach, writes the code across multiple files, and verifies it works.”
   • [github] “helps you code faster by executing routine tasks, explaining complex code, and handling git workflows -- all through natural language comman…”
   • [community] “Claude is significantly better than other models at code assistant tasks, or at least in the way I use it.”
   • [community] “I've been using Claude Code daily for months on a project with Elixir, Rust, and Python. The worst failure mode is when it does a replace_al…”
   • [community] “I've tried to use Claude code for a month now. It has a 100% failure rate so far. Comparing that to creating a project and just chatting wit…”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Claude Code✓fullclaimed8/10

   Claude Code is explicitly designed to be operated via plain-language instructions—describing tasks, git workflows, MCP tool use, and even natural-language chat commands (@claude in Slack, GitHub) all documented as core interaction modes, and GitHub docs explicitly state it works 'all through natural language commands.' missing for 10: independent hands-on benchmarking specifically confirming natural-language command comprehension breadth/accuracy versus slash-command or scripted usage, and some community reports note failure modes/hallucination under natural language instructions reducing reliability.

   • [claimed-docs] “Describe what you want in plain language. Claude Code plans the approach, writes the code across multiple files, and verifies it works.”
   • [claimed-docs] “Claude Code plans the approach, writes the code across multiple files, and verifies it works.”
   • [claimed-docs] “Claude Code works directly with git. It stages changes, writes commit messages, creates branches, and opens pull requests.”
   • [github] “helps you code faster by executing routine tasks, explaining complex code, and handling git workflows -- all through natural language comman…”
   • [claimed-docs] “Route tasks from team chat: mention @Claude in Slack with a bug report and get a pull request back”
   • [claimed-docs] “cd your-project claude”

   proof ↗⚑ flag

   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

Api quality

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

   weight 2 · round drawn
   Claude Code—none0/10

   The evidence pack shows standard documentation pages and an Agent SDK reference, but nothing describing an interactive API reference with runnable/executable code examples (e.g., an in-browser sandbox or live API explorer). No such capability is evidenced anywhere in the docs, GitHub, or community items.

   ⚑ flag

   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

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

   weight 2 · round drawn
   Claude Code—none0/10

   The evidence pack shows Claude Code as a CLI/agent tool with SDK, MCP, and CI integrations, but no mention of a downloadable OpenAPI or equivalent machine-readable API spec for Claude Code itself. This axis is plausible for a product with an Agent SDK and API-key based access, but the pack contains no such artifact.

   ⚑ flag

   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

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

   weight 2 · round drawn
   Claude Code—none0/10

   No evidence pack items mention API versioning schemes, version numbers, or a documented deprecation policy for Claude Code's APIs/CLI/SDK; the pack covers features, integrations, and community sentiment but nothing about API stability or deprecation commitments.

   ⚑ flag

   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

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

   weight 2 · round to Cursor
   Claude Code!disputedcontradicted6/10

   Claude Code's docs explicitly support bulk operations — fixing lint errors 'across a project', multi-file writes, spawning multiple agents to work on different parts of a task simultaneously, and running multiple sessions/tasks in parallel or on a schedule — which strongly matches the story. However, a hands-on community report describes a concrete failure mode during a bulk-style replace_all operation that corrupted code (turning a constant into 'GROQ_URL = GROQ_URL'), with the user stating you 'absolutely can't trust it to self-verify' on such operations, directly contradicting reliable execution of bulk changes at scale. Missing for 10: independent corroboration that large-scale bulk operations complete reliably without manual review, and resolution/acknowledgment of the reported failure mode.

   • [claimed-docs] “writing tests for untested code, fixing lint errors across a project, resolving merge conflicts, updating dependencies, and writing release …”
   • [claimed-docs] “Spawn multiple Claude Code agents that work on different parts of a task simultaneously. A lead agent coordinates the work, assigns subtasks…”
   • [claimed-docs] “Claude Code handles the tedious tasks that eat up your day: writing tests for untested code, fixing lint errors across a project, resolving …”
   • [claimed-docs] “Spawn multiple Claude Code agents that work on different parts of a task simultaneously.”
   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”
   • [claimed-docs] “Kick off long-running tasks and check back when they're done, work on repos you don't have locally, or run multiple tasks in parallel.”
   • [community] “I've been using Claude Code daily for months on a project with Elixir, Rust, and Python. The worst failure mode is when it does a replace_al…”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Claude Code~partialclaimed6/10

   Claude Code supports Hooks (shell commands triggered before/after actions like auto-formatting or lint on edits) and scheduled runs plus MCP channels (Telegram/Discord/webhook events) that push messages into a session automatically, which together constitute event-triggered automation rules. However, there's no unified declarative 'rules engine' with conditions/triggers documented — it's a patchwork of hooks, cron-like scheduling, and MCP event channels rather than a first-class rule-definition system. missing for 10: a unified rules/trigger definition UI or config, broader event types beyond hooks/schedule/MCP channels, and independent/hands-on validation of these automation triggers working reliably.

   • [claimed-docs] “Hooks let you run shell commands before or after Claude Code actions, like auto-formatting after every file edit or running lint before a co…”
   • [claimed-docs] “Run Claude on a schedule to automate work that repeats: morning PR reviews, overnight CI failure analysis, weekly dependency audits, or sync…”
   • [claimed-docs] “an MCP server can also act as a channel that pushes messages into your session, so Claude reacts to Telegram messages, Discord chats, or web…”
   • [claimed-docs] “an MCP server can also act as a channel that pushes messages into your session, so Claude reacts to Telegram messages, Discord chats, or web…”
   • [claimed-docs] “In CI, you can automate code review and issue triage with GitHub Actions or GitLab CI/CD.”

   proof ↗⚑ flag

   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

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Claude Code✓fullclaimed7/10

   Docs explicitly describe running Claude Code on a schedule for recurring automation (PR reviews, CI failure analysis, dependency audits, doc syncing) and mention 'schedule recurring tasks' as a feature. Missing for 10: independent/hands-on confirmation of the scheduling mechanism and details on configuration (cron syntax, triggers, reliability).

   • [claimed-docs] “Run Claude on a schedule to automate work that repeats: morning PR reviews, overnight CI failure analysis, weekly dependency audits, or sync…”
   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”

   proof ↗⚑ flag

   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

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

   weight 1 · round to Claude Code
   Claude Code~partialclaimed5/10

   Automations in Claude Code (CLAUDE.md, skills, hooks, slash commands) are plain files that live in the repo, so they inherit git's version history, and Claude Code natively works with git (staging, commits, diffs) and supports visual diff review (claude-code-docs-3, claude-code-docs-13, claude-code-docs-32, claude-code-docs-33, claude-code-docs-22). However, there is no dedicated feature for versioning/rolling back automations themselves (e.g., no automation-specific history log, no built-in 'revert this hook/skill run' or undo mechanism) — reviewers rely entirely on generic git workflows rather than a purpose-built automation-lifecycle tool. missing for 10: a dedicated automation versioning/audit history UI, an explicit rollback/undo command for skills or hooks, and independent hands-on confirmation that rollback of automations works as intended.

   • [claimed-docs] “Claude Code works directly with git. It stages changes, writes commit messages, creates branches, and opens pull requests.”
   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”
   • [claimed-docs] “Create skills to package repeatable workflows your team can share, like `/review-pr` or `/deploy-staging`.”
   • [claimed-docs] “Hooks let you run shell commands before or after Claude Code actions, like auto-formatting after every file edit or running lint before a co…”
   • [claimed-docs] “CLAUDE.md is a markdown file you add to your project root that Claude Code reads at the start of every session. Use it to set coding standar…”

   proof ↗⚑ flag

   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

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

   Docs show Claude Code can run as a cloud/browser session for long-running tasks (web, mobile, remote control, teleport), plan and write code across files, write tests, and open PRs with diff review for others to inspect — covering build, test, and reviewable-artifact steps end-to-end without local setup (claude-code-docs-9,10,13,14,26,28,3,12). However there's no explicit 'demo' feature (e.g., live preview/staging deploy) beyond PR/diff review, and independent hands-on reports raise reliability concerns about self-verification on complex tasks. Missing for 10: dedicated demo/preview-environment tooling, independent corroboration of full cloud build-test-PR pipelines succeeding end-to-end without human intervention.

   • [claimed-docs] “Step away from your desk and keep working from your phone or any browser with Remote Control”
   • [claimed-docs] “Kick off a long-running task on the web or the Claude mobile app, then pull it into your terminal with `claude --teleport`.”
   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”
   • [claimed-docs] “Kick off long-running tasks and check back when they're done, work on repos you don't have locally, or run multiple tasks in parallel.”
   • [claimed-docs] “Run Claude Code in your browser with no local setup. Kick off long-running tasks and check back when they're done, work on repos you don't h…”
   • [claimed-docs] “Claude Code plans the approach, writes the code across multiple files, and verifies it works.”
   • [claimed-docs] “Claude Code works directly with git. It stages changes, writes commit messages, creates branches, and opens pull requests.”
   • [claimed-docs] “Get automatic code review on every PR | GitHub Code Review”
   • [community] “I've been using Claude Code daily for months on a project with Elixir, Rust, and Python. The worst failure mode is when it does a replace_al…”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Cursor
   Claude Code✓fullclaimed7/10

   Docs describe running Claude Code in-browser with no local setup, kicking off long-running tasks and checking back later, working on repos not present locally, running multiple tasks in parallel, and remote control/teleport features to move sessions between web/mobile and terminal — matching the delegate-to-cloud story directly. Missing for 10: independent/hands-on confirmation of the cloud environment's isolation guarantees (the sandboxing docs cited relate to local Bash tool isolation, not the cloud session itself) and details on how isolated/secure the cloud runtime is.

   • [claimed-docs] “Step away from your desk and keep working from your phone or any browser with Remote Control”
   • [claimed-docs] “Kick off a long-running task on the web or the Claude mobile app, then pull it into your terminal with `claude --teleport`.”
   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”
   • [claimed-docs] “Kick off long-running tasks and check back when they're done, work on repos you don't have locally, or run multiple tasks in parallel.”
   • [claimed-docs] “Run Claude Code in your browser with no local setup. Kick off long-running tasks and check back when they're done, work on repos you don't h…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Cursor
   Claude Code~partialclaimed3/10

   Docs mention running Claude Code in the cloud/browser with no local setup and working on repos you don't have locally, implying some environment is provisioned, but there's no documentation of configuring a reproducible environment (e.g., setup scripts, dependency installation, devcontainer-style config) for cloud sessions. missing for 10: explicit environment/config file for cloud sandboxes, dependency installation steps, reproducibility guarantees across runs.

   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”
   • [claimed-docs] “Kick off long-running tasks and check back when they're done, work on repos you don't have locally, or run multiple tasks in parallel.”
   • [claimed-docs] “Run Claude Code in your browser with no local setup. Kick off long-running tasks and check back when they're done, work on repos you don't h…”

   proof ↗⚑ flag

   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

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

   Docs explicitly describe spawning multiple Claude Code agents with a lead agent coordinating subtasks, running multiple sessions/tasks in parallel in the cloud, scheduling recurring/long-running tasks, and remote/teleport control to check back later — directly matching the fleet/parallel/long-duration story. Missing for 10: independent hands-on verification of multi-day unattended fleet runs and clearer guarantees on stability over very long horizons (community reports note reliability/quality drift over extended sessions).

   • [claimed-docs] “Spawn multiple Claude Code agents that work on different parts of a task simultaneously. A lead agent coordinates the work, assigns subtasks…”
   • [claimed-docs] “Spawn multiple Claude Code agents that work on different parts of a task simultaneously.”
   • [claimed-docs] “Spawn multiple Claude Code agents that work on different parts of a task simultaneously. A lead agent coordin”
   • [claimed-docs] “Run Claude on a schedule to automate work that repeats: morning PR reviews, overnight CI failure analysis, weekly dependency audits, or sync…”
   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”
   • [claimed-docs] “Kick off long-running tasks and check back when they're done, work on repos you don't have locally, or run multiple tasks in parallel.”
   • [claimed-docs] “Run Claude Code in your browser with no local setup. Kick off long-running tasks and check back when they're done, work on repos you don't h…”
   • [claimed-docs] “Step away from your desk and keep working from your phone or any browser with Remote Control”
   • [claimed-docs] “Kick off a long-running task on the web or the Claude mobile app, then pull it into your terminal with `claude --teleport`.”

   proof ↗⚑ flag

   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

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

   weight 1 · round drawn
   Claude Code~partialclaimed6/10

   Docs mention running 'multiple sessions side by side' and reviewing diffs visually in the web/cloud interface, plus running multiple tasks in parallel and spawning multiple agents—supporting parallel execution and comparison, though not explicitly framed as multiple attempts at the *same* task with a selection step. Missing for 10: explicit documentation of running several independent attempts at one identical task and a UI/workflow for choosing the best among them, and independent hands-on confirmation of this specific workflow.

   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”
   • [claimed-docs] “Kick off long-running tasks and check back when they're done, work on repos you don't have locally, or run multiple tasks in parallel.”
   • [claimed-docs] “Run Claude Code in your browser with no local setup. Kick off long-running tasks and check back when they're done, work on repos you don't h…”
   • [claimed-docs] “Spawn multiple Claude Code agents that work on different parts of a task simultaneously. A lead agent coordinates the work, assigns subtasks…”
   • [claimed-docs] “Spawn multiple Claude Code agents that work on different parts of a task simultaneously.”

   proof ↗⚑ flag

   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

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

   First-party docs show robust support for scheduled/triggered automation: 'Run Claude on a schedule' for recurring maintenance tasks (docs-8), 'schedule recurring tasks' in the web UI (docs-13), MCP servers that push Telegram/Discord/webhook events into a session 'while you're away' (docs-31/54), and Slack @mentions triggering PRs (docs-11), plus CI integration for automated review/triage (docs-36). However, community reports raise real concerns about autonomous reliability over sustained/unsupervised runs (e.g. degrading output quality, self-verification failures, 'can't trust it to self-verify' — comm-16, comm-17, comm-19, comm-20), which tempers confidence that always-on autonomous maintenance works robustly in practice. Missing for 10: independent/hands-on validation that scheduled/triggered agents reliably self-maintain software over time without human correction, and no explicit multi-day/continuous 'always-on' uptime evidence beyond scheduled/triggered runs.

   • [claimed-docs] “Run Claude on a schedule to automate work that repeats: morning PR reviews, overnight CI failure analysis, weekly dependency audits, or sync…”
   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”
   • [claimed-docs] “an MCP server can also act as a channel that pushes messages into your session, so Claude reacts to Telegram messages, Discord chats, or web…”
   • [claimed-docs] “an MCP server can also act as a channel that pushes messages into your session, so Claude reacts to Telegram messages, Discord chats, or web…”
   • [claimed-docs] “Route tasks from team chat: mention @Claude in Slack with a bug report and get a pull request back”
   • [claimed-docs] “In CI, you can automate code review and issue triage with GitHub Actions or GitLab CI/CD.”
   • [community] “I've been using Claude Code daily for months on a project with Elixir, Rust, and Python. The worst failure mode is when it does a replace_al…”
   • [community] “Whenever the phrase 'simplest fix' appears, it's time to pull the emergency break. This has gotten much worse over the past few weeks. It wi…”
   • [community] “I've tried to use Claude code for a month now. It has a 100% failure rate so far. Comparing that to creating a project and just chatting wit…”
   • [community] “A month ago the agents researched, designed, and implemented a compelling app idea with minimal guidance and felt super human. A month later…”

   proof ↗⚑ flag

   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

Code completion

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

   weight 3 · round drawn
   Claude Code—none0/10

   Claude Code's documented interaction model is conversational/agentic (terminal commands, plan-then-execute, PR generation) and its IDE extensions offer inline diffs and @-mentions, not ghost-text style inline completions or next-edit suggestions as the user types. No evidence pack item describes autocomplete-style inline suggestions.

   • [claimed-docs] “The VS Code extension provides inline diffs, @-mentions, plan review, and conversation history directly in your editor.”
   • [claimed-docs] “A plugin for IntelliJ IDEA, PyCharm, WebStorm, and other JetBrains IDEs with interactive diff viewing and selection context sharing.”

   proof ↗⚑ flag

   Cursor—none0/10

   The evidence pack contains no first-party documentation or hands-on account describing Cursor's own inline code completion or next-edit suggestion feature; only tangential community references compare competitors' tab-completion tools (e.g., Continue, SuperMaven) without confirming or detailing Cursor's implementation. Missing for 10: any first-party doc on Cursor's Tab/inline completion feature, hands-on confirmation it works as typed, and mention of 'next-edit' suggestion behavior.

   ⚑ flag

Debugging

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

   weight 1 · round to Claude Code
   Claude Code~partialclaimed6/10

   Docs explicitly list a Chrome integration for debugging live web applications, indicating Claude Code can connect to and debug a running app via browser tooling rather than just editing static code. However, evidence is thin — just a single doc title/link with no detail on setup, capabilities (e.g., breakpoints, console/network inspection), or hands-on/community verification of this workflow. missing for 10: detailed documentation of the Chrome debugging workflow, independent/hands-on confirmation it works on real live apps, coverage of non-Chrome runtime debugging scenarios.

   • [claimed-docs] “Debug live web applications | Chrome”
   • [claimed-docs] “Work with Claude directly in your codebase. Build, debug, and ship from your terminal, IDE, Slack, web, and more.”

   proof ↗⚑ flag

   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

2. developerDebug issues and troubleshoot using natural-language queries

   weight 2 · round to Claude Code
   Claude Code✓fullcommunity7/10

   Docs explicitly cover debugging: 'Debug live web applications' (Chrome integration), 'overnight CI failure analysis', explaining complex code, and codebase-wide understanding to trace issues via natural-language prompts. This is core positioning ('Build, debug, and ship from your terminal, IDE...'). missing for 10: independent hands-on validation specifically of debugging workflows (community evidence instead highlights reliability issues like self-verification failures and bugs introduced during edits, which are adjacent but not direct proof debugging-via-NL fails).

   • [claimed-docs] “Debug live web applications | Chrome”
   • [claimed-docs] “Run Claude on a schedule to automate work that repeats: morning PR reviews, overnight CI failure analysis, weekly dependency audits, or sync…”
   • [claimed-docs] “Work with Claude directly in your codebase. Build, debug, and ship from your terminal, IDE, Slack, web, and more.”
   • [claimed-docs] “It understands your entire codebase and can work across multiple files and tools to get things done.”
   • [github] “helps you code faster by executing routine tasks, explaining complex code, and handling git workflows -- all through natural language comman…”
   • [community] “I've been using Claude Code daily for months on a project with Elixir, Rust, and Python. The worst failure mode is when it does a replace_al…”

   proof ↗⚑ flag

   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

Feature implementation

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

   weight 3 · round to Claude Code
   Claude Code✓fullcommunity7/10

   Docs explicitly describe the full loop: reading tracked issues (Jira, GitHub, Slack) via MCP, generating code across multiple files, running tests, creating branches, and opening PRs — e.g. 'Add the feature described in JIRA issue ENG-4521 and create a PR on GitHub' and 'reading issues, writing code, running tests, and submitting PRs—all from your terminal.' Community reports corroborate real-world usage but also note reliability issues (self-verification failures, quality degradation over time), so results aren't guaranteed to be flawless end-to-end. Missing for 10: independent case studies quantifying success rate of full issue-to-PR automation, and detail on how failures/test verification are handled when the generated PR doesn't pass CI.

   • [claimed-docs] “Claude Code works directly with git. It stages changes, writes commit messages, creates branches, and opens pull requests.”
   • [claimed-docs] “Claude Code integrates with GitHub, GitLab, and your command line tools to handle the entire workflow—reading issues, writing code, running …”
   • [claimed-docs] “Implement features from issue trackers: "Add the feature described in JIRA issue ENG-4521 and create a PR on GitHub."”
   • [claimed-docs] “Add the feature described in JIRA issue ENG-4521 and create a PR on GitHub.”
   • [claimed-docs] “Route tasks from team chat: mention @Claude in Slack with a bug report and get a pull request back”
   • [community] “I've been using Claude Code daily for months on a project with Elixir, Rust, and Python. The worst failure mode is when it does a replace_al…”
   • [community] “I've tried to use Claude code for a month now. It has a 100% failure rate so far. Comparing that to creating a project and just chatting wit…”

   proof ↗⚑ flag

   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

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
   Claude Code!disputedcontradicted6/10

   Docs strongly claim the core capability: describe a feature/bug in plain language and Claude Code plans, implements, and verifies code changes across multiple files (claude-code-docs-2/28/51/20, claude-code-gh-3). However, hands-on community reports cite concrete failures undermining reliability of multi-file edits, e.g. a replace_all bug corrupting a constant (GROQ_URL=GROQ_URL) and inability to self-verify, plus a user reporting a '100% failure rate' and quality degradation over time (claude-code-comm-16, claude-code-comm-17, claude-code-comm-19, claude-code-comm-20), balanced against other users praising its code-assistant ability (claude-code-comm-5). missing for 10: consistent independent benchmarks confirming reliability across diverse multi-file tasks, resolution of reported failure modes.

   • [claimed-docs] “Describe what you want in plain language. Claude Code plans the approach, writes the code across multiple files, and verifies it works.”
   • [claimed-docs] “Claude Code plans the approach, writes the code across multiple files, and verifies it works.”
   • [claimed-docs] “It understands your entire codebase and can work across multiple files and tools to get things done.”
   • [claimed-docs] “Claude Code handles the tedious tasks that eat up your day: writing tests for untested code, fixing lint errors across a project, resolving …”
   • [github] “helps you code faster by executing routine tasks, explaining complex code, and handling git workflows -- all through natural language comman…”
   • [community] “I've been using Claude Code daily for months on a project with Elixir, Rust, and Python. The worst failure mode is when it does a replace_al…”
   • [community] “Whenever the phrase 'simplest fix' appears, it's time to pull the emergency break. This has gotten much worse over the past few weeks. It wi…”
   • [community] “I've tried to use Claude code for a month now. It has a 100% failure rate so far. Comparing that to creating a project and just chatting wit…”
   • [community] “A month ago the agents researched, designed, and implemented a compelling app idea with minimal guidance and felt super human. A month later…”
   • [community] “Claude is significantly better than other models at code assistant tasks, or at least in the way I use it.”

   proof ↗⚑ flag

   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

Maintenance automation

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

   weight 3 · round to Claude Code
   Claude Code✓fullcommunity8/10

   First-party docs explicitly list this exact story's capabilities verbatim ('writing tests for untested code, fixing lint errors across a project, resolving merge conflicts, updating dependencies') and Claude Code is broadly documented as an agentic coding assistant that edits files, runs commands, and manages projects end-to-end. Community feedback confirms general coding competence but also raises reliability concerns (e.g., self-verification failures) not specific to these four tasks. Missing for 10: independent hands-on verification specifically for lint-fixing, merge-conflict resolution, and dependency updates rather than general coding tasks.

   • [claimed-docs] “writing tests for untested code, fixing lint errors across a project, resolving merge conflicts, updating dependencies, and writing release …”
   • [claimed-docs] “Claude Code handles the tedious tasks that eat up your day: writing tests for untested code, fixing lint errors across a project, resolving …”
   • [claimed-docs] “Claude Code maps and explains entire codebases in a few seconds. It uses agentic search to understand project structure and dependencies wit…”
   • [claimed-docs] “Claude Code integrates with GitHub, GitLab, and your command line tools to handle the entire workflow—reading issues, writing code, running …”
   • [community] “Claude is significantly better than other models at code assistant tasks, or at least in the way I use it.”

   proof ↗⚑ flag

   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

Multimodal generation

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

   weight 2 · round drawn
   Claude Code—none0/10

   The evidence pack describes Claude Code's general coding, git, MCP, and automation capabilities but never mentions accepting a sketch, image, or PDF as design input to scaffold or generate an app. The closest reference (claude-code-docs-23) only describes updating an email template from Figma designs shared in Slack, not app generation from visual designs. Missing for 10: any documentation or example of image/PDF/sketch-to-code app generation, multimodal input support in the CLI, or a demonstrated workflow turning a design mockup into a working application.

   ⚑ flag

   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

Codebase mapping

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

   weight 3 · round to Claude Code
   Claude Code✓fullclaimed7/10

   Docs explicitly claim Claude Code 'maps and explains entire codebases in a few seconds' using agentic search to understand project structure and dependencies without manual context selection, and separately states it 'understands your entire codebase' across files; CLAUDE.md further lets teams encode architecture decisions for onboarding. Missing for 10: independent/hands-on corroboration specifically validating codebase-mapping accuracy, and no benchmark or case study showing it correctly locates the right starting point in a large real-world repo.

   • [claimed-docs] “Claude Code maps and explains entire codebases in a few seconds. It uses agentic search to understand project structure and dependencies wit…”
   • [claimed-docs] “It understands your entire codebase and can work across multiple files and tools to get things done.”
   • [claimed-docs] “CLAUDE.md is a markdown file you add to your project root that Claude Code reads at the start of every session.”
   • [claimed-docs] “CLAUDE.md is a markdown file you add to your project root that Claude Code reads at the start of every session. Use it to set coding standar…”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Claude Code
   Claude Code✓fullclaimed7/10

   Claude Code's own product page explicitly states it 'maps and explains entire codebases in a few seconds' using 'agentic search to understand project structure and dependencies without you having to manually select context files,' directly matching the story, and other docs reinforce that it 'understands your entire codebase' across multiple files. Missing for 10: independent/hands-on evidence specifically corroborating the automatic codebase-mapping claim (community evidence covers general coding quality/trust issues but not this specific feature).

   • [claimed-docs] “Claude Code maps and explains entire codebases in a few seconds. It uses agentic search to understand project structure and dependencies wit…”
   • [claimed-docs] “It understands your entire codebase and can work across multiple files and tools to get things done.”
   • [claimed-docs] “CLAUDE.md is a markdown file you add to your project root that Claude Code reads at the start of every session.”

   proof ↗⚑ flag

   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

Context management

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

   weight 2 · round to Claude Code
   Claude Code~partialclaimed4/10

   Claude Code supports persistent project context via CLAUDE.md, which it reads at the start of every session, giving some continuity of 'memory' across sessions, and the VS Code extension keeps conversation history in-editor. However, this is a manually authored/maintained file, not an automatically built or recalled memory system that captures learnings from prior sessions without user intervention. Missing for 10: evidence of automatic memory formation/summarization from past sessions, automatic recall of prior task context without a manually maintained file, and any documentation of a persistent 'agent memory' feature beyond CLAUDE.md.

   • [claimed-docs] “CLAUDE.md is a markdown file you add to your project root that Claude Code reads at the start of every session.”
   • [claimed-docs] “CLAUDE.md is a markdown file you add to your project root that Claude Code reads at the start of every session. Use it to set coding standar…”
   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Claude Code—none0/10

   The evidence pack describes Claude Code understanding a single project's entire codebase and working across multiple files within it, but there is no mention of including multiple separate project directories in one session (e.g., an --add-dir style flag or multi-root workspace support).

   ⚑ flag

   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

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

   weight 3 · round to Claude Code
   Claude Code✓fullcommunity9/10

   First-party docs explicitly describe CLAUDE.md as a project-root markdown file read at every session start, used to set coding standards, architecture decisions, preferred libraries, and review checklists (claude-code-docs-5, claude-code-docs-22). Community evidence (claude-code-comm-15) independently confirms real-world use of CLAUDE.md files for guiding the agent, corroborating the feature exists and is actively used. Missing for 10: broader independent/hands-on documentation of best practices or examples beyond a single community mention.

   • [claimed-docs] “CLAUDE.md is a markdown file you add to your project root that Claude Code reads at the start of every session.”
   • [claimed-docs] “CLAUDE.md is a markdown file you add to your project root that Claude Code reads at the start of every session. Use it to set coding standar…”
   • [community] “I've found that I have to add more and more CLAUDE.md guide rails, and my CLAUDE.md files have been exploding since around mid-March... I've…”

   proof ↗⚑ flag

   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

Issue diagnosis

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

   weight 3 · round to Cursor
   Claude Code!disputedcontradicted5/10

   Docs claim Claude Code can debug live apps, plan fixes, and 'verifies it works' across multi-file changes (claude-code-docs-2/17/28/51), supporting reproduce/root-cause/verify workflows, but hands-on community reports give a concrete counter-example where self-verification failed (a replace_all bug silently corrupted a constant, 'You absolutely can't trust it to self-verify') and describe recurring low-quality 'simplest fix' patches that break things (claude-code-comm-16, claude-code-comm-17). missing for 10: independent benchmark/case study specifically on bug reproduction and root-cause isolation, and resolution of the self-verification reliability concerns raised by users.

   • [claimed-docs] “Describe what you want in plain language. Claude Code plans the approach, writes the code across multiple files, and verifies it works.”
   • [claimed-docs] “Debug live web applications | Chrome”
   • [claimed-docs] “Claude Code plans the approach, writes the code across multiple files, and verifies it works.”
   • [claimed-docs] “It understands your entire codebase and can work across multiple files and tools to get things done.”
   • [community] “I've been using Claude Code daily for months on a project with Elixir, Rust, and Python. The worst failure mode is when it does a replace_al…”
   • [community] “Whenever the phrase 'simplest fix' appears, it's time to pull the emergency break. This has gotten much worse over the past few weeks. It wi…”

   proof ↗⚑ flag

   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

Marketplace

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

   weight 1 · round to Claude Code
   Claude Code✓fullclaimed8/10

   Claude Code explicitly supports custom Skills ('Create skills to package repeatable workflows your team can share, like /review-pr or /deploy-staging') plus a scaffolding plugin (mcp-server-dev) for building custom tool integrations, giving developers a documented mechanism to equip the agent with specialized, shareable capabilities. Missing for 10: independent hands-on validation of the skills system's reliability/quality beyond first-party docs.

   • [claimed-docs] “Create skills to package repeatable workflows your team can share, like `/review-pr` or `/deploy-staging`.”
   • [claimed-docs] “You can also have Claude scaffold a server for you with the official mcp-server-dev plugin”
   • [claimed-docs] “Claude Code can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”

   proof ↗⚑ flag

   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

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

   weight 1 · round to Cursor
   Claude Code~partialclaimed6/10

   Claude Code supports MCP integration with third-party tools/servers (Notion, Jira, Slack, Google Drive, custom servers) and can be extended via the Agent SDK, plugins, and Slack/GitHub integrations, enabling integration of partner-built apps into workflows. However, there's no explicit evidence of a curated marketplace or formal partner-app ecosystem comparable to a dedicated app store, and integration relies mainly on generic MCP connectors rather than pre-built 'partner agent apps.' Missing for 10: a documented partner/marketplace program for third-party agent apps, independent verification of partner integrations working reliably, and case studies of engineering teams integrating named partner-built agents.

   • [claimed-docs] “With MCP, Claude Code can read your design docs in Google Drive, update tickets in Jira, pull data from Slack, or use your own custom toolin…”
   • [claimed-docs] “Claude Code can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”
   • [claimed-docs] “claude mcp add --transport http notion https://mcp.notion.com/mcp”
   • [claimed-docs] “You can also have Claude scaffold a server for you with the official mcp-server-dev plugin”
   • [claimed-docs] “the Agent SDK lets you build your own agents powered by Claude Code's tools and capabilities, with full control over orchestration, tool acc…”
   • [claimed-docs] “Route tasks from team chat: mention @Claude in Slack with a bug report and get a pull request back”

   proof ↗⚑ flag

   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

Team knowledge

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

   weight 1 · round to Claude Code
   Claude Code~partialclaimed5/10

   CLAUDE.md gives teams a shared, repo-committed markdown file for coding standards, architecture decisions, and review checklists that Claude reads every session, and shareable Skills (e.g. /review-pr, /deploy-staging) let a lead codify team workflows; MCP integrations let Claude also pull in Google Drive docs, Jira tickets, and Slack data as additional context sources. However, this is scattered configuration/context-injection tooling rather than a dedicated 'workspace' or knowledge-base product that unifies docs and repos into one queryable source of truth for the whole team. Missing for 10: a purpose-built shared workspace/knowledge-base UI, cross-repo aggregation, and evidence of team-wide adoption/governance beyond per-repo CLAUDE.md files.

   • [claimed-docs] “CLAUDE.md is a markdown file you add to your project root that Claude Code reads at the start of every session.”
   • [claimed-docs] “CLAUDE.md is a markdown file you add to your project root that Claude Code reads at the start of every session. Use it to set coding standar…”
   • [claimed-docs] “Create skills to package repeatable workflows your team can share, like `/review-pr` or `/deploy-staging`.”
   • [claimed-docs] “With MCP, Claude Code can read your design docs in Google Drive, update tickets in Jira, pull data from Slack, or use your own custom toolin…”
   • [claimed-docs] “Claude Code can read your design docs in Google Drive, update tickets in Jira, pull data from Slack, or use your own custom tooling.”

   proof ↗⚑ flag

   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

Tool integration

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

   weight 3 · round to Claude Code
   Claude Code✓fullclaimed9/10

   Docs explicitly state Claude Code can connect via MCP to Jira, Slack, Google Drive, and other custom tooling, with concrete examples (updating Jira tickets, pulling Slack data, Notion MCP server add command) and multiple transport options. Missing for 10: independent/hands-on third-party confirmation of these specific integrations working in practice beyond vendor docs.

   • [claimed-docs] “Claude Code can read your design docs in Google Drive, update tickets in Jira, pull data from Slack, or use your own custom tooling.”
   • [claimed-docs] “With MCP, Claude Code can read your design docs in Google Drive, update tickets in Jira, pull data from Slack, or use your own custom toolin…”
   • [claimed-docs] “Update our standard email template based on the new Figma designs that were posted in Slack”
   • [claimed-docs] “Claude Code can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”
   • [claimed-docs] “Implement features from issue trackers: "Add the feature described in JIRA issue ENG-4521 and create a PR on GitHub."”
   • [claimed-docs] “claude mcp add --transport http notion https://mcp.notion.com/mcp”
   • [claimed-docs] “Add the feature described in JIRA issue ENG-4521 and create a PR on GitHub.”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Claude Code~partialclaimed7/10

   Docs confirm task kickoff from GitHub (@claude mentions, GitHub Code Review, GitHub Actions) and Slack (@Claude mention returns a PR), plus GitLab CI/CD integration, but there is no evidence of Linear integration or a Linear-triggered agent workflow. missing for 10: explicit Linear integration/trigger support, independent/hands-on confirmation of cross-platform task kickoff.

   • [github] “Use it in your terminal, IDE, or tag @claude on Github.”
   • [claimed-docs] “Route tasks from team chat: mention @Claude in Slack with a bug report and get a pull request back”
   • [claimed-docs] “Get automatic code review on every PR | GitHub Code Review”
   • [claimed-docs] “Claude Code integrates with GitHub, GitLab, and your command line tools to handle the entire workflow—reading issues, writing code, running …”
   • [claimed-docs] “In CI, you can automate code review and issue triage with GitHub Actions or GitLab CI/CD.”

   proof ↗⚑ flag

   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

Cross device continuity

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

   weight 2 · round to Claude Code
   Claude Code✓fullclaimed8/10

   Docs explicitly describe cross-device continuity: 'Remote Control' lets you continue work from phone/browser (docs-9), and 'claude --teleport' lets you start a task on web/mobile and pull it into your terminal later (docs-10), backed by browser/cloud session support (docs-13, docs-14, docs-26). missing for 10: independent/hands-on confirmation of teleport and remote-control reliability across devices

   • [claimed-docs] “Step away from your desk and keep working from your phone or any browser with Remote Control”
   • [claimed-docs] “Kick off a long-running task on the web or the Claude mobile app, then pull it into your terminal with `claude --teleport`.”
   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”
   • [claimed-docs] “Kick off long-running tasks and check back when they're done, work on repos you don't have locally, or run multiple tasks in parallel.”
   • [claimed-docs] “Run Claude Code in your browser with no local setup. Kick off long-running tasks and check back when they're done, work on repos you don't h…”

   proof ↗⚑ flag

   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

Ide integration

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

   weight 1 · round to Claude Code
   Claude Code✓fullclaimed8/10

   Docs explicitly describe a JetBrains plugin (IntelliJ IDEA, PyCharm, WebStorm, etc.) with interactive diff viewing and selection context sharing, directly matching the story. Missing for 10: independent/hands-on corroboration of the JetBrains plugin specifically (community evidence only covers CLI/terminal experience, not the IDE plugin).

   • [claimed-docs] “A plugin for IntelliJ IDEA, PyCharm, WebStorm, and other JetBrains IDEs with interactive diff viewing and selection context sharing.”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Claude Code
   Claude Code✓fullclaimed8/10

   Official docs confirm dedicated IDE integrations (VS Code extension with inline diffs, @-mentions, plan review, conversation history; JetBrains plugin with diff viewing and selection context sharing), plus terminal-based chat usable from within an IDE, and GitHub explicitly states 'Use it in your terminal, IDE, or tag @claude on Github.' Missing for 10: independent hands-on validation specifically of the IDE chat experience (community evidence is mostly about CLI/terminal use and general quality, not IDE-embedded chat specifically).

   • [claimed-docs] “The VS Code extension provides inline diffs, @-mentions, plan review, and conversation history directly in your editor.”
   • [claimed-docs] “A plugin for IntelliJ IDEA, PyCharm, WebStorm, and other JetBrains IDEs with interactive diff viewing and selection context sharing.”
   • [github] “Use it in your terminal, IDE, or tag @claude on Github.”
   • [claimed-docs] “Work with Claude directly in your codebase. Build, debug, and ship from your terminal, IDE, Slack, web, and more.”

   proof ↗⚑ flag

   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

Session management

1. developerReview diffs visually and run multiple sessions side by side in a desktop app

   weight 2 · round to Cursor
   Claude Code~partialclaimed6/10

   First-party docs explicitly state the capability ('Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions'), closely matching the story, and related IDE integrations (VS Code inline diffs, JetBrains interactive diff viewer) support visual diff review, but this appears to describe a web/desktop companion app rather than a fully detailed, screenshot-documented desktop client, and no independent or hands-on evidence corroborates the side-by-side multi-session desktop UI. Missing for 10: independent/hands-on confirmation of the desktop app's diff viewer and multi-session UI, and richer first-party documentation (screenshots, feature depth) beyond a single summary line.

   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”
   • [claimed-docs] “A plugin for IntelliJ IDEA, PyCharm, WebStorm, and other JetBrains IDEs with interactive diff viewing and selection context sharing.”
   • [claimed-docs] “The VS Code extension provides inline diffs, @-mentions, plan review, and conversation history directly in your editor.”
   • [claimed-docs] “Available for macOS, Linux, and Windows.”

   proof ↗⚑ flag

   Cursor✓fullclaimed6/10

   Cursor's docs explicitly describe inspecting diffs before merge and launching fleets of agents to work in parallel, both core to a desktop IDE experience with visual diff review and concurrent sessions. Missing for 10: independent/hands-on confirmation of the side-by-side session UI and a detailed walkthrough of the diff viewer beyond marketing copy.

   • [claimed-docs] “Inspect diffs, run checks, and catch problems before you merge”
   • [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.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Claude Code✓fullclaimed7/10

   Docs describe running multiple sessions side by side, kicking off parallel/cloud sessions from a browser, and spawning multiple coordinated sub-agents under a lead agent, which directly support a lead managing several agent sessions from one workspace (claude-code-docs-13, -14, -26, -6, -34, -44). Missing for 10: independent/hands-on confirmation of the 'unified workspace' UX (no community reports specifically validate multi-session management) and no detail on session-level access control across a team for the lead-agent view.

   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”
   • [claimed-docs] “Kick off long-running tasks and check back when they're done, work on repos you don't have locally, or run multiple tasks in parallel.”
   • [claimed-docs] “Run Claude Code in your browser with no local setup. Kick off long-running tasks and check back when they're done, work on repos you don't h…”
   • [claimed-docs] “Spawn multiple Claude Code agents that work on different parts of a task simultaneously. A lead agent coordinates the work, assigns subtasks…”
   • [claimed-docs] “Spawn multiple Claude Code agents that work on different parts of a task simultaneously.”
   • [claimed-docs] “Spawn multiple Claude Code agents that work on different parts of a task simultaneously. A lead agent coordin”

   proof ↗⚑ flag

   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

Terminal workflow

1. developerRun a coding agent locally from my terminal

   weight 3 · round to Claude Code
   Claude Code✓fullcommunity9/10

   Claude Code is explicitly documented as a terminal-native coding agent: install via curl script, run with cd your-project && claude, available on macOS/Linux/Windows, and GitHub README confirms 'Use it in your terminal, IDE, or tag @claude on Github.' Community posts corroborate hands-on terminal use, noting it's 'implemented as a bash tool and not an editor replacement.' Missing for 10: broader independent benchmark or third-party review confirming consistent reliability of local terminal operation beyond a few anecdotal community posts.

   • [claimed-docs] “cd your-project claude”
   • [claimed-docs] “curl -fsSL https://claude.ai/install.sh | bash”
   • [claimed-docs] “Available for macOS, Linux, and Windows.”
   • [github] “Use it in your terminal, IDE, or tag @claude on Github.”
   • [community] “The cost is absurd (compared to other LLM providers these days). I asked 3 questions and the cost was ~0.77c. I do like how this is implemen…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Claude Code
   Claude Code✓fullclaimed8/10

   Docs explicitly describe non-interactive automation: piping logs, running in CI, scheduling recurring tasks, GitHub Actions/GitLab CI/CD integration for automated code review and issue triage, and headless-style scripting per Unix philosophy. missing for 10: no explicit mention of a documented --print/non-interactive flag or exit-code behavior, and no independent/hands-on report confirming scripted CI usage works as described.

   • [claimed-docs] “Claude Code is composable and follows the Unix philosophy. Pipe logs into it, run it in CI, or chain it with other tools”
   • [claimed-docs] “Run Claude on a schedule to automate work that repeats: morning PR reviews, overnight CI failure analysis, weekly dependency audits, or sync…”
   • [claimed-docs] “In CI, you can automate code review and issue triage with GitHub Actions or GitLab CI/CD.”
   • [claimed-docs] “Get automatic code review on every PR | GitHub Code Review”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Claude Code
   Claude Code~partialclaimed5/10

   Claude Code exposes an Agent SDK for building custom agents with 'full control over orchestration, tool access, and permissions' (docs-18) and supports direct API-key access and CI/headless automation (docs-36, docs-39/40), suggesting core coding capabilities are programmatically accessible. However, evidence doesn't confirm parity for UI-specific features like Remote Control, teleport, mobile app, or Slack routing being fully reachable via the API/SDK. Missing for 10: explicit documentation that all UI-surfaced features (remote control, teleport, IDE-specific interactions) are equally available through the API/SDK, and independent confirmation of this parity.

   • [claimed-docs] “the Agent SDK lets you build your own agents powered by Claude Code's tools and capabilities, with full control over orchestration, tool acc…”
   • [claimed-docs] “In CI, you can automate code review and issue triage with GitHub Actions or GitLab CI/CD.”
   • [claimed-docs] “If you've set the ANTHROPIC_API_KEY environment variable, Claude Code skips the login prompt and asks you to approve the key instead.”
   • [claimed-docs] “ANTHROPIC_API_KEY environment variable. Sent as the X-Api-Key header. Use this for direct Anthropic API access with a key from the Claude Co…”
   • [claimed-docs] “Use Claude Code as an MCP server. You can use Claude Code itself as an MCP server that other applications can connect to: claude mcp serve (…”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Claude Code—none0/10

   The evidence pack contains no mention of a data export feature, session/conversation history export, or open-format portability guarantees for Claude Code — nothing addresses a user's ability to extract all their data and leave the platform. While Claude Code operates on local files (inherently open), there is no documented mechanism for exporting session logs, configs, or account data in open formats, so this applicable axis is unsupported.

   ⚑ flag

   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

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

   weight 2 · round drawn
   Claude Code—none0/10

   No evidence Claude Code's source is available under an open license; in fact community discussion explicitly contrasts it with an open-source competitor, noting 'Codex CLI is FOSS, unlike Claude Code' — confirming it is closed-source.

   • [community] “Codex CLI is FOSS, unlike Claude Code, so Codex is less likely to do things like that, and it's one more reason to avoid Claude Code and Cla…”

   proof ↗⚑ flag

   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

Authentication

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

   weight 2 · round to Claude Code
   Claude Code✓fullclaimed9/10

   Docs explicitly confirm ANTHROPIC_API_KEY env var authentication bypasses the account login prompt, using it for direct API access via X-Api-Key header, as an alternative to Claude.ai account login. missing for 10: independent/hands-on community confirmation of this specific auth flow (only first-party docs cited).

   • [claimed-docs] “If you've set the ANTHROPIC_API_KEY environment variable, Claude Code skips the login prompt and asks you to approve the key instead.”
   • [claimed-docs] “ANTHROPIC_API_KEY environment variable. Sent as the X-Api-Key header. Use this for direct Anthropic API access with a key from the Claude Co…”
   • [claimed-docs] “Claude Pro or Max subscription: log in with your Claude.ai account.”
   • [claimed-docs] “Individual users can log in with a claude.ai account, while teams can use Claude for Teams or Enterprise, the Claude Console, or a cloud pro…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Claude Code
   Claude Code✓fullclaimed8/10

   Claude Code documents enterprise authentication via SSO/SAML, domain capture, role-based permissions, compliance API, and managed policy settings under Claude for Enterprise, plus flexible auth options (Console API key, Claude.ai account, Teams/Enterprise, cloud provider) for scaling across org structures. missing for 10: independent/hands-on corroboration of SSO setup working in practice, and no explicit mention of cloud IAM integration (e.g., AWS/GCP native identity federation) beyond 'cloud provider' mention.

   • [claimed-docs] “Claude for Enterprise: adds SSO, domain capture, role-based permissions, compliance API, and managed policy settings for organization-wide C…”
   • [claimed-docs] “Single sign-on (SSO/SAML) and domain capture”
   • [claimed-docs] “Individual users can log in with a claude.ai account, while teams can use Claude for Teams or Enterprise, the Claude Console, or a cloud pro…”
   • [claimed-docs] “Claude Pro or Max subscription: log in with your Claude.ai account.”
   • [claimed-docs] “You can sign in to your Console account without creating an API key, even when your organization doesn't let developers create them.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Claude Code
   Claude Code✓fullclaimed9/10

   Docs explicitly confirm developers can log in with their existing Claude Pro or Max subscription (claude.ai account) instead of needing a separate API key, with API key as an alternative for direct API access. Missing for 10: independent/hands-on confirmation of the subscription login flow working smoothly in practice (community evidence focuses on other topics, not this login flow specifically).

   • [claimed-docs] “Claude Pro or Max subscription: log in with your Claude.ai account.”
   • [claimed-docs] “Individual users can log in with a claude.ai account, while teams can use Claude for Teams or Enterprise, the Claude Console, or a cloud pro…”
   • [claimed-docs] “If you've set the ANTHROPIC_API_KEY environment variable, Claude Code skips the login prompt and asks you to approve the key instead.”
   • [claimed-docs] “ANTHROPIC_API_KEY environment variable. Sent as the X-Api-Key header. Use this for direct Anthropic API access with a key from the Claude Co…”

   proof ↗⚑ flag

   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

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

   weight 1 · round to Claude Code
   Claude Code~partialclaimed6/10

   Docs confirm individual developers can log in with a personal claude.ai account (Pro/Max subscription) instead of managing an API key, and that API-key auth is optional/alternate. However, evidence only references Pro/Max subscription login, not an explicit free tier for Claude Code — missing for 10: explicit confirmation that a free/no-cost claude.ai account grants Claude Code access, and independent user corroboration of free-tier login flow.

   • [claimed-docs] “Claude Pro or Max subscription: log in with your Claude.ai account.”
   • [claimed-docs] “If you've set the ANTHROPIC_API_KEY environment variable, Claude Code skips the login prompt and asks you to approve the key instead.”
   • [claimed-docs] “ANTHROPIC_API_KEY environment variable. Sent as the X-Api-Key header. Use this for direct Anthropic API access with a key from the Claude Co…”
   • [claimed-docs] “Individual users can log in with a claude.ai account, while teams can use Claude for Teams or Enterprise, the Claude Console, or a cloud pro…”

   proof ↗⚑ flag

   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

Model choice

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

   weight 1 · round drawn
   Claude Code—none0/10

   No evidence in the pack describes automatic model selection or routing per task; users manually choose models (e.g., Sonnet vs Opus per comm-19) and there's no mention of an auto-select feature. Missing for 10: any docs describing automatic model routing/selection logic based on task complexity or cost.

   ⚑ flag

   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

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

   weight 2 · round to Cursor
   Claude Code—none0/10

   Evidence shows Claude Code authentication routes (Claude.ai login, API key, Console, Enterprise SSO) are all tied to Anthropic's own Claude models; there is no mention of selecting GPT, Gemini, or other third-party model providers to power a session. Since comparable coding tools do offer multi-provider model selection, this axis applies but is unevidenced here.

   • [claimed-docs] “Claude Pro or Max subscription: log in with your Claude.ai account.”
   • [claimed-docs] “If you've set the ANTHROPIC_API_KEY environment variable, Claude Code skips the login prompt and asks you to approve the key instead.”
   • [claimed-docs] “ANTHROPIC_API_KEY environment variable. Sent as the X-Api-Key header. Use this for direct Anthropic API access with a key from the Claude Co…”
   • [claimed-docs] “Individual users can log in with a claude.ai account, while teams can use Claude for Teams or Enterprise, the Claude Console, or a cloud pro…”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Claude Code—none0/10

   No evidence pack items mention data residency, regional data storage options, or geographic controls for where Claude Code data is processed/stored; only SSO/domain capture/compliance API for enterprise IAM are mentioned. Missing for 10: any documentation of region selection, data residency guarantees, or geo-specific storage controls.

   ⚑ flag

   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

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

   weight 3 · round drawn
   Claude Code—none0/10

   The evidence pack includes enterprise/compliance features (SSO, compliance API, managed policies) but contains no mention of any training-data opt-out, data-usage policy, or explicit statement that user code/conversations are excluded from model training.

   ⚑ flag

   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

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Claude Code—none0/10

   The evidence pack shows enterprise features like SSO, domain capture, and a vague 'compliance API' but nothing describing user-controllable data retention settings or deletion of stored conversation/code data. No documentation addresses how users can view, export, or delete retained data.

   ⚑ flag

   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

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

   weight 2 · round drawn
   Claude Code—none0/10

   The evidence pack contains no documentation or reference to a telemetry/usage-tracking opt-out setting (e.g., no mention of a DISABLE_TELEMETRY flag, privacy settings page, or opt-out toggle) for Claude Code. Community commentary touches on unrelated trust/security concerns (anti-distillation fake tools, undercover mode) but none confirm or deny a telemetry opt-out mechanism.

   ⚑ flag

   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

Data governance

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

   weight 1 · round drawn
   Claude Code—none0/10

   The evidence pack contains no documentation or statements about Claude Code's data usage or model-training policies, nor any opt-out mechanism for code/prompt data. Enterprise features mentioned (SSO, compliance API, RBAC) do not address training data usage, and community items are unrelated to this specific concern.

   ⚑ flag

   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

Pr review

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

   weight 3 · round to Claude Code
   Claude Code✓fullclaimed8/10

   First-party docs explicitly state Claude Code 'stages changes, writes commit messages, creates branches, and opens pull requests' and integrates with GitHub/GitLab to handle the entire workflow including submitting PRs, corroborated by the GitHub repo description mentioning it 'handles git workflows'. Missing for 10: independent hands-on verification of a full stage-commit-branch-PR flow (community evidence discusses code quality/trust issues but not this specific git workflow failing).

   • [claimed-docs] “Claude Code works directly with git. It stages changes, writes commit messages, creates branches, and opens pull requests.”
   • [claimed-docs] “Claude Code integrates with GitHub, GitLab, and your command line tools to handle the entire workflow—reading issues, writing code, running …”
   • [github] “helps you code faster by executing routine tasks, explaining complex code, and handling git workflows -- all through natural language comman…”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Claude Code✓fullcommunity7/10

   Docs explicitly advertise 'Get automatic code review on every PR | GitHub Code Review' plus CI-based automated code review/issue triage and enterprise security code review, and CLAUDE.md can encode review checklists; community evidence even notes Claude performs well specifically as a reviewer. missing for 10: independent hands-on validation of the GitHub Code Review integration itself and detail on how contextual feedback is generated/delivered on PRs.

   • [claimed-docs] “Get automatic code review on every PR | GitHub Code Review”
   • [claimed-docs] “In CI, you can automate code review and issue triage with GitHub Actions or GitLab CI/CD.”
   • [claimed-docs] “Claude helps security teams and developers by reviewing code for security issues, drafts patches, and explains the risk in language your who…”
   • [claimed-docs] “CLAUDE.md is a markdown file you add to your project root that Claude Code reads at the start of every session. Use it to set coding standar…”
   • [community] “I have found that Claude Opus 4.6 is a better reviewer than it is an implementer. When Codex implements and Claude reviews, it's usually jus…”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Claude Code
   Claude Code~partialcommunity6/10

   Claude Code supports diff inspection (inline diffs in VS Code/JetBrains, visual diff review in web/desktop UI) and can run tests, lint, and CI checks as part of its workflow, plus automatic PR code review via GitHub integration. However, the story's 'inspect diffs and run checks before merging' as a cohesive reviewer workflow is only partially evidenced — there's no dedicated diff/lint/test-gate UI walkthrough, and community reports raise self-verification concerns (e.g., replace_all bugs going undetected). missing for 10: a dedicated pre-merge review workflow with integrated check-gating (not just individual features), independent hands-on validation of diff-review accuracy, and evidence addressing the self-verification skepticism raised in community reports.

   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”
   • [claimed-docs] “The VS Code extension provides inline diffs, @-mentions, plan review, and conversation history directly in your editor.”
   • [claimed-docs] “A plugin for IntelliJ IDEA, PyCharm, WebStorm, and other JetBrains IDEs with interactive diff viewing and selection context sharing.”
   • [claimed-docs] “Get automatic code review on every PR | GitHub Code Review”
   • [claimed-docs] “Hooks let you run shell commands before or after Claude Code actions, like auto-formatting after every file edit or running lint before a co…”
   • [claimed-docs] “In CI, you can automate code review and issue triage with GitHub Actions or GitLab CI/CD.”
   • [community] “I've been using Claude Code daily for months on a project with Elixir, Rust, and Python. The worst failure mode is when it does a replace_al…”
   • [community] “I have found that Claude Opus 4.6 is a better reviewer than it is an implementer. When Codex implements and Claude reviews, it's usually jus…”

   proof ↗⚑ flag

   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

Safe execution

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

   weight 2 · round to Cursor
   Claude Code~partialclaimed6/10

   Claude Code supports MCP server allow-listing via config (claude mcp add), sandboxed Bash tool with filesystem/network domain controls, and Enterprise-tier managed policy settings/SSO/role-based permissions that let an engineering lead govern tool and integration access. However, evidence doesn't show granular per-tool allow/deny lists at a team-policy level outside Enterprise, nor independent confirmation these controls reliably block unauthorized MCP/tool use in practice. missing for 10: fine-grained non-enterprise tool permission controls, independent/hands-on verification that access restrictions are enforced, and centralized audit/reporting of which integrations were actually used.

   • [claimed-docs] “Claude Code can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”
   • [claimed-docs] “claude mcp add --transport http notion https://mcp.notion.com/mcp”
   • [claimed-docs] “Stdio servers run as local processes on your machine. They're ideal for tools that need direct system access or custom scripts.”
   • [claimed-docs] “Use Claude Code as an MCP server. You can use Claude Code itself as an MCP server that other applications can connect to: claude mcp serve (…”
   • [claimed-docs] “Learn how Claude Code's sandboxed Bash tool provides filesystem and network isolation for safer, more autonomous agent execution. The Bash s…”
   • [claimed-docs] “Claude for Enterprise: adds SSO, domain capture, role-based permissions, compliance API, and managed policy settings for organization-wide C…”
   • [claimed-docs] “Single sign-on (SSO/SAML) and domain capture”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Claude Code
   Claude Code✓fullclaimed8/10

   Claude Code documents a dedicated sandboxed Bash tool that enforces filesystem and network isolation via OS-level boundaries, letting the agent run commands autonomously within defined limits rather than requiring per-command approval. missing for 10: independent/hands-on verification of sandbox robustness, and detail on sandboxing coverage for non-Bash tool calls (e.g., MCP tool network access).

   • [claimed-docs] “Learn how Claude Code's sandboxed Bash tool provides filesystem and network isolation for safer, more autonomous agent execution. The Bash s…”

   proof ↗⚑ flag

   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

Security checks

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

   weight 1 · round drawn
   Claude Code—none0/10

   No evidence anywhere in the pack of license detection, public-code/OSS match references, or provenance attribution for AI-suggested code; Claude Code's documented features focus on code generation, review, MCP integrations, and workflow automation, not license/plagiarism matching.

   ⚑ flag

   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

2. developerGet contextual explanations and automatic fixes for security vulnerabilities

   weight 2 · round to Claude Code
   Claude Code✓fullclaimed7/10

   Anthropic's enterprise docs explicitly state Claude Code reviews code for security issues, drafts patches, and explains risk in plain language, directly matching the story's contextual-explanation-plus-fix pattern, and this is reinforced by automatic PR code review integration. Missing for 10: independent/hands-on evidence confirming automatic vulnerability fixes work reliably in practice, and more detail on the security-specific workflow beyond a single marketing mention.

   • [claimed-docs] “Claude helps security teams and developers by reviewing code for security issues, drafts patches, and explains the risk in language your who…”
   • [claimed-docs] “Get automatic code review on every PR | GitHub Code Review”
   • [claimed-docs] “In CI, you can automate code review and issue triage with GitHub Actions or GitLab CI/CD.”

   proof ↗⚑ flag

   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