Cursor vs Cline

Agent access

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

   weight 2 · round to Cline
   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

   Cline~partialprobed6/10

   Cline's own docs site publishes a working llms.txt (probe-confirmed HTTP 200) and Cline can browse the web and pull in external tools/data via MCP, implying a user could point the agent at llms.txt or similar agent-oriented docs for context. However, there is no explicit first-party documentation describing a workflow for feeding llms.txt or agent-oriented doc formats into Cline's context. Missing for 10: explicit documented feature/workflow for ingesting llms.txt as agent context, and independent confirmation of this specific use case.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.cline.bot/llms.txt # Cline > AI-powered coding agent for complex work - [Cline Overview](https://…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.cline.bot/cline-overview.md > ## Documentation Index > Fetch the complete documentation index at: ht…”
   • [claimed-docs] “AI coding assistant in your editor. Create files, run commands, browse the web, and use tools with human-in-the-loop approval.”
   • [claimed-docs] “MCP (Model Context Protocol) lets Cline use external tools and data sources through MCP servers.”

   proof ↗⚑ flag

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

   weight 2 · round to Cline
   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

   Cline✓fullclaimed9/10

   Cline ships a dedicated CLI with explicit headless/automation mode, auto-approve flags for unattended runs, pipeable I/O (git diff | cline), cron scheduling via hub, and documented CI/CD integration (GitHub Actions, GitLab pipelines). Multiple first-party docs corroborate this across CLI overview, scheduling, and marketing pages. Missing for 10: independent/community hands-on confirmation of CI usage specifically (community evidence covers general tool quality, not headless CI runs).

   • [claimed-docs] “Run Cline in your terminal with interactive chat or fully headless automation for CI/CD and scripting.”
   • [claimed-docs] “Use headless mode for scripts/automation and processable output.”
   • [claimed-docs] “Autonomous execution can modify files and run commands without further prompts.”
   • [claimed-docs] “Chat with the agent from Slack, Discord, Telegram, or Linear. Run it headlessly inside GitHub Actions, GitLab, or any pipeline.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [claimed-docs] “Use Cline CLI for interactive terminal sessions and automated headless workflows.”
   • [claimed-docs] “cline --auto-approve true "run tests and fix failures"”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [claimed-docs] “Run agents on cron schedules for recurring automations like daily summaries and code reviews.”

   proof ↗⚑ flag

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

   weight 3 · round to Cline
   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

   Cline✓fullclaimed9/10

   Cline explicitly documents MCP support ('MCP lets Cline use external tools and data sources through MCP servers') and both the CLI/hub and GitHub docs reference managing MCP servers alongside models and plugins; auto-approve settings even list MCP tools as controllable. Missing for 10: independent hands-on verification of MCP server setup/usage beyond docs and GitHub blurb.

   • [claimed-docs] “MCP (Model Context Protocol) lets Cline use external tools and data sources through MCP servers.”
   • [github] “Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP servers.”
   • [github] “Cline as a native app for macOS and Windows. Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP server…”
   • [claimed-docs] “YOLO mode is Auto Approve on steroids. Check the box and Cline auto-approves everything: file changes, terminal commands, browser actions, M…”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Cline
   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

   Cline✓fullprobed9/10

   Cline ships a well-documented official CLI (npm install -g cline) supporting interactive and headless modes, auto-approve automation, piping (git diff | cline), scripting/CI use, and cron scheduling via the hub, all under the same core engine as other Cline surfaces. Missing for 10: independent/hands-on community verification specifically of the CLI (community evidence discusses the IDE/agent experience generally, not the CLI itself).

   • [claimed-docs] “Run Cline in your terminal with interactive chat or fully headless automation for CI/CD and scripting.”
   • [claimed-docs] “Use headless mode for scripts/automation and processable output.”
   • [claimed-docs] “Autonomous execution can modify files and run commands without further prompts.”
   • [claimed-docs] “npm install -g cline”
   • [claimed-docs] “Use Cline CLI for interactive terminal sessions and automated headless workflows.”
   • [claimed-docs] “cline --auto-approve true "run tests and fix failures"”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [probe] “official CLI documented at https://docs.cline.bot/usage/cli-overview”

   proof ↗⚑ flag

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

   weight 3 · round to Cline
   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

   Cline~partialprobed6/10

   Cline documents multiple programmatic surfaces — a scriptable CLI with headless mode and processable output (cline-docs-3, cline-docs-32), cron-scheduled agents (cline-docs-23), and the ACP protocol letting any ACP-capable client drive Cline as a coding agent (cline-docs-7, cline-docs-26) — which together let an AI-native user drive it programmatically. However, an explicit probe for a formal public REST/OpenAPI API found nothing (cline-probe-3: all candidate openapi/swagger paths 404), so there's no conventional documented public API, only CLI/ACP surfaces. Missing for 10: a formal REST/HTTP API with OpenAPI/swagger docs or SDK reference, and independent hands-on confirmation of scripting the CLI/ACP end-to-end.

   • [claimed-docs] “Use headless mode for scripts/automation and processable output.”
   • [claimed-docs] “Autonomous execution can modify files and run commands without further prompts.”
   • [claimed-docs] “Use Cline CLI for interactive terminal sessions and automated headless workflows.”
   • [claimed-docs] “cline --auto-approve true "run tests and fix failures"”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [claimed-docs] “Any ACP-capable client can use Cline as its coding agent without a dedicated extension”
   • [claimed-docs] “Any ACP-capable client can use Cline as its coding agent without a dedicated extension — the same agent you use in the terminal, embedded in…”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [claimed-docs] “Build AI agents and integrations powered by the same core engine behind the CLI, Kanban, VS Code extension, and JetBrains plugin.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cline.bot/openapi.json, https://docs.cline.bot/swagger.json, https://docs.cline.bot/api…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Cursor—none0/10

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

   ⚑ flag

   Cline—none0/10

   Evidence shows Cline supports Bring-Your-Own-Key (BYOK) for various providers and its own sign-in credit system, but there is no mention of issuing scoped, permission-limited, or least-privilege API credentials/tokens for the agent — only full provider keys and coarse action-approval settings (auto-approve, plan/act mode) which govern actions, not credential scope.

   • [claimed-docs] “Absolutely! You can bring your own API keys from providers like OpenAI, Anthropic, Google, and others.”
   • [claimed-docs] “Bring Your Own Key (BYOK): use your own provider credentials (cloud or local runtimes).”
   • [claimed-docs] “Instead of managing separate API keys across multiple vendors, you sign in once, add Cline credits, and select from available models directl…”
   • [claimed-docs] “Auto Approve lets you decide which actions Cline can take without prompting you each time.”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Cline
   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

   Cline~partialprobed3/10

   Cline docs mention building 'AI agents and integrations powered by the same core engine' behind its CLI/Kanban/IDE plugins, implying an SDK-like foundation, but there's no actual SDK package, API reference, or code samples, and a probe for OpenAPI/schema docs returned 404s across all candidate paths. missing for 10: published SDK package/reference docs, code samples for building against the engine, independent evidence of third-party integrations built with it.

   • [claimed-docs] “Build AI agents and integrations powered by the same core engine behind the CLI, Kanban, VS Code extension, and JetBrains plugin.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cline.bot/openapi.json, https://docs.cline.bot/swagger.json, https://docs.cline.bot/api…”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Cursor—none0/10

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

   ⚑ flag

   Cline—none0/10

   No evidence of webhook subscription capability; Cline's integrations (Slack, Discord, Telegram, Linear, CI/CD pipelines) are described as chat/automation surfaces, not an event/webhook subscription API, and the openapi probe returned all 404s suggesting no public API surface for such events.

   • [claimed-docs] “Chat with the agent from Slack, Discord, Telegram, or Linear. Run it headlessly inside GitHub Actions, GitLab, or any pipeline.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cline.bot/openapi.json, https://docs.cline.bot/swagger.json, https://docs.cline.bot/api…”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to Cursor
   Cursor✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   Cline~partialclaimed5/10

   Cline is an agentic coding assistant that generates code changes, diffs, and can research a codebase via subagents, which counts as AI-generated suggestions inside the product, but this is code-editing/task-execution rather than 'insights and suggestions from my data' in a BI/analytics sense — there's no evidence of dashboards, data analysis, or insight summaries over user data. missing for 10: evidence of analyzing/summarizing arbitrary user data (not just code) and presenting insights/recommendations distinct from code edits.

   • [claimed-docs] “Subagents let Cline spawn focused research agents that run in parallel.”
   • [claimed-docs] “Subagents let Cline spawn focused research agents that run in parallel. Each subagent gets its own prompt and context window, explores the c…”
   • [github] “In VS Code and JetBrains, every edit shows up as a diff you can review, modify, or revert.”
   • [claimed-docs] “Coordinated multi-file changes with linter-aware fixes, diffs, checkpoints, and one-click undo on every step.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Cline✓fullclaimed8/10

   Cline's CLI/hub explicitly supports cron-scheduled agents that persist across restarts and run independently of any terminal session, enabling recurring background automations like daily summaries or code reviews, plus headless mode for CI/CD pipelines and chat integrations (Slack/Discord/Telegram/Linear). This is well documented first-party but lacks independent hands-on confirmation of the scheduling feature specifically. Missing for 10: independent/community verification of the cron-scheduling feature working in practice, more detail on reliability/failure handling of unattended runs.

   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [claimed-docs] “Run agents on cron schedules for recurring automations like daily summaries and code reviews.”
   • [claimed-docs] “Chat with the agent from Slack, Discord, Telegram, or Linear. Run it headlessly inside GitHub Actions, GitLab, or any pipeline.”
   • [claimed-docs] “Use headless mode for scripts/automation and processable output.”
   • [claimed-docs] “Autonomous execution can modify files and run commands without further prompts.”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   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

   Cline✓fullcommunity9/10

   Cline is a built-in AI coding assistant that can be delegated tasks directly (file edits, terminal commands, browser use) via natural conversation, with plan/act modes, auto-approve/YOLO autonomy, and hands-on community corroboration of effective autonomous task completion. Both first-party docs and independent HN reviews confirm real delegation of substantive coding tasks. Missing for 10: no independent benchmark/quality study beyond anecdotal forum praise/criticism.

   • [claimed-docs] “AI coding assistant in your editor. Create files, run commands, browse the web, and use tools with human-in-the-loop approval.”
   • [claimed-docs] “It can read and write files, run terminal commands, use a browser, and help you build features through natural conversation. Every action re…”
   • [claimed-docs] “Plan mode lets you explore and strategize without changing files. Act mode executes against your plan.”
   • [claimed-docs] “Auto Approve lets you decide which actions Cline can take without prompting you each time.”
   • [claimed-docs] “YOLO mode is Auto Approve on steroids. Check the box and Cline auto-approves everything: file changes, terminal commands, browser actions, M…”
   • [community] “Cline is, hands down, the most effective agentic coding tool out there. I've extensively daily driven any one of them you can name, and ther…”
   • [community] “Cline is the most impressive agentic coder tool I've used and it seems to be getting better. I can plan with it for 10-15 minutes, set it lo…”
   • [community] “I can have cline control a terminal command, it's by no means limited to editing code... I find Cline better [than Claude Code] (plus I can …”

   proof ↗⚑ flag

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

   weight 2 · round to Cline
   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

   Cline✓fullcommunity9/10

   Cline is built entirely around natural-language task commands — through IDE chat, CLI ('cline "run tests and fix failures"'), Slack/Discord/Telegram/Linear chat, and headless CI automation — and community reviews corroborate it as a strong agentic natural-language coding tool. Missing for 10: no formal benchmark/independent test of NL command robustness across all surfaces.

   • [claimed-docs] “It can read and write files, run terminal commands, use a browser, and help you build features through natural conversation. Every action re…”
   • [claimed-docs] “cline --auto-approve true "run tests and fix failures"”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [claimed-docs] “Chat with the agent from Slack, Discord, Telegram, or Linear. Run it headlessly inside GitHub Actions, GitLab, or any pipeline.”
   • [claimed-docs] “Use headless mode for scripts/automation and processable output.”
   • [community] “Cline is, hands down, the most effective agentic coding tool out there. I've extensively daily driven any one of them you can name, and ther…”
   • [community] “Cline is the most impressive agentic coder tool I've used and it seems to be getting better. I can plan with it for 10-15 minutes, set it lo…”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round drawn
   Cursor—none0/10

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

   ⚑ flag

   Cline—none0/10

   A direct probe for OpenAPI/swagger specs returned 404 on all candidate paths, and no documentation elsewhere references a downloadable machine-readable API spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cline.bot/openapi.json, https://docs.cline.bot/swagger.json, https://docs.cline.bot/api…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Cursor—none0/10

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

   ⚑ flag

   Cline—none0/10

   No evidence of versioned APIs or a documented deprecation policy; the OpenAPI probe found no API spec at any candidate path, and no docs mention API versioning or deprecation practices.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cline.bot/openapi.json, https://docs.cline.bot/swagger.json, https://docs.cline.bot/api…”

   proof ↗⚑ flag

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

   weight 2 · round to Cline
   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

   Cline✓fullclaimed7/10

   Cline explicitly supports running many agents in parallel via a Kanban task board with isolated worktrees and dependency chains, spawning parallel subagents for research, and CLI/cron-based headless automation for scripted bulk workflows (e.g. batch test-fixing, scheduled recurring runs). This directly supports bulk/automation-depth operations across many items, though evidence is entirely vendor-documented with no independent hands-on account of actually running large-scale bulk jobs. Missing for 10: independent/community verification of large-scale bulk usage, and concrete examples of bulk operations beyond parallel agents (e.g., processing many files/tickets in one command).

   • [claimed-docs] “Run many agents in parallel from a web-based task board with per-card worktrees, auto-commit, and dependency chains.”
   • [claimed-docs] “Use Cline Kanban to run multiple coding agents in parallel with isolated git worktrees.”
   • [claimed-docs] “Subagents let Cline spawn focused research agents that run in parallel.”
   • [claimed-docs] “Subagents let Cline spawn focused research agents that run in parallel. Each subagent gets its own prompt and context window, explores the c…”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [claimed-docs] “Run agents on cron schedules for recurring automations like daily summaries and code reviews.”
   • [claimed-docs] “cline --auto-approve true "run tests and fix failures"”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [claimed-docs] “Use headless mode for scripts/automation and processable output.”

   proof ↗⚑ flag

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

   weight 3 · round to Cline
   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

   Cline~partialclaimed7/10

   Cline's CLI/hub supports cron-scheduled agents that persist and run automatically (e.g., daily summaries, code reviews), plus headless mode for CI/CD pipelines and chat-platform triggers (Slack/Discord/Telegram/Linear), which together enable automatic action-triggering on time/events. However, this is scheduling/pipeline-integration rather than a general event-rule engine, and there's no independent/community verification of these automation triggers working reliably in practice. Missing for 10: a broader event-based rule/trigger system beyond cron and CI hooks, and hands-on/community corroboration of scheduled or event-driven automation actually functioning as documented.

   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [claimed-docs] “Run agents on cron schedules for recurring automations like daily summaries and code reviews.”
   • [claimed-docs] “Chat with the agent from Slack, Discord, Telegram, or Linear. Run it headlessly inside GitHub Actions, GitLab, or any pipeline.”
   • [claimed-docs] “Use headless mode for scripts/automation and processable output.”
   • [claimed-docs] “Run Cline in your terminal with interactive chat or fully headless automation for CI/CD and scripting.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   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

   Cline✓fullclaimed7/10

   Cline's docs explicitly describe running agents on cron schedules through its CLI hub, persisting across restarts, for recurring automations like daily summaries and code reviews (cline-docs-13, cline-docs-23, cline-docs-36), directly matching the story. Missing for 10: independent/hands-on confirmation of scheduling reliability and details on failure handling/monitoring of scheduled jobs.

   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [claimed-docs] “Run agents on cron schedules for recurring automations like daily summaries and code reviews.”
   • [claimed-docs] “Use Cline CLI for interactive terminal sessions and automated headless workflows.”

   proof ↗⚑ flag

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

   weight 1 · round to Cline
   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

   Cline~partialclaimed6/10

   Cline documents checkpoints, per-step diffs, and one-click undo for the agent's actions, plus Kanban card diff review with inline comments, which lets an ai-native user review and roll back the results of an automation run (cline-docs-30, cline-gh-1, cline-docs-47). However, there is no evidence of first-class versioning/rollback for the automation definitions themselves (skills, scheduled cron routines, subagent configs) — no version history or rollback UI is documented for those artifacts. Missing for 10: explicit version history/rollback for skills and scheduled automations, independent hands-on confirmation of the undo/checkpoint feature working reliably.

   • [claimed-docs] “Coordinated multi-file changes with linter-aware fixes, diffs, checkpoints, and one-click undo on every step.”
   • [github] “In VS Code and JetBrains, every edit shows up as a diff you can review, modify, or revert.”
   • [claimed-docs] “Review diffs in card detail view and leave inline comments.”
   • [claimed-docs] “Skills are modular instruction sets that extend Cline's capabilities for specific tasks.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”

   proof ↗⚑ flag

Background execution

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

   weight 2 · round to Cursor
   Cursor✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   Cline~partialclaimed6/10

   Cline supports headless/autonomous execution, cron-scheduled agents, parallel Kanban agents with isolated worktrees, auto-commit, diff review, and inline comments, which together approximate a 'cloud agent builds/tests/demos and I review' workflow. However, there's no explicit evidence of a fully cloud-hosted (non-local) agent environment, integrated automated testing/demo generation, or a dedicated review UI beyond diff/comment viewing. missing for 10: dedicated cloud execution environment (not just local/CI runners), built-in test execution and demo artifact generation, end-to-end proof of a single autonomous run producing a reviewable demo, independent hands-on confirmation of this specific workflow.

   • [claimed-docs] “Run many agents in parallel from a web-based task board with per-card worktrees, auto-commit, and dependency chains.”
   • [claimed-docs] “Use Cline Kanban to run multiple coding agents in parallel with isolated git worktrees.”
   • [claimed-docs] “Review diffs in card detail view and leave inline comments.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [claimed-docs] “Chat with the agent from Slack, Discord, Telegram, or Linear. Run it headlessly inside GitHub Actions, GitLab, or any pipeline.”
   • [claimed-docs] “Autonomous execution can modify files and run commands without further prompts.”

   proof ↗⚑ flag

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

   weight 3 · round to Cursor
   Cursor✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Cline~partialclaimed4/10

   Cline supports background/async execution via CLI headless mode, cron-scheduled agents that 'persist across process restarts and run independently of any terminal session,' and a Kanban board with isolated git worktrees for parallel agents, plus CI/CD integration (GitHub Actions/GitLab). However, none of this evidence describes a Cline-hosted or fully isolated cloud sandbox — the scheduling/hub and worktrees appear to run on the user's own machine or CI infrastructure rather than a dedicated cloud environment. missing for 10: explicit documentation of a Cline-managed cloud/remote execution environment, isolation guarantees (e.g., containerization) for background tasks, and independent confirmation of cloud-hosted background runs.

   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [claimed-docs] “Run agents on cron schedules for recurring automations like daily summaries and code reviews.”
   • [claimed-docs] “Use Cline Kanban to run multiple coding agents in parallel with isolated git worktrees.”
   • [claimed-docs] “Chat with the agent from Slack, Discord, Telegram, or Linear. Run it headlessly inside GitHub Actions, GitLab, or any pipeline.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub.”

   proof ↗⚑ flag

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

   weight 2 · round to Cursor
   Cursor~partialclaimed4/10

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

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

   proof ↗⚑ flag

   Cline—none0/10

   Cline's evidence covers local IDE/CLI/terminal execution, worktrees, kanban boards, and CI/CD headless runs, but nothing describes configuring a reproducible cloud sandbox environment (e.g., devcontainer-style setup, dependency installation scripts, or a persistent cloud VM) tied to a repository.

   ⚑ 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 drawn
   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

   Cline✓fullclaimed8/10

   Cline's Kanban board explicitly supports running many agents in parallel with isolated git worktrees, auto-commit, and dependency chains, while subagents spawn parallel focused research agents and CLI scheduling lets agents run on cron schedules that persist across restarts and run independently of any terminal session—directly matching 'fleets working in parallel for hours or days.' Missing for 10: independent/hands-on corroboration of long-duration (multi-day) fleet runs and scale limits, since community evidence only discusses single-agent session quality, not fleet orchestration.

   • [claimed-docs] “Run many agents in parallel from a web-based task board with per-card worktrees, auto-commit, and dependency chains.”
   • [claimed-docs] “Use Cline Kanban to run multiple coding agents in parallel with isolated git worktrees.”
   • [claimed-docs] “Subagents let Cline spawn focused research agents that run in parallel. Each subagent gets its own prompt and context window, explores the c…”
   • [claimed-docs] “Subagents let Cline spawn focused research agents that run in parallel.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [claimed-docs] “Run agents on cron schedules for recurring automations like daily summaries and code reviews.”
   • [github] “Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP servers.”

   proof ↗⚑ flag

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

   weight 1 · round to Cline
   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

   Cline✓fullclaimed8/10

   Cline's Kanban board explicitly supports running multiple coding agents in parallel with isolated git worktrees per card, and lets you review diffs and leave inline comments per card before deciding which to keep — directly matching the parallel-attempt/compare story. missing for 10: independent/hands-on corroboration of the Kanban parallel-run workflow (community evidence covers general Cline use, not Kanban specifically), and no detail on an explicit 'pick winner and discard others' UX beyond diff review.

   • [claimed-docs] “Run many agents in parallel from a web-based task board with per-card worktrees, auto-commit, and dependency chains.”
   • [claimed-docs] “Use Cline Kanban to run multiple coding agents in parallel with isolated git worktrees.”
   • [claimed-docs] “Review diffs in card detail view and leave inline comments.”
   • [github] “Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP servers.”
   • [github] “Cline as a native app for macOS and Windows. Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP server…”

   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 drawn
   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

   Cline✓fullclaimed8/10

   Cline's CLI documents cron-based scheduling of agents that 'persist across process restarts and run independently of any terminal session,' explicitly for 'recurring automations like daily summaries and code reviews' (cline-docs-13, 23, 36), plus chat-triggered agents via Slack/Discord/Telegram/Linear and headless operation in CI/CD pipelines (cline-docs-17), combined with auto-approve/YOLO mode for unattended autonomous execution (cline-docs-21, 22). missing for 10: independent/hands-on corroboration of the scheduling feature actually working reliably in production, and more detail on trigger-based (non-cron) autonomous maintenance workflows

   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [claimed-docs] “Run agents on cron schedules for recurring automations like daily summaries and code reviews.”
   • [claimed-docs] “Chat with the agent from Slack, Discord, Telegram, or Linear. Run it headlessly inside GitHub Actions, GitLab, or any pipeline.”
   • [claimed-docs] “YOLO mode is Auto Approve on steroids. Check the box and Cline auto-approves everything: file changes, terminal commands, browser actions, M…”
   • [claimed-docs] “cline --auto-approve true "run tests and fix failures"”

   proof ↗⚑ flag

Code completion

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

   weight 3 · round drawn
   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

   Cline—none0/10

   Evidence describes Cline as a chat-driven, task-based agentic coding assistant that edits files via reviewable diffs and terminal actions, not an inline ghost-text/next-edit-suggestion tool that activates as you type. No citation mentions autocomplete-style inline completions or next-edit prediction.

   • [claimed-docs] “AI coding assistant in your editor. Create files, run commands, browse the web, and use tools with human-in-the-loop approval.”
   • [github] “In VS Code and JetBrains, every edit shows up as a diff you can review, modify, or revert.”
   • [claimed-docs] “Plan mode lets you explore and strategize without changing files. Act mode executes against your plan.”
   • [claimed-docs] “Coordinated multi-file changes with linter-aware fixes, diffs, checkpoints, and one-click undo on every step.”

   proof ↗⚑ flag

Debugging

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

   weight 1 · round to Cline
   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

   Cline~partialclaimed5/10

   Cline can run and interact with a live dev server/terminal in real time (cline-docs-14) and has a browser tool it can use to inspect visual issues (cline-docs-1, cline-docs-18, cline-docs-22), which supports basic live-app debugging like fixing layout bugs from a screenshot. However there's no evidence of deeper live-debugging features such as reading browser console/network logs, setting breakpoints, or inspecting running app state beyond screenshots. Missing for 10: console/network log inspection, breakpoint/step debugging, structured devtools integration, and independent hands-on confirmation of live web-app debugging.

   • [claimed-docs] “Executes in your terminal and reacts to output as it appears. Long-running dev servers, tests, deploys, all handled live.”
   • [claimed-docs] “AI coding assistant in your editor. Create files, run commands, browse the web, and use tools with human-in-the-loop approval.”
   • [claimed-docs] “fix the layout issue shown in @./screenshot.png”
   • [claimed-docs] “YOLO mode is Auto Approve on steroids. Check the box and Cline auto-approves everything: file changes, terminal commands, browser actions, M…”

   proof ↗⚑ flag

2. developerDebug issues and troubleshoot using natural-language queries

   weight 2 · round to Cline
   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

   Cline✓fullcommunity7/10

   Cline supports natural-language driven debugging: it can run tests and fix failures (cline-docs-33), react live to terminal output for dev servers/tests/deploys (cline-docs-14), review diffs and codebase issues via conversation (cline-docs-34, cline-docs-31), and community reviews confirm strong agentic troubleshooting effectiveness (cline-comm-1, cline-comm-3, cline-comm-10). Missing for 10: dedicated 'debugging mode' documentation, structured error-trace analysis features, and independent benchmarks specifically on bug-fixing accuracy.

   • [claimed-docs] “cline --auto-approve true "run tests and fix failures"”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [claimed-docs] “Executes in your terminal and reacts to output as it appears. Long-running dev servers, tests, deploys, all handled live.”
   • [claimed-docs] “It can read and write files, run terminal commands, use a browser, and help you build features through natural conversation. Every action re…”
   • [community] “Cline is, hands down, the most effective agentic coding tool out there. I've extensively daily driven any one of them you can name, and ther…”
   • [community] “Cline is the most impressive agentic coder tool I've used and it seems to be getting better. I can plan with it for 10-15 minutes, set it lo…”
   • [community] “I can have cline control a terminal command, it's by no means limited to editing code... I find Cline better [than Claude Code] (plus I can …”

   proof ↗⚑ flag

Feature implementation

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

   weight 3 · round to Cursor
   Cursor~partialclaimed7/10

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

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

   proof ↗⚑ flag

   Cline~partialclaimed4/10

   Cline offers strong underlying primitives—autonomous file edits, terminal/git command execution, headless CI/CD runs, and PR-adjacent workflows like 'git diff | cline review'—but there is no evidence of a dedicated feature that ingests a tracked issue (e.g., GitHub issue) and produces a complete pull request end-to-end. missing for 10: explicit issue-tracker integration (e.g., GitHub Issues API), automated PR creation/submission step, and any documented end-to-end issue-to-PR workflow or case study.

   • [claimed-docs] “Use headless mode for scripts/automation and processable output.”
   • [claimed-docs] “Autonomous execution can modify files and run commands without further prompts.”
   • [claimed-docs] “Chat with the agent from Slack, Discord, Telegram, or Linear. Run it headlessly inside GitHub Actions, GitLab, or any pipeline.”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [github] “In VS Code and JetBrains, every edit shows up as a diff you can review, modify, or revert.”

   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 drawn
   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

   Cline✓fullcommunity8/10

   Cline's core value prop is natural-language coding tasks executed across files with diffs, multi-file coordination, terminal execution, and undo/checkpoints, backed by both docs and strong community testimony of successful multi-file autonomous edits. missing for 10: independent benchmark data on multi-file bug-fix accuracy, and resolution of community complaints about needing many prompts/codebase indexing gaps in some cases.

   • [claimed-docs] “AI coding assistant in your editor. Create files, run commands, browse the web, and use tools with human-in-the-loop approval.”
   • [claimed-docs] “Coordinated multi-file changes with linter-aware fixes, diffs, checkpoints, and one-click undo on every step.”
   • [github] “In VS Code and JetBrains, every edit shows up as a diff you can review, modify, or revert.”
   • [claimed-docs] “cline --auto-approve true "run tests and fix failures"”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [community] “Cline is, hands down, the most effective agentic coding tool out there. I've extensively daily driven any one of them you can name, and ther…”
   • [community] “Cline is the most impressive agentic coder tool I've used and it seems to be getting better. I can plan with it for 10-15 minutes, set it lo…”
   • [community] “After trying cline, aider, codex, and what not, I feel claude code is just so so better than all of them. It takes much much fewer prompts t…”

   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 Cline
   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

   Cline✓fullcommunity7/10

   Cline is a general-purpose coding agent with terminal execution, file editing, and auto-approve modes; docs show concrete examples of writing/running tests and fixing failures (cline-docs-33), linter-aware multi-file fixes (cline-docs-30), and reviewing diffs (cline-docs-34), all backed by community reports of strong autonomous coding performance (cline-comm-1, cline-comm-3). Merge conflict resolution and dependency updates aren't explicitly demoed, but they fall squarely within the same terminal-command + file-edit capability set already evidenced. missing for 10: explicit worked example of merge conflict resolution, explicit example of dependency update workflow, independent hands-on validation of these exact tasks.

   • [claimed-docs] “cline --auto-approve true "run tests and fix failures"”
   • [claimed-docs] “Coordinated multi-file changes with linter-aware fixes, diffs, checkpoints, and one-click undo on every step.”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [claimed-docs] “Executes in your terminal and reacts to output as it appears. Long-running dev servers, tests, deploys, all handled live.”
   • [community] “Cline is, hands down, the most effective agentic coding tool out there. I've extensively daily driven any one of them you can name, and ther…”
   • [community] “Cline is the most impressive agentic coder tool I've used and it seems to be getting better. I can plan with it for 10-15 minutes, set it lo…”
   • [claimed-docs] “It can read and write files, run terminal commands, use a browser, and help you build features through natural conversation. Every action re…”

   proof ↗⚑ flag

Multimodal generation

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

   weight 2 · round to Cline
   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

   Cline~partialclaimed3/10

   Cline's CLI example shows it can accept an image reference (@./screenshot.png) to address a layout issue, implying some multimodal/image input capability, and general docs confirm it can build features from natural conversation and modify files/commands. However there is no evidence of a dedicated 'sketch/image/PDF-to-app' workflow, no PDF input support, and no documented end-to-end example of generating a full working app from a design file. missing for 10: PDF input support, a documented sketch-to-app or design-to-code workflow, evidence of generating a complete app (not just a layout fix) from an image.

   • [claimed-docs] “fix the layout issue shown in @./screenshot.png”
   • [claimed-docs] “It can read and write files, run terminal commands, use a browser, and help you build features through natural conversation. Every action re…”

   proof ↗⚑ flag

Codebase mapping

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

   weight 3 · round drawn
   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

   Cline~partialcommunity6/10

   Cline's Plan mode explicitly lets the agent read the codebase, run searches, and discuss strategy before any edits, and Subagents can explore the codebase independently and return detailed reports to help orient before changes are made, supporting the story's core intent. However, community discussion (HN) specifically disputes Cline's codebase-understanding approach, criticizing it for not indexing the codebase and calling this a 'missing major feature,' while other users report good results letting it explore and act on a codebase — a genuine mixed signal on how well it maps large/unfamiliar codebases. Missing for 10: a dedicated codebase-mapping/indexing feature, independent benchmarks on navigation accuracy, and resolution of the indexing critique.

   • [claimed-docs] “Plan mode is where you and Cline figure out what you're building and how. In this mode, Cline can read your codebase, run searches, and disc…”
   • [claimed-docs] “Subagents let Cline spawn focused research agents that run in parallel. Each subagent gets its own prompt and context window, explores the c…”
   • [github] “In VS Code and JetBrains, every edit shows up as a diff you can review, modify, or revert.”
   • [community] “This honestly makes me think less of Cline. They're wrong about this [not indexing codebase] and it seems like they're trying to do damage c…”
   • [community] “Cline is the most impressive agentic coder tool I've used and it seems to be getting better. I can plan with it for 10-15 minutes, set it lo…”

   proof ↗⚑ flag

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

   weight 3 · round to Cursor
   Cursor~partialclaimed4/10

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

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

   proof ↗⚑ flag

   Cline!disputedcontradicted5/10

   Cline's docs describe agentic exploration (Plan mode reads the codebase and runs searches, subagents spawn parallel research agents that 'explore the codebase independently' and report back) which supports mapping an unfamiliar codebase without manual file selection. However, a hands-on community discussion explicitly disputes this, criticizing Cline for not indexing the codebase and calling it 'wrong' and 'missing a major feature' for large/unfamiliar codebase understanding. Missing for 10: first-party documentation of a dedicated codebase-mapping/indexing feature, and independent corroboration that agentic search alone reliably substitutes for indexing on large unfamiliar repos.

   • [claimed-docs] “Plan mode is where you and Cline figure out what you're building and how. In this mode, Cline can read your codebase, run searches, and disc…”
   • [claimed-docs] “Subagents let Cline spawn focused research agents that run in parallel. Each subagent gets its own prompt and context window, explores the c…”
   • [claimed-docs] “Subagents let Cline spawn focused research agents that run in parallel.”
   • [community] “This honestly makes me think less of Cline. They're wrong about this [not indexing codebase] and it seems like they're trying to do damage c…”
   • [community] “Cline is the most impressive agentic coder tool I've used and it seems to be getting better. I can plan with it for 10-15 minutes, set it lo…”

   proof ↗⚑ flag

Context management

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

   weight 2 · round drawn
   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

   Cline—none0/10

   The evidence pack shows conversation continuity only within a session when switching Plan/Act modes (cline-docs-40), but no documented feature for automatically building and recalling memory across separate sessions (e.g., a memory bank, persistent context store, or session-recall mechanism). Skills, subagents, and scheduling features are unrelated to automatic cross-session memory.

   • [claimed-docs] “The conversation history carries over when you switch modes. Cline remembers everything you discussed in Plan mode, so you don't need to rep…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Cline—none0/10

   No evidence describes Cline supporting multiple project directories or multi-root workspaces within a single session; evidence only mentions running agent sessions 'in any folder' (singular) and per-card worktrees for parallel agents, not combined multi-directory context.

   • [github] “Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP servers.”
   • [github] “Cline as a native app for macOS and Windows. Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP server…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   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

   Cline~partialclaimed3/10

   The evidence only mentions 'Skills' as modular instruction sets that extend Cline's capabilities for specific tasks, which is tangential to a dedicated project-wide instructions/coding-standards file rather than a clear equivalent of a rules file. Missing for 10: explicit documentation of a project-level instructions/rules file (e.g. a .clinerules-style config), guidance on setting coding standards/conventions, and any community corroboration of this specific feature.

   • [claimed-docs] “Skills are modular instruction sets that extend Cline's capabilities for specific tasks.”

   proof ↗⚑ flag

Issue diagnosis

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

   weight 3 · round to Cline
   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

   Cline~partialcommunity7/10

   Cline can execute terminal commands and react live to test/dev-server output (cline-docs-14), run test-fix loops via CLI (cline-docs-33), review diffs (cline-docs-34, cline-gh-1), use Plan mode to explore/narrow root causes via codebase search (cline-docs-39), and spawn subagents for independent codebase investigation (cline-docs-25). Checkpoints/undo support verifying and rolling back fixes (cline-docs-30), and community feedback confirms it can autonomously produce correct diffs after exploration (cline-comm-3). Missing for 10: no explicit debugging-specific tooling (e.g., breakpoints/log tracing) or independent hands-on case studies specifically about root-cause diagnosis and fix verification workflows.

   • [claimed-docs] “Executes in your terminal and reacts to output as it appears. Long-running dev servers, tests, deploys, all handled live.”
   • [claimed-docs] “cline --auto-approve true "run tests and fix failures"”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [claimed-docs] “Plan mode is where you and Cline figure out what you're building and how. In this mode, Cline can read your codebase, run searches, and disc…”
   • [claimed-docs] “Subagents let Cline spawn focused research agents that run in parallel. Each subagent gets its own prompt and context window, explores the c…”
   • [claimed-docs] “Coordinated multi-file changes with linter-aware fixes, diffs, checkpoints, and one-click undo on every step.”
   • [github] “In VS Code and JetBrains, every edit shows up as a diff you can review, modify, or revert.”
   • [community] “Cline is the most impressive agentic coder tool I've used and it seems to be getting better. I can plan with it for 10-15 minutes, set it lo…”

   proof ↗⚑ flag

Marketplace

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

   weight 1 · round to Cline
   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

   Cline✓fullclaimed8/10

   Cline has a dedicated Skills feature: modular instruction sets that package guidance, processes, and optional resources, loaded only when relevant to the task, explicitly designed to extend Cline's capabilities for specialized tasks. This is directly documented first-party functionality matching the story, though independent/hands-on corroboration is absent. Missing for 10: independent or community validation of skill authoring/usage, and details on a skills marketplace/sharing ecosystem.

   • [claimed-docs] “Skills are modular instruction sets that extend Cline's capabilities for specific tasks.”
   • [claimed-docs] “Skills are modular instruction sets that extend Cline's capabilities for specific tasks. Each skill packages detailed guidance, processes, a…”

   proof ↗⚑ flag

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

   weight 1 · round to Cursor
   Cursor✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   Cline~partialclaimed5/10

   Cline supports MCP servers for external tool/data integration and ACP so third-party clients (editors, tools) can embed Cline as an agent, plus chat integrations (Slack, Discord, Telegram, Linear) and CI/CD pipeline embedding — all evidence of ecosystem interoperability. However there's no explicit evidence of a marketplace or catalog of partner-built 'agent apps' that can be dropped into Cline workflows the way MCP tools can. Missing for 10: a documented partner/agent marketplace, third-party agent app examples, and independent verification of such integrations working end-to-end.

   • [claimed-docs] “MCP (Model Context Protocol) lets Cline use external tools and data sources through MCP servers.”
   • [claimed-docs] “Any ACP-capable client can use Cline as its coding agent without a dedicated extension — the same agent you use in the terminal, embedded in…”
   • [claimed-docs] “Chat with the agent from Slack, Discord, Telegram, or Linear. Run it headlessly inside GitHub Actions, GitLab, or any pipeline.”
   • [github] “Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP servers.”

   proof ↗⚑ flag

Team knowledge

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

   weight 1 · round drawn
   Cursor—none0/10

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

   ⚑ flag

   Cline—none0/10

   Cline's evidence covers a Kanban task board for running parallel agents with worktrees, MCP integrations, and skills/instructions, but none of this describes ingesting team docs and repos into a shared knowledge workspace or source-of-truth repository for engineering leads. Missing for 10: any feature for indexing/aggregating documentation and codebases into a shared, queryable team knowledge base, evidence of team-wide onboarding or knowledge-sharing workspace, and any first-party or community mention of such a capability.

   • [claimed-docs] “Run many agents in parallel from a web-based task board with per-card worktrees, auto-commit, and dependency chains.”
   • [claimed-docs] “Use Cline Kanban to run multiple coding agents in parallel with isolated git worktrees.”
   • [claimed-docs] “Review diffs in card detail view and leave inline comments.”
   • [claimed-docs] “MCP (Model Context Protocol) lets Cline use external tools and data sources through MCP servers.”

   proof ↗⚑ flag

Tool integration

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

   weight 3 · round to Cursor
   Cursor✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Cline~partialclaimed6/10

   Cline explicitly supports chatting with the agent from Slack (and Discord/Telegram/Linear) and documents MCP as the general mechanism for connecting external tools and data sources, which is how community MCP servers for Jira, Google Drive, etc. are typically wired in. However, there's no direct evidence of a first-party Jira or Google Drive integration or MCP server. Missing for 10: explicit Jira integration evidence, explicit Google Drive integration evidence, and confirmation these connect specifically for context-extension use cases beyond chat.

   • [claimed-docs] “Chat with the agent from Slack, Discord, Telegram, or Linear. Run it headlessly inside GitHub Actions, GitLab, or any pipeline.”
   • [claimed-docs] “MCP (Model Context Protocol) lets Cline use external tools and data sources through MCP servers.”
   • [github] “Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP servers.”

   proof ↗⚑ flag

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

   weight 2 · round to Cursor
   Cursor~partialclaimed7/10

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

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

   proof ↗⚑ flag

   Cline~partialclaimed6/10

   cline-docs-17 explicitly claims chat/task-kickoff via Slack, Discord, Telegram, Linear, and headless runs in GitHub Actions/GitLab pipelines, directly matching the story. However this is a single marketing-page mention with no deeper docs on setup, no independent/hands-on corroboration, and no GitHub-specific (issue/PR trigger) integration details beyond CI headless mode. Missing for 10: independent verification, per-platform setup documentation, and confirmation of native GitHub issue/PR-triggered task kickoff.

   • [claimed-docs] “Chat with the agent from Slack, Discord, Telegram, or Linear. Run it headlessly inside GitHub Actions, GitLab, or any pipeline.”

   proof ↗⚑ flag

Cross device continuity

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

   weight 2 · round drawn
   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

   Cline~partialclaimed5/10

   Cline's Kanban (web-based task board) and CLI with cron-scheduled agents that persist across restarts suggest tasks can be started and later resumed independently of a single device/session, and Cline works across many IDEs/editors so a task's environment isn't tied to one editor. However there is no explicit documentation of cross-device session handoff or browser-based continuation of a specific in-progress task (e.g., syncing an active conversation/task state to a different machine or web UI). missing for 10: explicit cross-device task/session sync or handoff mechanism, browser-based resumption of an existing task, and independent/community confirmation of this specific workflow.

   • [claimed-docs] “Run many agents in parallel from a web-based task board with per-card worktrees, auto-commit, and dependency chains.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [claimed-docs] “Use Cline Kanban to run multiple coding agents in parallel with isolated git worktrees.”
   • [claimed-docs] “Cline works across all major editors: **VS Code**, **Cursor**, **Windsurf**, **JetBrains** (IntelliJ, PyCharm, WebStorm), **Antigravity**, a…”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub.”

   proof ↗⚑ flag

Ide integration

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

   weight 1 · round to Cline
   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

   Cline~partialclaimed6/10

   Cline explicitly supports JetBrains IDEs and documents that edits in JetBrains show up as reviewable/revertable diffs (cline-gh-1, cline-docs-6, cline-docs-28), covering the interactive diff part of the story. However, there is no explicit documentation of a 'share selected code as context' feature specifically for the JetBrains plugin (only general chat/context usage is implied), so the second half of the story is unevidenced. Missing for 10: explicit JetBrains-specific documentation or screenshots of selecting code and adding it as context, independent/hands-on confirmation of this specific workflow in JetBrains.

   • [github] “In VS Code and JetBrains, every edit shows up as a diff you can review, modify, or revert.”
   • [claimed-docs] “The same Cline experience in IntelliJ IDEA, PyCharm, WebStorm, GoLand, and the rest of the JetBrains family.”
   • [claimed-docs] “Cline works across all major editors: **VS Code**, **Cursor**, **Windsurf**, **JetBrains** (IntelliJ, PyCharm, WebStorm), **Antigravity**, a…”
   • [claimed-docs] “IDE Extension — VS Code, Cursor, JetBrains, Windsurf, VSCodium, Antigravity”

   proof ↗⚑ flag

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

   weight 3 · round to Cline
   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

   Cline✓fullcommunity9/10

   Cline is documented as an AI coding assistant embedded directly in VS Code, JetBrains IDEs, Cursor, Windsurf, and other editors, providing conversational chat with contextual codebase access, file/command actions, and inline diff review (cline-docs-1, cline-docs-6, cline-docs-28, cline-docs-31, cline-gh-1). Community reports from daily users corroborate effective in-IDE agentic chat experience (cline-comm-1, cline-comm-3, cline-comm-7, cline-comm-10). Missing for 10: independent third-party UX review specifically of the chat panel interface itself (most evidence is vendor docs).

   • [claimed-docs] “AI coding assistant in your editor. Create files, run commands, browse the web, and use tools with human-in-the-loop approval.”
   • [claimed-docs] “The same Cline experience in IntelliJ IDEA, PyCharm, WebStorm, GoLand, and the rest of the JetBrains family.”
   • [claimed-docs] “Cline works across all major editors: **VS Code**, **Cursor**, **Windsurf**, **JetBrains** (IntelliJ, PyCharm, WebStorm), **Antigravity**, a…”
   • [claimed-docs] “It can read and write files, run terminal commands, use a browser, and help you build features through natural conversation. Every action re…”
   • [github] “In VS Code and JetBrains, every edit shows up as a diff you can review, modify, or revert.”
   • [community] “Cline is, hands down, the most effective agentic coding tool out there. I've extensively daily driven any one of them you can name, and ther…”
   • [community] “Cline is the most impressive agentic coder tool I've used and it seems to be getting better. I can plan with it for 10-15 minutes, set it lo…”
   • [community] “This is the golden tool that doesn't get the hype. Hope they can keep delivering. It seems to hit my personal sweet spot.”
   • [community] “I can have cline control a terminal command, it's by no means limited to editing code... I find Cline better [than Claude Code] (plus I can …”

   proof ↗⚑ flag

Session management

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

   weight 2 · round to Cline
   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

   Cline✓fullclaimed8/10

   Cline ships a native desktop app (macOS/Windows) with a Kanban-style task board that runs multiple agent sessions in parallel with isolated git worktrees, and supports diff review with inline comments in card detail view; VS Code/JetBrains editors also show diffs for review, modify, or revert. missing for 10: no independent/hands-on review specifically confirming the desktop Kanban diff-review UX (community evidence covers IDE extension use, not the desktop app directly), and no detail on running truly side-by-side sessions within a single app window versus per-card views.

   • [claimed-docs] “Run many agents in parallel from a web-based task board with per-card worktrees, auto-commit, and dependency chains.”
   • [claimed-docs] “Use Cline Kanban to run multiple coding agents in parallel with isolated git worktrees.”
   • [claimed-docs] “Review diffs in card detail view and leave inline comments.”
   • [github] “Cline as a native app for macOS and Windows. Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP server…”
   • [github] “In VS Code and JetBrains, every edit shows up as a diff you can review, modify, or revert.”
   • [github] “Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP servers.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Cline✓fullclaimed7/10

   Cline Kanban is explicitly documented as a web-based task board for running many agents in parallel with per-card isolated git worktrees, auto-commit, dependency chains, and inline diff review—directly matching the engineering-lead's need to manage multiple agent-driven sessions from one unified workspace. This is reinforced by CLI scheduling (cron-based agents persisting independently) and subagents that run in parallel with their own context windows. Missing for 10: independent/hands-on community corroboration specifically of the Kanban multi-session workspace (community evidence only covers single-agent coding quality, not the Kanban feature), and no evidence on scaling limits or team-collaboration aspects of the shared workspace.

   • [claimed-docs] “Run many agents in parallel from a web-based task board with per-card worktrees, auto-commit, and dependency chains.”
   • [claimed-docs] “Use Cline Kanban to run multiple coding agents in parallel with isolated git worktrees.”
   • [claimed-docs] “Review diffs in card detail view and leave inline comments.”
   • [github] “Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP servers.”
   • [github] “Cline as a native app for macOS and Windows. Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP server…”
   • [claimed-docs] “Subagents let Cline spawn focused research agents that run in parallel.”
   • [claimed-docs] “Subagents let Cline spawn focused research agents that run in parallel. Each subagent gets its own prompt and context window, explores the c…”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [claimed-docs] “Run agents on cron schedules for recurring automations like daily summaries and code reviews.”

   proof ↗⚑ flag

Terminal workflow

1. developerRun a coding agent locally from my terminal

   weight 3 · round to Cline
   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

   Cline✓fullcommunity9/10

   Cline ships a dedicated CLI (npm install -g cline) supporting interactive terminal chat, headless automation, auto-approve flags, and live reaction to terminal output, well documented with concrete command examples and corroborated by community usage reports of terminal-based control. missing for 10: independent hands-on verification of the standalone CLI specifically (community evidence mostly covers the IDE extension, not the terminal CLI tool).

   • [claimed-docs] “Run Cline in your terminal with interactive chat or fully headless automation for CI/CD and scripting.”
   • [claimed-docs] “Use headless mode for scripts/automation and processable output.”
   • [claimed-docs] “Autonomous execution can modify files and run commands without further prompts.”
   • [claimed-docs] “Executes in your terminal and reacts to output as it appears. Long-running dev servers, tests, deploys, all handled live.”
   • [claimed-docs] “npm install -g cline”
   • [claimed-docs] “Use Cline CLI for interactive terminal sessions and automated headless workflows.”
   • [claimed-docs] “cline --auto-approve true "run tests and fix failures"”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [community] “I can have cline control a terminal command, it's by no means limited to editing code... I find Cline better [than Claude Code] (plus I can …”

   proof ↗⚑ flag

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

   weight 2 · round to Cline
   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

   Cline✓fullclaimed9/10

   Cline ships a documented CLI with explicit headless/non-interactive mode for scripts and CI/CD, auto-approve flags for unattended execution, pipeable I/O, and cron scheduling for recurring automations, plus explicit examples of running headlessly in GitHub Actions/GitLab pipelines. Missing for 10: independent (non-vendor) hands-on confirmation of headless CI usage specifically.

   • [claimed-docs] “Run Cline in your terminal with interactive chat or fully headless automation for CI/CD and scripting.”
   • [claimed-docs] “Use headless mode for scripts/automation and processable output.”
   • [claimed-docs] “Autonomous execution can modify files and run commands without further prompts.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub.”
   • [claimed-docs] “Chat with the agent from Slack, Discord, Telegram, or Linear. Run it headlessly inside GitHub Actions, GitLab, or any pipeline.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [claimed-docs] “cline --auto-approve true "run tests and fix failures"”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [claimed-docs] “Run agents on cron schedules for recurring automations like daily summaries and code reviews.”

   proof ↗⚑ flag

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

   weight 2 · round to Cline
   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

   Cline~partialprobed6/10

   Cline ships a full-featured CLI/headless mode (scripting, auto-approve, cron scheduling, ACP integration) that covers much of what the UI does, and docs emphasize scriptable automation for CI/CD. However, there is no documented REST/OpenAPI surface (probe found only 404s for openapi endpoints), and some UI-only features like the Kanban board's diff review/inline comments aren't shown to have CLI equivalents, so full UI/API parity isn't confirmed. missing for 10: a formal API/OpenAPI spec, explicit parity between Kanban UI actions (diff review, inline comments) and CLI/API, independent confirmation of complete feature equivalence.

   • [claimed-docs] “Use headless mode for scripts/automation and processable output.”
   • [claimed-docs] “Autonomous execution can modify files and run commands without further prompts.”
   • [claimed-docs] “Use Cline CLI for interactive terminal sessions and automated headless workflows.”
   • [claimed-docs] “cline --auto-approve true "run tests and fix failures"”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub.”
   • [claimed-docs] “The CLI supports running agents on cron schedules through the hub. Scheduled agents persist across process restarts and run independently of…”
   • [claimed-docs] “Run agents on cron schedules for recurring automations like daily summaries and code reviews.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cline.bot/openapi.json, https://docs.cline.bot/swagger.json, https://docs.cline.bot/api…”
   • [claimed-docs] “Use Cline Kanban to run multiple coding agents in parallel with isolated git worktrees.”
   • [claimed-docs] “Review diffs in card detail view and leave inline comments.”

   proof ↗⚑ flag

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

   weight 3 · round to Cline
   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

   Cline~partialclaimed4/10

   Cline documents that users are 'never locked into our platform or pricing' and can 'switch providers or self-host anytime' (cline-docs-15), plus BYOK/local-model support (cline-docs-27, cline-docs-41, cline-docs-42), which speaks to avoiding lock-in but is not the same as a documented data-export feature. There is no evidence of an explicit export function for task history, conversations, or configs in open formats. missing for 10: explicit data-export/backup feature, documentation of file formats used for stored history, independent confirmation of a 'leave with your data' workflow.

   • [claimed-docs] “You're never locked into our platform or pricing. Switch providers or self-host anytime.”
   • [claimed-docs] “Absolutely! You can bring your own API keys from providers like OpenAI, Anthropic, Google, and others.”
   • [claimed-docs] “Run Cline with local models using Ollama, LM Studio or Atomic Chat.”
   • [claimed-docs] “Bring Your Own Key (BYOK): use your own provider credentials (cloud or local runtimes).”

   proof ↗⚑ flag

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

   weight 2 · round to Cline
   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

   Cline~partialclaimed5/10

   The evidence confirms Cline's source code is hosted publicly on GitHub (cline/cline), which is strong circumstantial evidence of open availability, but none of the cited items state or link to an explicit open-source license (e.g., Apache/MIT) or licensing terms. missing for 10: explicit license text/citation, confirmation of license type, any docs page addressing licensing.

   • [github] “In VS Code and JetBrains, every edit shows up as a diff you can review, modify, or revert.”
   • [github] “Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP servers.”
   • [github] “Cline as a native app for macOS and Windows. Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP server…”

   proof ↗⚑ flag

Authentication

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

   weight 2 · round to Cline
   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

   Cline✓fullclaimed8/10

   Docs explicitly support BYOK (bring your own API key from OpenAI, Anthropic, Google, local runtimes) as an alternative to signing in with a Cline account for credits, and pricing page confirms users are never locked into platform login/pricing and can switch providers or self-host. Missing for 10: independent/hands-on confirmation of API-key-only auth flow and details on any limitations when skipping account login.

   • [claimed-docs] “Absolutely! You can bring your own API keys from providers like OpenAI, Anthropic, Google, and others.”
   • [claimed-docs] “Bring Your Own Key (BYOK): use your own provider credentials (cloud or local runtimes).”
   • [claimed-docs] “You're never locked into our platform or pricing. Switch providers or self-host anytime.”
   • [claimed-docs] “Instead of managing separate API keys across multiple vendors, you sign in once, add Cline credits, and select from available models directl…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Cline—none0/10

   No evidence of SSO/SAML/OIDC enterprise identity integration, or cloud platform (AWS/Azure/GCP) IAM authentication; evidence only covers BYOK API keys, Cline account sign-in for credits, and local model auth. Missing for 10: SSO/SAML/OIDC support, enterprise directory integration, cloud IAM role-based auth, admin/team provisioning for compliance.

   • [claimed-docs] “Bring Your Own Key (BYOK): use your own provider credentials (cloud or local runtimes).”
   • [claimed-docs] “Instead of managing separate API keys across multiple vendors, you sign in once, add Cline credits, and select from available models directl…”
   • [claimed-docs] “Absolutely! You can bring your own API keys from providers like OpenAI, Anthropic, Google, and others.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Cline—none0/10

   Cline's docs describe BYOK (bring-your-own API key), its own Cline account/credits system, and the ClinePass subscription, but there is no evidence of signing in with an existing third-party subscription (e.g., a Claude Pro/ChatGPT Plus plan) to authenticate and use the agent's entitlements.

   • [claimed-docs] “Bring Your Own Key (BYOK): use your own provider credentials (cloud or local runtimes).”
   • [claimed-docs] “Instead of managing separate API keys across multiple vendors, you sign in once, add Cline credits, and select from available models directl…”
   • [claimed-docs] “ClinePass is a low-cost monthly subscription — $9.99/month — that offers 2-5x the usage on popular open coding models compared to standard A…”

   proof ↗⚑ flag

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

   weight 1 · round to Cline
   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

   Cline~partialclaimed6/10

   Cline lets you sign in once and use Cline's account system instead of juggling per-provider API keys (cline-docs-43), and it periodically offers free model promotions with a limited usage quota without requiring your own key (cline-docs-45). However, the primary account-based path is credit-based (ClinePass at $9.99/mo or pay-as-you-go credits, cline-docs-44), so 'free-tier access' is only a limited promotional feature, not a durable no-cost tier. Missing for 10: independent confirmation of the free-tier's usage limits/duration, and clearer positioning of free access vs. paid credits as the default sign-in experience.

   • [claimed-docs] “Instead of managing separate API keys across multiple vendors, you sign in once, add Cline credits, and select from available models directl…”
   • [claimed-docs] “Cline periodically offers free model promotions that let you try select models at no cost, up to a limited usage quota.”
   • [claimed-docs] “ClinePass is a low-cost monthly subscription — $9.99/month — that offers 2-5x the usage on popular open coding models compared to standard A…”
   • [claimed-docs] “Absolutely! You can bring your own API keys from providers like OpenAI, Anthropic, Google, and others.”

   proof ↗⚑ flag

Model choice

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

   weight 1 · round drawn
   Cursor—none0/10

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

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

   proof ↗⚑ flag

   Cline—none0/10

   Cline documents manual model configuration (separate models for Plan/Act, BYOK, ClinePass, free model promotions) but there is no evidence of an automatic 'best model for the task' selection or routing engine choosing models on the user's behalf.

   • [claimed-docs] “You can configure separate models for Plan and Act modes.”
   • [claimed-docs] “Absolutely! You can bring your own API keys from providers like OpenAI, Anthropic, Google, and others.”
   • [claimed-docs] “Bring Your Own Key (BYOK): use your own provider credentials (cloud or local runtimes).”
   • [claimed-docs] “Instead of managing separate API keys across multiple vendors, you sign in once, add Cline credits, and select from available models directl…”
   • [claimed-docs] “ClinePass is a low-cost monthly subscription — $9.99/month — that offers 2-5x the usage on popular open coding models compared to standard A…”

   proof ↗⚑ flag

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

   weight 2 · round to Cline
   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

   Cline✓fullcommunity9/10

   Cline explicitly supports multi-provider model choice: BYOK for OpenAI, Anthropic, Google and others, local models via Ollama/LM Studio, separate model selection per Plan/Act mode, a unified Cline provider to switch between hosted models, and explicit messaging that users are never locked into one provider/pricing. Community evidence corroborates local model (Ollama) and Gemini usage alongside Anthropic. Missing for 10: no independent benchmark of full provider parity/quality across all providers.

   • [claimed-docs] “Absolutely! You can bring your own API keys from providers like OpenAI, Anthropic, Google, and others.”
   • [claimed-docs] “Run Cline with local models using Ollama, LM Studio or Atomic Chat.”
   • [claimed-docs] “Bring Your Own Key (BYOK): use your own provider credentials (cloud or local runtimes).”
   • [claimed-docs] “Instead of managing separate API keys across multiple vendors, you sign in once, add Cline credits, and select from available models directl…”
   • [claimed-docs] “You can configure separate models for Plan and Act modes.”
   • [claimed-docs] “You're never locked into our platform or pricing. Switch providers or self-host anytime.”
   • [community] “I like cline... I was particularly surprised that it worked pretty well with local models... local model support is hit and miss [in other t…”
   • [community] “I can have cline control a terminal command, it's by no means limited to editing code... I find Cline better [than Claude Code] (plus I can …”
   • [community] “Cline also supposedly supports Ollama but it doesn't work that well with most models. There are some models dedicated to cline.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Cursor—none0/10

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

   ⚑ flag

   Cline—none0/10

   The evidence describes BYOK, local model support (Ollama/LM Studio), and 'self-host anytime' claims, but nothing addresses explicit region/data-residency selection for where data is stored (e.g., choosing EU vs US storage for Cline's own cloud/credits service). This is a fair axis for an AI-native privacy-conscious user but no evidence shows such a control exists.

   • [claimed-docs] “You're never locked into our platform or pricing. Switch providers or self-host anytime.”
   • [claimed-docs] “Run Cline with local models using Ollama, LM Studio or Atomic Chat.”
   • [claimed-docs] “Bring Your Own Key (BYOK): use your own provider credentials (cloud or local runtimes).”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Cursor—none0/10

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

   ⚑ flag

   Cline—none0/10

   No evidence in the pack addresses data usage for AI model training, opt-out policies, zero-retention agreements, or any privacy/data-training controls for Cline. BYOK and self-hosting options (cline-docs-15, cline-docs-27, cline-docs-42) relate to provider flexibility, not to preventing training on user data.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Cursor—none0/10

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

   ⚑ flag

   Cline—none0/10

   The evidence pack covers BYOK, local model support, and self-hosting options, but contains no mention of data retention policies, conversation/history deletion controls, or telemetry opt-out mechanisms that would let a user control what data is retained or deleted.

   ⚑ flag

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

   weight 2 · round drawn
   Cursor—none0/10

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

   ⚑ flag

   Cline—none0/10

   No evidence in the pack mentions telemetry, usage tracking, analytics collection, or an opt-out/privacy setting for Cline; the docs cover BYOK, local models, and provider choice but not telemetry controls.

   ⚑ flag

Data governance

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

   weight 1 · round drawn
   Cursor—none0/10

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

   ⚑ flag

   Cline—none0/10

   No evidence in the pack addresses data-retention or training-opt-out policies for code/prompts; while BYOK and self-host options are mentioned, none speak to model-training usage or an opt-out control.

   ⚑ flag

Pr review

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

   weight 3 · round to Cline
   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

   Cline~partialclaimed5/10

   Cline can execute arbitrary terminal commands (including git operations) with human-in-the-loop or auto-approve, and Kanban explicitly mentions 'auto-commit' across worktrees, implying it stages and commits changes as part of its workflow. However, there's no explicit documentation of Cline authoring commit messages, creating branches, or opening pull requests as first-class features—this would rely on generic shell/terminal execution rather than a dedicated git/PR workflow. Missing for 10: explicit commit-message generation, branch creation, and PR-opening capability (e.g., via GitHub CLI integration) documented as a feature, plus independent evidence of it doing so successfully.

   • [claimed-docs] “Run many agents in parallel from a web-based task board with per-card worktrees, auto-commit, and dependency chains.”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [claimed-docs] “Executes in your terminal and reacts to output as it appears. Long-running dev servers, tests, deploys, all handled live.”
   • [github] “In VS Code and JetBrains, every edit shows up as a diff you can review, modify, or revert.”
   • [claimed-docs] “Coordinated multi-file changes with linter-aware fixes, diffs, checkpoints, and one-click undo on every step.”

   proof ↗⚑ flag

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

   weight 3 · round to Cursor
   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

   Cline~partialclaimed4/10

   Cline can be scripted to review diffs (`git diff | cline "review these changes"`) and run headlessly inside GitHub Actions/GitLab pipelines or on cron schedules for 'recurring automations like...code reviews,' so a review workflow could be built. However there's no evidence of a dedicated PR-triggered bot/GitHub App that automatically posts contextual review comments on every pull request out of the box — it's a general agent that must be manually wired into CI. Missing for 10: a first-party PR-trigger integration (e.g., GitHub App/bot), evidence of automatic invocation on PR open/update, and evidence of posting inline contextual comments on PRs themselves.

   • [claimed-docs] “Chat with the agent from Slack, Discord, Telegram, or Linear. Run it headlessly inside GitHub Actions, GitLab, or any pipeline.”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [claimed-docs] “Run agents on cron schedules for recurring automations like daily summaries and code reviews.”
   • [claimed-docs] “Use headless mode for scripts/automation and processable output.”

   proof ↗⚑ flag

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

   weight 3 · round to Cline
   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

   Cline✓fullclaimed8/10

   Cline shows every edit as a reviewable diff with modify/revert and one-click undo (cline-gh-1, cline-docs-30), supports piping diffs for review ('git diff | cline "review these changes"', cline-docs-34), can run tests/checks and auto-fix failures (cline-docs-33), and Kanban mode offers diff review with inline comments (cline-docs-47) — together covering diff inspection plus pre-merge checks. Missing for 10: independent/hands-on corroboration specifically validating the diff-review or check-running workflow (community evidence is general praise, not focused on this axis).

   • [github] “In VS Code and JetBrains, every edit shows up as a diff you can review, modify, or revert.”
   • [claimed-docs] “Coordinated multi-file changes with linter-aware fixes, diffs, checkpoints, and one-click undo on every step.”
   • [claimed-docs] “git diff | cline "review these changes"”
   • [claimed-docs] “cline --auto-approve true "run tests and fix failures"”
   • [claimed-docs] “Review diffs in card detail view and leave inline comments.”

   proof ↗⚑ flag

Safe execution

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

   weight 2 · round to Cursor
   Cursor✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Cline~partialclaimed7/10

   Cline documents granular Auto Approve settings that let users decide which actions (file edits, terminal commands, browser actions, MCP tools) require approval versus running automatically, and MCP server configuration lets you add/remove which external tool integrations are available at all [cline-docs-21],[cline-docs-22],[cline-docs-38],[cline-docs-16],[cline-gh-2]. This gives meaningful control over tool/integration access, but evidence is all individual-developer-level settings with no organization-wide policy enforcement, role-based restriction, or admin console for an engineering-lead to mandate controls across a team. Missing for 10: team/org-level policy enforcement, audit logging of tool access decisions, and independent verification that these controls hold up in practice.

   • [claimed-docs] “Auto Approve lets you decide which actions Cline can take without prompting you each time.”
   • [claimed-docs] “YOLO mode is Auto Approve on steroids. Check the box and Cline auto-approves everything: file changes, terminal commands, browser actions, M…”
   • [claimed-docs] “Auto Approve lets you decide which actions Cline can take without prompting you each time. It keeps you out of approval popups during routin…”
   • [claimed-docs] “MCP (Model Context Protocol) lets Cline use external tools and data sources through MCP servers.”
   • [github] “Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP servers.”
   • [claimed-docs] “Use Cline Kanban to run multiple coding agents in parallel with isolated git worktrees.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Cursor—none0/10

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

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

   proof ↗⚑ flag

   Cline—none0/10

   Cline's safety model is built around human-in-the-loop approval, diff review, checkpoints, and auto-approve settings (cline-docs-1, cline-docs-21, cline-docs-30), not sandboxed execution of code/tools/network. Kanban worktrees provide git isolation for parallel agents (cline-docs-24) but this is not a sandbox for code/tool/network execution. No evidence of containerized, VM-based, or otherwise isolated runtime environment for agent actions.

   • [claimed-docs] “Auto Approve lets you decide which actions Cline can take without prompting you each time.”
   • [claimed-docs] “Coordinated multi-file changes with linter-aware fixes, diffs, checkpoints, and one-click undo on every step.”
   • [claimed-docs] “Use Cline Kanban to run multiple coding agents in parallel with isolated git worktrees.”
   • [claimed-docs] “Auto Approve lets you decide which actions Cline can take without prompting you each time. It keeps you out of approval popups during routin…”

   proof ↗⚑ flag

Security checks

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

   weight 1 · round drawn
   Cursor—none0/10

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

   ⚑ flag

   Cline—none0/10

   No evidence anywhere in the pack of license detection, public-code/plagiarism matching, or provenance references for AI-suggested code; Cline's review features focus on diffs, checkpoints, and human approval, not license/originality attribution.

   ⚑ flag

2. developerGet contextual explanations and automatic fixes for security vulnerabilities

   weight 2 · round drawn
   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

   Cline—none0/10

   Cline's evidence shows general-purpose code editing, diff review, and command execution (e.g., 'git diff | cline review these changes'), but no dedicated feature for detecting, explaining, or auto-fixing security vulnerabilities (no SAST/CVE integration, security linting, or vulnerability-specific workflow is documented).

   ⚑ flag