Cursor Bugbot vs cubic

Agent access

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

   weight 2 · round to cubic
   Cursor Bugbot✓fullprobed8/10

   Cursor publishes a working llms.txt index (HTTP 200) and provides machine-readable .md versions of its docs (e.g., docs/bugbot.md), directly enabling an agent to be pointed at agent-oriented documentation. Missing for 10: no evidence of llms-full.txt or explicit guidance encouraging agents to consume these docs, and no independent report of an agent successfully using this format end-to-end.

   • [probe] “PROBE llms.txt: HTTP 200 at https://cursor.com/llms.txt # Cursor Documentation ## Get Started - https://cursor.com/docs.md - https://curso…”
   • [probe] “PROBE docs-md: HTTP 200 at https://cursor.com/docs/bugbot.md # Bugbot Bugbot reviews pull requests and identifies bugs, security issues, an…”

   proof ↗⚑ flag

   cubic✓fullprobed9/10

   cubic hosts a live llms.txt (HTTP 200) and .md-suffixed agent-friendly docs pages that link back to the llms.txt index, confirming an agent can be pointed at these docs and navigate them. missing for 10: no independent/community confirmation of an agent actually consuming llms.txt successfully in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.cubic.dev/llms.txt # cubic documentation > cubic reviews code on GitHub and in local coding workfl…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.cubic.dev/ai-review/introduction.md > ## Documentation Index > Fetch the complete documentation inde…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Cursor Bugbot~partialclaimed6/10

   Bugbot runs automatically on every PR update across GitHub, GitLab, Bitbucket, and Azure DevOps without manual invocation, which is inherently headless/automated behavior, and can also be triggered by PR comments (a CI-like trigger). However, there's no documented standalone CLI, API, or explicit 'run in CI pipeline' mode independent of git-host PR events. Missing for 10: a documented CLI/API for invoking Bugbot outside PR webhooks, evidence of arbitrary CI pipeline integration (e.g. as a build step), and independent confirmation of headless automation reliability.

   • [claimed-docs] “Runs automatic reviews on every PR update”
   • [claimed-docs] “Manual trigger by commenting `cursor review` or `bugbot run` on any PR”
   • [claimed-docs] “GitHub (including GitHub Enterprise Server): See the GitHub integration page”
   • [claimed-docs] “GitLab (including GitLab Self-Hosted): See the GitLab integration page”
   • [claimed-docs] “Cloud Agents clone your code, work on branches, and open pull requests. Bugbot reviews pull requests and posts its findings as comments.”
   • [claimed-docs] “It analyzes every pull request for bugs, security vulnerabilities, and code quality issues, leaving inline comments with explanations and su…”

   proof ↗⚑ flag

   cubic~partialprobed6/10

   cubic's core review flow is already headless — it auto-reviews PRs on open with no manual step (cubic-docs-1, cubic-docs-47), and the cubic CLI can review local changes before a push (cubic-docs-7, cubic-probe-5), which is plausible to script into CI. However there is no explicit documentation of a CI/pipeline integration mode, exit codes for pass/fail gating, or GitHub Actions/other CI examples. Missing for 10: explicit CI pipeline integration docs, non-interactive/exit-code behavior for automation gating, and independent confirmation of CLI use in CI.

   • [claimed-docs] “Once installed, cubic automatically reviews new pull requests.”
   • [claimed-docs] “The **cubic CLI** reviews local changes before you push. It finds bugs and generates a prompt that your coding agent can use to fix them.”
   • [probe] “official CLI documented at https://docs.cubic.dev/ide/cli-review”
   • [claimed-docs] “The AI automatically scans every pull request for a wide range of issues, including logic errors, style inconsistencies, and potential secur…”
   • [claimed-docs] “Codebase scans deploy thousands of AI agents to find bugs and vulnerabilities across your repository.”

   proof ↗⚑ flag

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

   weight 3 · round to cubic
   Cursor Bugbot—none0/10

   Evidence shows Bugbot is driven via PR comment triggers (`bugbot run`, `cursor review`) and VCS integrations (GitHub/GitLab/Bitbucket/Azure DevOps), not via any documented public REST/webhook API for programmatic control. No API reference, SDK, or endpoint documentation appears anywhere in the pack.

   • [claimed-docs] “Manual trigger by commenting `cursor review` or `bugbot run` on any PR”
   • [claimed-docs] “GitHub (including GitHub Enterprise Server): See the GitHub integration page”
   • [claimed-docs] “GitLab (including GitLab Self-Hosted): See the GitLab integration page”
   • [claimed-docs] “Connect Bitbucket Cloud repositories to Cloud Agents and Bugbot. Connect Bitbucket Data Center repositories to Bugbot.”
   • [claimed-docs] “Cloud Agents clone your code, work on branches, and open pull requests. Bugbot reviews pull requests and posts its findings as comments.”

   proof ↗⚑ flag

   cubic~partialprobed6/10

   cubic exposes some programmatic surfaces — a documented Analytics API for PR-level metrics (cubic-docs-16), an official MCP server for agents to request reviews/triage issues (cubic-docs-8, cubic-probe-4), and a CLI for local review (cubic-probe-5) — which together let an AI-native user drive parts of the product programmatically. However, a probe for a general public REST/OpenAPI spec returned 404 on all standard paths, indicating no comprehensive documented public API beyond these narrower interfaces. Missing for 10: a full OpenAPI/REST API spec covering core product actions (not just analytics), independent hands-on verification of the Analytics API and MCP server working as documented.

   • [claimed-docs] “The Analytics API gives you PR-level data on how many issues were flagged, how many were fixed, how much AI code was authored, etc.”
   • [claimed-docs] “Connect cubic's MCP server to your coding agent to read review findings and codebase context, request PR reviews, and triage PR or codebase …”
   • [probe] “official MCP server documented at https://docs.cubic.dev/ide/mcp-server”
   • [probe] “official CLI documented at https://docs.cubic.dev/ide/cli-review”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cubic.dev/openapi.json, https://docs.cubic.dev/swagger.json, https://docs.cubic.dev/api…”

   proof ↗⚑ flag

4. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Cursor Bugbot—none0/10

   No evidence anywhere in the pack of webhook subscription capability for Bugbot events; it integrates via PR comments/git provider webhooks internally but exposes no user-facing webhook subscription API.

   ⚑ flag

   cubic—none0/10

   No evidence of a webhook subscription mechanism; cubic offers an Analytics API, MCP server, and GitHub comment interactions but nothing about outbound event webhooks. OpenAPI/webhook probes returned 404s, and no docs mention webhook subscriptions.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cubic.dev/openapi.json, https://docs.cubic.dev/swagger.json, https://docs.cubic.dev/api…”
   • [claimed-docs] “The Analytics API gives you PR-level data on how many issues were flagged, how many were fixed, how much AI code was authored, etc.”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to cubic
   Cursor Bugbot✓fullcommunity8/10

   Bugbot is explicitly an AI reviewer that analyzes PR diffs to generate bug, security, and code-quality insights with inline explanations and suggested fixes, directly matching the story of AI-generated insights from the product's data. Community feedback (HN) corroborates real-world value, though some users report subtly wrong or frivolous suggestions. Missing for 10: independent benchmark of insight accuracy, and resolution of the mixed community sentiment on reliability.

   • [claimed-docs] “It analyzes every pull request for bugs, security vulnerabilities, and code quality issues, leaving inline comments with explanations and su…”
   • [claimed-docs] “Bugbot analyzes PR diffs and leaves comments with explanations and fix suggestions.”
   • [claimed-docs] “Runs automatic reviews on every PR update”
   • [community] “Do you have actual experience with bugbot? Its live in our org and is actually pretty good, almost none of its comments are frivolous or wro…”
   • [community] “I've found Bugbot to be shockingly effective at finding bugs in my PRs. Even when it's wrong, it's usually worth adding a comment, since it'…”
   • [community] “I assume that this is the same as when Cursor spontaneously decides to show code review comments in the IDE as part of some upsell? In that …”

   proof ↗⚑ flag

   cubic✓fullcommunity9/10

   cubic delivers extensive AI-generated insights: automated PR review comments flagging bugs/security issues, AI-generated PR summaries, an AI wiki that indexes the codebase into diagrams/docs, analytics dashboards (AI coding, AI review, delivery) with PR-level insight data, and issue-analysis that checks PRs against linked Jira/Linear tickets. A community reviewer corroborates the quality of these AI-generated technical explanations as more useful than generic LLM output. Missing for 10: independent large-scale benchmarking of insight accuracy beyond one HN anecdote.

   • [claimed-docs] “Spots bugs and improvements: Comments on bugs and improvements in pull requests”
   • [claimed-docs] “PR summaries: Generates PR descriptions based on code changes”
   • [claimed-docs] “cubic's AI wiki automatically indexes your codebase and produces searchable wikis, complete with links to source code, architecture diagrams…”
   • [claimed-docs] “The Analytics API gives you PR-level data on how many issues were flagged, how many were fixed, how much AI code was authored, etc.”
   • [claimed-docs] “cubic can automatically analyze your pull requests to see if they meet the requirements from your linked Linear or Jira issues.”
   • [claimed-docs] “The analytics dashboard shows how your team ships code across three lenses: AI coding usage, AI review impact, and delivery speed.”
   • [community] “I really liked it - it hit the mark. The current balance works very well, and it genuinely surprised me. It provides more technical explanat…”

   proof ↗⚑ flag

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

   weight 2 · round to cubic
   Cursor Bugbot✓fullclaimed7/10

   Bugbot autonomously reviews every PR update in the background without manual intervention, and supports organization-wide automation rules via Bugbot Automations, plus configurable effort levels and custom review guidelines (BUGBOT.md). missing for 10: no independent/hands-on evidence confirming the 'Bugbot Automations' feature's scope or reliability, and no detail on scheduling/triggers beyond PR events.

   • [claimed-docs] “Runs automatic reviews on every PR update”
   • [claimed-docs] “It analyzes every pull request for bugs, security vulnerabilities, and code quality issues, leaving inline comments with explanations and su…”
   • [claimed-docs] “Create `.cursor/BUGBOT.md` files in your repository to give Bugbot project-specific review guidelines.”
   • [claimed-docs] “Team admins can also create organization-wide rules in [Bugbot Automations](https://cursor.com/automations/from-cursor/bugbot).”
   • [claimed-docs] “With usage billing, you can now choose the effort level Bugbot uses when reviewing PRs. Users can configure Bugbot to think for longer and r…”

   proof ↗⚑ flag

   cubic✓fullclaimed8/10

   cubic automatically reviews every new PR without manual trigger, runs codebase-wide scans deploying many agents, can auto-fix issues and auto-approve PRs, and continuously learns from feedback—all happening in the background once installed, per docs-1, docs-4, docs-6, docs-12, docs-29, docs-52. This matches the story of autonomous background automation for code review workflows. Missing for 10: independent/hands-on verification that these automations run reliably unattended over time, and clearer detail on scheduling/triggers beyond PR events.

   • [claimed-docs] “Once installed, cubic automatically reviews new pull requests.”
   • [claimed-docs] “cubic generates the fix and pushes it to your PR branch.”
   • [claimed-docs] “Enable [auto-approval](/ai-review/auto-approval) to let cubic approve PRs that meet your review policy.”
   • [claimed-docs] “Codebase scans deploy thousands of AI agents to find bugs and vulnerabilities across your repository.”
   • [claimed-docs] “Enable auto-approval to let cubic approve PRs that meet your review policy.”
   • [claimed-docs] “cubic can automatically fix issues in the background. When the AI spots a problem, you can click the **Fix with cubic** button”
   • [claimed-docs] “Auto-approval lets you skip human review for pull requests that cubic determines are low risk and issue-free.”
   • [claimed-docs] “cubic automatically learns when you: Reply to its comments... React to suggestions: Thumbs up/down help cubic calibrate what's useful vs noi…”

   proof ↗⚑ flag

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

   weight 3 · round to cubic
   Cursor Bugbot~partialclaimed5/10

   Bugbot supports delegating specific tasks — manually triggering AI reviews via PR comments and delegating fixes to Cursor's Cloud Agents via 'Fix in Cursor'/'Fix in Web' links — but it is a narrow, single-purpose review/fix agent rather than a general-purpose built-in assistant you can delegate arbitrary tasks to. missing for 10: evidence of open-ended task delegation beyond PR review/fix workflows, and a conversational/general-assistant interface within Bugbot itself.

   • [claimed-docs] “Manual trigger by commenting `cursor review` or `bugbot run` on any PR”
   • [claimed-docs] “Fix in Cursor links open issues directly in Cursor”
   • [claimed-docs] “Fix in Web links open issues directly in cursor.com/agents”
   • [claimed-docs] “It analyzes every pull request for bugs, security vulnerabilities, and code quality issues, leaving inline comments with explanations and su…”
   • [claimed-docs] “Cloud Agents clone your code, work on branches, and open pull requests. Bugbot reviews pull requests and posts its findings as comments.”

   proof ↗⚑ flag

   cubic✓fullcommunity7/10

   cubic acts as a built-in AI teammate that users can direct with explicit commands (e.g. '@cubic-dev-ai review this PR', triggering ultrareview, asking it to generate and push a fix, replying for clarification, enabling auto-approval, or running codebase scans that deploy AI agents), and a community reviewer corroborates that it does more than basic checks. Missing for 10: independent/hands-on verification of these delegated actions actually completing end-to-end, and evidence of broader (non-review) task delegation beyond the code-review domain.

   • [claimed-docs] “To review a PR that was opened _before_ you installed the app, comment: `@cubic-dev-ai review this PR`.”
   • [claimed-docs] “Ultrareview runs a longer review using cubic's most capable review models, which is useful for risky migrations, security-sensitive changes,…”
   • [claimed-docs] “cubic generates the fix and pushes it to your PR branch.”
   • [claimed-docs] “Reply to a review comment to ask for clarification:”
   • [claimed-docs] “Enable [auto-approval](/ai-review/auto-approval) to let cubic approve PRs that meet your review policy.”
   • [claimed-docs] “Codebase scans deploy thousands of AI agents to find bugs and vulnerabilities across your repository.”
   • [community] “I really liked it - it hit the mark. The current balance works very well, and it genuinely surprised me. It provides more technical explanat…”

   proof ↗⚑ flag

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

   weight 2 · round to cubic
   Cursor Bugbot~partialclaimed6/10

   Bugbot can be triggered and configured via natural-language-like PR comments (e.g. `bugbot run`, `verbose=true`) and effort levels can be set via natural language instructions ('Describe in natural language when Bugbot should use low, default, or high effort'), showing some NL-driven control. However, this is limited to comment-based commands and config strings rather than full conversational/agentic natural-language operation of the tool itself. missing for 10: evidence of open-ended conversational control (e.g. chat-based instructions beyond fixed commands/effort strings), independent confirmation of NL effort-setting actually working, and broader NL command surface beyond review triggering.

   • [claimed-docs] “Manual trigger by commenting `cursor review` or `bugbot run` on any PR”
   • [claimed-docs] “Comment `bugbot run verbose=true` or `cursor review verbose=true` on the pull request. Bugbot replies with a table of the rules included in …”
   • [claimed-docs] “Describe in natural language when Bugbot should use low, default, or high effort. Cursor will dynamically set effort levels based on your in…”
   • [claimed-docs] “Smart: Describe in natural language when Bugbot should use low, default, or high effort. Cursor will dynamically set effort levels based on …”
   • [claimed-docs] “Comment `cursor review verbose=true` or `bugbot run verbose=true` on the PR for detailed logs, which Bugbot rules loaded, and a request ID”

   proof ↗⚑ flag

   cubic✓fullclaimed7/10

   cubic supports natural-language interaction: commenting `@cubic-dev-ai review this PR`, replying to review comments to ask clarification or trigger fixes, and requesting an Ultrareview, plus MCP server integration letting a coding agent issue natural-language requests (review, triage, manage subscription) on cubic's behalf. This covers command-like NL operation across PR comments and agent tooling. missing for 10: independent/hands-on verification of NL command robustness beyond documented examples, and no evidence of a broader conversational/chat interface beyond structured comment triggers.

   • [claimed-docs] “To review a PR that was opened _before_ you installed the app, comment: `@cubic-dev-ai review this PR`.”
   • [claimed-docs] “Reply to a review comment to ask for clarification:”
   • [claimed-docs] “@cubic-dev-ai review this PR”
   • [claimed-docs] “Interact with cubic in PR comments to ask questions, trigger reviews, and fix issues. You can tag `@cubic-dev-ai` directly, or reply to cubi…”
   • [claimed-docs] “Connect cubic's MCP server to your coding agent to read review findings and codebase context, request PR reviews, and triage PR or codebase …”
   • [claimed-docs] “You can now ask your coding agent to check your cubic subscription, manage team seats and roles, and purchase more seats without leaving you…”
   • [claimed-docs] “When a pull request needs extra scrutiny, you can ask cubic for an Ultrareview.”

   proof ↗⚑ flag

Ai authored

1. ai-native userThe reviewer holds the line on AI-generated PRs — it verifies agent-authored code at a volume no human team could review

   weight 2 · round to cubic
   Cursor Bugbot!disputedcontradicted6/10

   Bugbot is explicitly built to auto-review every PR at scale (docs-1, docs-13, docs-24) with configurable effort/depth for thorough review (docs-8, docs-26) and project-specific rules (docs-6) — squarely matching the 'verify AI-authored code at volume' story. However, hands-on community reports are mixed: some engineers report it catches genuine bugs reliably at scale (comm-2, comm-4), while others report it producing 'subtly wrong' comments or flip-flopping on its own fix recommendations, leading them to disable auto-review (comm-1, comm-3) — a concrete contradiction of the 'holds the line' claim in real usage. Missing for 10: independent benchmark data on bug-catch/false-positive rates at scale, and resolution of the reliability inconsistency reported by users.

   • [claimed-docs] “Runs automatic reviews on every PR update”
   • [claimed-docs] “With usage billing, you can now choose the effort level Bugbot uses when reviewing PRs. Users can configure Bugbot to think for longer and r…”
   • [claimed-docs] “It analyzes every pull request for bugs, security vulnerabilities, and code quality issues, leaving inline comments with explanations and su…”
   • [claimed-docs] “Bugbot analyzes PR diffs and leaves comments with explanations and fix suggestions.”
   • [claimed-docs] “High: Bugbot spends more time reasoning. Reviews are more expensive and take longer, but Bugbot may find more bugs.”
   • [community] “I've witnessed numerous instances where either the cursor bugbot or Claude has found a bug and recommended a reasonable fix. The fix has bee…”
   • [community] “Do you have actual experience with bugbot? Its live in our org and is actually pretty good, almost none of its comments are frivolous or wro…”
   • [community] “I assume that this is the same as when Cursor spontaneously decides to show code review comments in the IDE as part of some upsell? In that …”
   • [community] “I've found Bugbot to be shockingly effective at finding bugs in my PRs. Even when it's wrong, it's usually worth adding a comment, since it'…”

   proof ↗⚑ flag

   cubic✓fullcommunity8/10

   cubic is explicitly built to auto-review every PR, run deep Ultrareview/codebase scans deploying 'thousands of AI agents,' auto-fix and auto-approve, and surface analytics specifically tracking AI-authored code volume — directly matching the story of scaling review beyond human capacity. Community feedback (cubic-comm-1) corroborates real-world value, though cubic-comm-2 raises a substantive critique that YAML-based rules are less robust than code-based checks, a minor caveat rather than a contradiction of the core capability. Missing for 10: independent large-scale benchmark/study proving review quality holds at massive AI-PR volume, and more than two community data points.

   • [claimed-docs] “Once installed, cubic automatically reviews new pull requests.”
   • [claimed-docs] “Codebase scans deploy thousands of AI agents to find bugs and vulnerabilities across your repository.”
   • [claimed-docs] “The Analytics API gives you PR-level data on how many issues were flagged, how many were fixed, how much AI code was authored, etc.”
   • [claimed-docs] “Flex capacity keeps GitHub PR AI reviews running after your workspace uses its included reviewed-line capacity.”
   • [claimed-docs] “The AI coding tab shows how AI assistants contribute to merged pull requests in your repositories.”
   • [claimed-docs] “The AI automatically scans every pull request for a wide range of issues, including logic errors, style inconsistencies, and potential secur…”
   • [claimed-docs] “Auto-approval lets you skip human review for pull requests that cubic determines are low risk and issue-free.”
   • [community] “I really liked it - it hit the mark. The current balance works very well, and it genuinely surprised me. It provides more technical explanat…”
   • [community] “The 'in-codebase' approach is the right one, but a YAML file with plain text is a half-measure. The most reliable rule that 'lives next to t…”

   proof ↗⚑ flag

Checks

1. ai-native userI define custom agentic pre-merge checks in plain language — 'docs updated', 'tests cover new paths' — that run on every PR

   weight 2 · round to cubic
   Cursor Bugbot~partialclaimed6/10

   Bugbot lets teams define custom, natural-language review guidelines via `.cursor/BUGBOT.md` and org-wide rules via Bugbot Automations, and it runs automatically on every PR, closely matching the 'plain language custom check' idea. However, the evidence describes it purely as a commenting/review bot (posts findings, suggested fixes) rather than a pass/fail pre-merge gate tied to specific check names like 'docs updated' or 'tests cover new paths', and there's no evidence of blocking merges or exposing check results as CI status checks. Missing for 10: explicit support for named custom checks that gate/block merges, documentation of specific check definitions beyond general review guidelines, and evidence of merge-blocking behavior.

   • [claimed-docs] “Create `.cursor/BUGBOT.md` files in your repository to give Bugbot project-specific review guidelines.”
   • [claimed-docs] “Team admins can also create organization-wide rules in [Bugbot Automations](https://cursor.com/automations/from-cursor/bugbot).”
   • [claimed-docs] “Runs automatic reviews on every PR update”
   • [claimed-docs] “It analyzes every pull request for bugs, security vulnerabilities, and code quality issues, leaving inline comments with explanations and su…”
   • [claimed-docs] “Bugbot Teams includes code reviews on all PRs, analytics and reporting, effort level controls, and advanced rules and settings.”

   proof ↗⚑ flag

   cubic✓fullcommunity7/10

   cubic's 'Custom agents' feature lets teams define plain-language review rules enforcing org-specific best practices, stored in cubic.yaml, applied automatically across every PR, with a community library for adoption — directly matching the story of custom agentic pre-merge checks defined in plain language. Missing for 10: no first-party example matching the exact 'docs updated' / 'tests cover new paths' phrasing, and no independent hands-on validation of how reliably these plain-text rules enforce (one community comment raises skepticism about plain-text rule reliability vs. hard-coded checks, though this is not a concrete failure report).

   • [claimed-docs] “Custom agents are review rules that enforce your organization's specific best practices across pull requests.”
   • [claimed-docs] “Custom agents: Enforce your team's coding standards”
   • [claimed-docs] “You can also adopt existing agents from the community library with a single click.”
   • [claimed-docs] “cubic.yaml lives in the root of your repository and becomes the source of truth for AI review behavior, ignore patterns, PR descriptions, an…”
   • [claimed-docs] “`cubic.yaml` lives in the root of your repository and becomes the source of truth for AI review behavior, ignore patterns, PR descriptions, …”
   • [community] “The 'in-codebase' approach is the right one, but a YAML file with plain text is a half-measure. The most reliable rule that 'lives next to t…”

   proof ↗⚑ flag

Fixes

1. developerI turn a review finding into an applied fix — a committed patch or an agent-generated follow-up — without leaving the PR

   weight 3 · round to cubic
   Cursor Bugbot~partialcommunity6/10

   Bugbot findings include 'Fix in Cursor' and 'Fix in Web' links that launch an agent to generate the fix directly from the PR comment, and community reports confirm fixes get implemented from its suggestions (though with some friction/reverts noted). However, the docs describe these as links that open a separate Cursor/agents interface rather than an in-PR one-click apply/commit, so it's not fully 'without leaving the PR' and reliability is debated. Missing for 10: evidence of a native in-PR commit/apply button, and stronger independent confirmation that agent-generated fixes are reliably applied back to the PR without manual intervention.

   • [claimed-docs] “Fix in Cursor links open issues directly in Cursor”
   • [claimed-docs] “Fix in Web links open issues directly in cursor.com/agents”
   • [claimed-docs] “It analyzes every pull request for bugs, security vulnerabilities, and code quality issues, leaving inline comments with explanations and su…”
   • [community] “I've witnessed numerous instances where either the cursor bugbot or Claude has found a bug and recommended a reasonable fix. The fix has bee…”
   • [community] “Do you have actual experience with bugbot? Its live in our org and is actually pretty good, almost none of its comments are frivolous or wro…”

   proof ↗⚑ flag

   cubic✓fullclaimed8/10

   cubic lets developers turn review findings into applied fixes directly in the PR: it can generate a fix and push it to the PR branch, offers a one-click 'Fix with cubic' button, and its coding-agent/MCP integration lets an agent read findings and generate follow-up fixes without leaving the PR workflow. Auto-resolve threads and interactive PR comments reinforce that the fix loop stays within the PR. Missing for 10: independent/hands-on verification of the auto-fix push actually working in practice beyond vendor docs, and more detail on failure/edge cases of the auto-fix flow.

   • [claimed-docs] “cubic generates the fix and pushes it to your PR branch.”
   • [claimed-docs] “cubic can automatically fix issues in the background. When the AI spots a problem, you can click the **Fix with cubic** button”
   • [claimed-docs] “cubic can automatically fix issues identified during code review. Request a targeted fix with one click.”
   • [claimed-docs] “Auto-resolve threads: Enable automatic thread resolution to close findings when the issue is fixed”
   • [claimed-docs] “Interact with cubic in PR comments to ask questions, trigger reviews, and fix issues.”
   • [claimed-docs] “Connect cubic's MCP server to your coding agent to read review findings and codebase context, request PR reviews, and triage PR or codebase …”
   • [claimed-docs] “Coding agents: Generate fixes when requested, using your configured provider”

   proof ↗⚑ flag

Handoff

1. ai-native userReview findings hand off cleanly to my coding agent — copyable fix prompts or direct integration with Claude Code, Cursor, or Codex

   weight 2 · round to cubic
   Cursor Bugbot~partialclaimed6/10

   Bugbot provides direct one-click handoff into Cursor's own agent ("Fix in Cursor" and "Fix in Web" opening cursor.com/agents) and posts inline PR comments with suggested fixes, satisfying the core 'review findings hand off cleanly' need for Cursor itself. However, there's no evidence of copyable fix prompts formatted for external tools, nor any direct integration with Claude Code or Codex as named in the story. missing for 10: explicit copyable fix-prompt format, direct integration/handoff to Claude Code, direct integration/handoff to Codex.

   • [claimed-docs] “Fix in Cursor links open issues directly in Cursor”
   • [claimed-docs] “Fix in Web links open issues directly in cursor.com/agents”
   • [claimed-docs] “It analyzes every pull request for bugs, security vulnerabilities, and code quality issues, leaving inline comments with explanations and su…”
   • [claimed-docs] “Bugbot analyzes PR diffs and leaves comments with explanations and fix suggestions.”

   proof ↗⚑ flag

   cubic✓fullprobed8/10

   cubic explicitly supports both hand-off paths: the CLI reviews local changes and 'generates a prompt that your coding agent can use to fix them' (cubic-docs-7), and cubic's MCP server lets you 'connect cubic's MCP server to your coding agent' with named support for Cursor, Claude Code, VS Code, Codex, and Gemini CLI (cubic-docs-8, cubic-docs-35). PR-level auto-fix ('Fix with cubic') that pushes fixes directly to the branch (cubic-docs-4, cubic-docs-29, cubic-docs-53) and coding-agent skills (cubic-docs-17) further reinforce clean hand-off to agents. Missing for 10: independent/hands-on confirmation that the generated prompts or MCP flow work smoothly in practice, and no community evidence specifically validating the agent hand-off UX.

   • [claimed-docs] “The **cubic CLI** reviews local changes before you push. It finds bugs and generates a prompt that your coding agent can use to fix them.”
   • [claimed-docs] “Connect cubic's MCP server to your coding agent to read review findings and codebase context, request PR reviews, and triage PR or codebase …”
   • [claimed-docs] “Install and connect cubic in Cursor, Claude Code, VS Code, Codex, Gemini CLI, or another coding tool.”
   • [claimed-docs] “cubic generates the fix and pushes it to your PR branch.”
   • [claimed-docs] “cubic can automatically fix issues in the background. When the AI spots a problem, you can click the **Fix with cubic** button”
   • [claimed-docs] “cubic can automatically fix issues identified during code review. Request a targeted fix with one click.”
   • [claimed-docs] “cubic skills give your coding agent instructions for reviewing code, handling PR comments, and using your team's codebase context.”
   • [probe] “official MCP server documented at https://docs.cubic.dev/ide/mcp-server”
   • [probe] “official CLI documented at https://docs.cubic.dev/ide/cli-review”

   proof ↗⚑ flag

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

   weight 2 · round to cubic
   Cursor Bugbot~partialclaimed4/10

   Bugbot automatically reviews every PR update and lets team admins set organization-wide rules via Bugbot Automations, which gives some cross-item automation, but there's no documented capability to trigger or manage reviews in bulk across many PRs/repos at once from a single user action. missing for 10: explicit bulk/batch trigger across multiple PRs or repos, any UI/API for multi-item selection, evidence of bulk fix application beyond per-PR 'Fix in Cursor/Web' links.

   • [claimed-docs] “Runs automatic reviews on every PR update”
   • [claimed-docs] “Team admins can also create organization-wide rules in [Bugbot Automations](https://cursor.com/automations/from-cursor/bugbot).”
   • [claimed-docs] “Bugbot Teams includes code reviews on all PRs, analytics and reporting, effort level controls, and advanced rules and settings.”

   proof ↗⚑ flag

   cubic~partialclaimed5/10

   cubic supports some bulk-scale automation — codebase scans that 'deploy thousands of AI agents to find bugs and vulnerabilities across your repository' (cubic-docs-12) and an Analytics API that aggregates PR-level data across many PRs (cubic-docs-16, cubic-docs-59) — but there is no evidence of user-triggered bulk operations like batch-fixing, batch-approving, or batch-triaging many PRs/items at once beyond per-PR auto-approval and auto-fix. Missing for 10: explicit bulk/batch action UI or API (e.g., select-many-and-fix, bulk approve across PRs), evidence of scale/performance at bulk volume, and independent confirmation of the codebase-scan bulk claim.

   • [claimed-docs] “Codebase scans deploy thousands of AI agents to find bugs and vulnerabilities across your repository.”
   • [claimed-docs] “The Analytics API gives you PR-level data on how many issues were flagged, how many were fixed, how much AI code was authored, etc.”
   • [claimed-docs] “The analytics dashboard shows how your team ships code across three lenses: AI coding usage, AI review impact, and delivery speed.”
   • [claimed-docs] “Cross-repo reviews help cubic catch changes that need a matching update in another repository. Link related repositories so reviews can chec…”
   • [claimed-docs] “Enable [auto-approval](/ai-review/auto-approval) to let cubic approve PRs that meet your review policy.”

   proof ↗⚑ flag

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

   weight 3 · round to Cursor Bugbot
   Cursor Bugbot~partialclaimed6/10

   Bugbot supports automatic triggers on PR updates, manual triggers via comments, custom repo-level guidelines (BUGBOT.md), and org-wide rules via Bugbot Automations — showing genuine rule-based automation tied to events. However, the evidence doesn't detail a broad general-purpose 'if X event then Y action' rules engine beyond PR review triggers and effort-level configuration. missing for 10: documentation of the full scope/flexibility of 'Bugbot Automations' rules (what events/actions are configurable beyond PR-triggered reviews), independent hands-on verification of automation rule customization beyond BUGBOT.md.

   • [claimed-docs] “Runs automatic reviews on every PR update”
   • [claimed-docs] “Manual trigger by commenting `cursor review` or `bugbot run` on any PR”
   • [claimed-docs] “Create `.cursor/BUGBOT.md` files in your repository to give Bugbot project-specific review guidelines.”
   • [claimed-docs] “Team admins can also create organization-wide rules in [Bugbot Automations](https://cursor.com/automations/from-cursor/bugbot).”
   • [claimed-docs] “Bugbot Teams includes code reviews on all PRs, analytics and reporting, effort level controls, and advanced rules and settings.”
   • [claimed-docs] “Describe in natural language when Bugbot should use low, default, or high effort. Cursor will dynamically set effort levels based on your in…”

   proof ↗⚑ flag

   cubic~partialcommunity5/10

   cubic supports event-triggered automation within its code-review domain: PRs auto-trigger reviews, custom agents enforce rules on PRs, auto-approval and auto-fix run on policy conditions, and cubic.yaml configures behavior — but this is domain-specific (PR/code-review events) rather than a general-purpose rules engine for arbitrary events/actions that an AI-native user could define. Missing for 10: evidence of a generalized rule/trigger builder spanning arbitrary event sources and actions beyond PR review workflows, and independent hands-on validation of custom-agent rule reliability (community feedback questions robustness of YAML-based rules).

   • [claimed-docs] “Once installed, cubic automatically reviews new pull requests.”
   • [claimed-docs] “Custom agents are review rules that enforce your organization's specific best practices across pull requests.”
   • [claimed-docs] “Enable [auto-approval](/ai-review/auto-approval) to let cubic approve PRs that meet your review policy.”
   • [claimed-docs] “Enable auto-approval to let cubic approve PRs that meet your review policy.”
   • [claimed-docs] “cubic can automatically fix issues in the background. When the AI spots a problem, you can click the **Fix with cubic** button”
   • [claimed-docs] “cubic.yaml lives in the root of your repository and becomes the source of truth for AI review behavior, ignore patterns, PR descriptions, an…”
   • [claimed-docs] “Auto-approval lets you skip human review for pull requests that cubic determines are low risk and issue-free.”
   • [community] “The 'in-codebase' approach is the right one, but a YAML file with plain text is a half-measure. The most reliable rule that 'lives next to t…”

   proof ↗⚑ flag

Context

1. engineering leadThe reviewer understands changes that span multiple repositories or a large monorepo and reviews them coherently

   weight 2 · round to cubic
   Cursor Bugbot—none0/10

   Bugbot's documented behavior is per-repository PR review (diffs, inline comments, BUGBOT.md for repo-specific rules) with no evidence of coherent review across multiple linked repositories or explicit large-monorepo context handling. Missing for 10: any mention of cross-repo dependency awareness, monorepo-scale indexing, or coordinated review across repos in a single PR/change set.

   • [claimed-docs] “It analyzes every pull request for bugs, security vulnerabilities, and code quality issues, leaving inline comments with explanations and su…”
   • [claimed-docs] “Create `.cursor/BUGBOT.md` files in your repository to give Bugbot project-specific review guidelines.”
   • [claimed-docs] “Bugbot analyzes PR diffs and leaves comments with explanations and fix suggestions.”

   proof ↗⚑ flag

   cubic~partialclaimed7/10

   cubic explicitly ships cross-repo reviews (link related repositories so reviews can check shared APIs/schemas/docs) and codebase-wide indexing via AI wiki and codebase scans, which support coherent understanding of changes spanning repos or large codebases. However, evidence is entirely vendor docs with no independent/hands-on validation of monorepo-scale coherence, and the cross-repo feature description is thin (only checking shared APIs/schemas, not full monorepo-scale reasoning). Missing for 10: independent/hands-on evidence of multi-repo review coherence at scale, explicit monorepo support details, and any case study of large/complex spanning changes reviewed successfully.

   • [claimed-docs] “Link related repositories so reviews can check shared APIs, schemas, docs, or release work.”
   • [claimed-docs] “Cross-repo reviews help cubic catch changes that need a matching update in another repository. Link related repositories so reviews can chec…”
   • [claimed-docs] “Codebase scans deploy thousands of AI agents to find bugs and vulnerabilities across your repository.”
   • [claimed-docs] “cubic's AI wiki automatically indexes your codebase and produces searchable wikis, complete with links to source code, architecture diagrams…”

   proof ↗⚑ flag

2. developerReview comments reflect the whole repository — call sites, related modules, existing conventions — not just the changed hunks

   weight 3 · round to cubic
   Cursor Bugbot~partialclaimed4/10

   Docs state Bugbot "analyzes PR diffs" (docs-24) and reads PR comments for context (docs-5/14), plus BUGBOT.md lets teams encode repo-specific conventions (docs-6) — suggesting some repo-level convention awareness, but there is no explicit claim or evidence that Bugbot traces call sites or related modules beyond the changed hunks. Missing for 10: explicit documentation or examples of cross-file/call-site analysis, evidence review considers unchanged related modules, and independent confirmation that comments reference whole-repo context rather than diff-only.

   • [claimed-docs] “Bugbot analyzes PR diffs and leaves comments with explanations and fix suggestions.”
   • [claimed-docs] “Create `.cursor/BUGBOT.md` files in your repository to give Bugbot project-specific review guidelines.”
   • [claimed-docs] “Uses existing PR comments as context: reads connected PR comments (top-level and inline) to avoid duplicate suggestions and build on prior f…”

   proof ↗⚑ flag

   cubic~partialclaimed7/10

   cubic's docs describe repo-wide context mechanisms beyond the diff: it auto-detects context files (README, AGENTS.md, .cursorrules), links related repositories for cross-repo reviews of shared APIs/schemas, runs codebase scans across the whole repo, builds an AI wiki index of the codebase, and learns 'unwritten rules' from senior engineers' historical reviews and team feedback — all suggesting reviews draw on broader repository knowledge, not just changed hunks. However, no evidence explicitly confirms it traces call sites or cross-references unrelated modules within a single-repo review, and there's no independent/hands-on corroboration of this specific behavior. Missing for 10: explicit call-site/dependency-tracing evidence, independent verification that review comments actually cite non-hunk code.

   • [claimed-docs] “cubic automatically detects and uses context files in your repository, including `README.md`, `context.md`, `AGENTS.md`, `.cursorrules`”
   • [claimed-docs] “cubic automatically detects and uses context files in your repository, including `README.md`, `context.md`, `AGENTS.md`, `.cursorrules`, age…”
   • [claimed-docs] “Link related repositories so reviews can check shared APIs, schemas, docs, or release work.”
   • [claimed-docs] “Cross-repo reviews help cubic catch changes that need a matching update in another repository. Link related repositories so reviews can chec…”
   • [claimed-docs] “Codebase scans deploy thousands of AI agents to find bugs and vulnerabilities across your repository.”
   • [claimed-docs] “cubic's AI wiki automatically indexes your codebase and produces searchable wikis, complete with links to source code, architecture diagrams…”
   • [claimed-docs] “cubic learns your team's unwritten rules from two sources: direct feedback on its comments, and patterns extracted from your senior engineer…”

   proof ↗⚑ flag

Memory

1. ai-native userThe reviewer builds a persistent memory of my team's conventions and past review decisions and applies it to future PRs

   weight 2 · round to cubic
   Cursor Bugbot~partialclaimed4/10

   Bugbot supports a manually-authored `.cursor/BUGBOT.md` for team conventions and reads existing PR comments to avoid duplicating feedback, but this is static, user-maintained configuration and per-PR context — not an evolving, persistent memory that automatically learns from past review decisions across PRs. Missing for 10: evidence of automatic learning/adaptation from historical review outcomes, cross-PR memory beyond the current thread, and any feedback loop that updates conventions based on accepted/rejected suggestions.

   • [claimed-docs] “Create `.cursor/BUGBOT.md` files in your repository to give Bugbot project-specific review guidelines.”
   • [claimed-docs] “Uses existing PR comments as context: reads connected PR comments (top-level and inline) to avoid duplicate suggestions and build on prior f…”
   • [claimed-docs] “reads connected PR comments (top-level and inline) to avoid duplicate suggestions and build on prior feedback”

   proof ↗⚑ flag

   cubic✓fullcommunity8/10

   cubic explicitly documents persistent memory: it learns from replies/reactions to its comments and from patterns in senior engineers' historical reviews, storing conventions in cubic.yaml and custom agents that persist across PRs and repos (cubic-docs-10,32,33,54,9,11,34). This directly matches the ai-native persona's desire for a reviewer that builds team-convention memory over time. Missing for 10: independent/hands-on verification that learned rules actually persist and improve accuracy over many PRs (one community comment questions whether YAML-based rules are robust vs. hard failures, cubic-comm-2), and no quantitative data on learning effectiveness.

   • [claimed-docs] “cubic automatically learns when you: Reply to its comments... React to suggestions: Thumbs up/down help cubic calibrate what's useful vs noi…”
   • [claimed-docs] “Reply to its comments: Type a response explaining what cubic should do differently, and it remembers for next time”
   • [claimed-docs] “React to suggestions: Thumbs up/down help cubic calibrate what's useful vs noise for your specific codebase”
   • [claimed-docs] “cubic learns your team's unwritten rules from two sources: direct feedback on its comments, and patterns extracted from your senior engineer…”
   • [claimed-docs] “Custom agents are review rules that enforce your organization's specific best practices across pull requests.”
   • [claimed-docs] “`cubic.yaml` lives in the root of your repository and becomes the source of truth for AI review behavior, ignore patterns, PR descriptions, …”
   • [claimed-docs] “cubic.yaml lives in the root of your repository and becomes the source of truth for AI review behavior, ignore patterns, PR descriptions, an…”
   • [community] “The 'in-codebase' approach is the right one, but a YAML file with plain text is a half-measure. The most reliable rule that 'lives next to t…”

   proof ↗⚑ flag

Chat

1. developerI reply to the reviewer in the PR thread to ask questions, get explanations, or issue commands — and it answers in context

   weight 2 · round to cubic
   Cursor Bugbot~partialclaimed4/10

   Bugbot supports comment-based commands in the PR thread (`cursor review`, `bugbot run`, `verbose=true`) and reads prior PR comments to build context and avoid duplicate suggestions, showing some interactive, context-aware behavior. However, there is no evidence it supports open-ended conversational replies (answering arbitrary questions or explaining its reasoning on demand) beyond the fixed set of trigger commands. Missing for 10: evidence of free-form Q&A/explanation replies in the PR thread, examples of it responding to developer questions rather than just re-running reviews.

   • [claimed-docs] “Manual trigger by commenting `cursor review` or `bugbot run` on any PR”
   • [claimed-docs] “Uses existing PR comments as context: reads connected PR comments (top-level and inline) to avoid duplicate suggestions and build on prior f…”
   • [claimed-docs] “Comment `bugbot run verbose=true` or `cursor review verbose=true` on the pull request. Bugbot replies with a table of the rules included in …”
   • [claimed-docs] “Comment `cursor review verbose=true` or `bugbot run verbose=true` on the PR for detailed logs, which Bugbot rules loaded, and a request ID”

   proof ↗⚑ flag

   cubic✓fullcommunity8/10

   Docs explicitly describe replying to cubic's PR comments to ask questions, get clarifications, issue fix commands, or trigger reviews/Ultrareview, with cubic responding in-thread and even learning from replies. This is well documented across multiple pages (interactive-comments, memory-and-learning, quickstart) and corroborated by a community user noting cubic gives deeper technical explanations than plain LLMs. missing for 10: independent hands-on verification of multi-turn contextual follow-up quality/accuracy in real threads.

   • [claimed-docs] “Reply to a review comment to ask for clarification:”
   • [claimed-docs] “Reply to a review comment to ask for clarification”
   • [claimed-docs] “Interact with cubic in PR comments to ask questions, trigger reviews, and fix issues.”
   • [claimed-docs] “Interact with cubic in PR comments to ask questions, trigger reviews, and fix issues. You can tag `@cubic-dev-ai` directly, or reply to cubi…”
   • [claimed-docs] “Reply to its comments: Type a response explaining what cubic should do differently, and it remembers for next time”
   • [claimed-docs] “When a pull request needs extra scrutiny, you can ask cubic for an Ultrareview.”
   • [community] “I really liked it - it hit the mark. The current balance works very well, and it genuinely surprised me. It provides more technical explanat…”

   proof ↗⚑ flag

Control

1. developerI control when reviews run — skip drafts, trigger on demand, filter by branch or label — so the bot shows up only when wanted

   weight 1 · round to Cursor Bugbot
   Cursor Bugbot~partialclaimed5/10

   Bugbot supports on-demand triggering via PR comments (`cursor review`/`bugbot run`) and automatic review on every PR update, plus org-wide rules via Bugbot Automations and BUGBOT.md guidelines. However, there's no evidence of draft-PR skipping, branch/label filtering, or granular per-repo/per-branch control settings that let developers scope exactly when the bot runs. missing for 10: draft-PR skip behavior, branch/label-based filtering rules, explicit settings UI for scoping trigger conditions beyond org-wide automations.

   • [claimed-docs] “Runs automatic reviews on every PR update”
   • [claimed-docs] “Manual trigger by commenting `cursor review` or `bugbot run` on any PR”
   • [claimed-docs] “Team admins can also create organization-wide rules in [Bugbot Automations](https://cursor.com/automations/from-cursor/bugbot).”
   • [claimed-docs] “Create `.cursor/BUGBOT.md` files in your repository to give Bugbot project-specific review guidelines.”

   proof ↗⚑ flag

   cubic~partialclaimed4/10

   cubic clearly supports on-demand triggering (@cubic-dev-ai review this PR, Ultrareview on demand) and configurable behavior via cubic.yaml (ignore patterns, review behavior), giving developers some control over when reviews run. However there is no explicit evidence of skipping draft PRs or filtering by branch/label — cubic.yaml's 'ignore patterns' are documented generically, not tied to draft/branch/label filters. Missing for 10: explicit draft-PR skip setting, branch-based trigger rules, label-based filtering documentation.

   • [claimed-docs] “Once installed, cubic automatically reviews new pull requests.”
   • [claimed-docs] “To review a PR that was opened _before_ you installed the app, comment: `@cubic-dev-ai review this PR`.”
   • [claimed-docs] “When a pull request needs extra scrutiny, you can ask cubic for an Ultrareview.”
   • [claimed-docs] “Ultrareview is cubic's deepest review. It runs a longer, multi-pass analysis using cubic's most capable review models, and typically takes a…”
   • [claimed-docs] “`cubic.yaml` lives in the root of your repository and becomes the source of truth for AI review behavior, ignore patterns, PR descriptions, …”
   • [claimed-docs] “cubic.yaml lives in the root of your repository and becomes the source of truth for AI review behavior, ignore patterns, PR descriptions, an…”

   proof ↗⚑ flag

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

   weight 2 · round to cubic
   Cursor Bugbot—none0/10

   No evidence of a public API for Bugbot; all interactions documented are via PR comments (GitHub/GitLab/Bitbucket/Azure DevOps), the Cursor IDE, or BUGBOT.md config files, not a programmatic API for triggering/configuring reviews. Absence of evidence for this applicable capability yields none.

   ⚑ flag

   cubic~partialprobed5/10

   cubic exposes some programmatic surfaces beyond the UI — an Analytics API for PR-level metrics, an official MCP server for review findings/PR reviews/triage/subscription management, and a CLI for local review — but there is no general public REST/OpenAPI covering full platform functionality (probe found openapi.json/swagger.json all 404), so many UI features (wiki, custom agents config, integrations, analytics dashboards) lack documented API parity. missing for 10: a comprehensive public API/OpenAPI spec covering all UI capabilities, evidence that wiki/integrations/custom-agent configuration can be done via API, and confirmation that Analytics API + MCP together achieve full UI parity.

   • [claimed-docs] “The Analytics API gives you PR-level data on how many issues were flagged, how many were fixed, how much AI code was authored, etc.”
   • [claimed-docs] “Connect cubic's MCP server to your coding agent to read review findings and codebase context, request PR reviews, and triage PR or codebase …”
   • [claimed-docs] “You can now ask your coding agent to check your cubic subscription, manage team seats and roles, and purchase more seats without leaving you…”
   • [claimed-docs] “The **cubic CLI** reviews local changes before you push. It finds bugs and generates a prompt that your coding agent can use to fix them.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cubic.dev/openapi.json, https://docs.cubic.dev/swagger.json, https://docs.cubic.dev/api…”
   • [probe] “official MCP server documented at https://docs.cubic.dev/ide/mcp-server”
   • [probe] “official CLI documented at https://docs.cubic.dev/ide/cli-review”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Cursor Bugbot—none0/10

   Evidence covers Bugbot's PR review features, integrations, and account deletion, but there is no mention of any data export functionality or open-format export of reviews/settings — missing for 10: any export tool, data portability feature, or open-format download of Bugbot's findings/config.

   • [claimed-docs] “Security page, certifications: "Cursor holds AIUC-1, ISO/IEC 27001:2022, and ISO/IEC 42001:2023 certifications, along with a SOC 2 Type II a…”

   proof ↗⚑ flag

   cubic—none0/10

   Cubic is a code review/analysis platform whose data (review findings, PR comments, analytics, wiki) lives in GitHub, Jira, Notion, etc.; there is no evidence of a data export feature for users to download their cubic-generated data in open formats. The Analytics API (cubic-docs-16) offers programmatic access to some metrics but this is not documented as a full data export/portability mechanism, and no evidence addresses exporting AI wiki content, review history, or memory/learning data.

   • [claimed-docs] “The Analytics API gives you PR-level data on how many issues were flagged, how many were fixed, how much AI code was authored, etc.”
   • [claimed-docs] “cubic's AI wiki automatically indexes your codebase and produces searchable wikis, complete with links to source code, architecture diagrams…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Cursor Bugbot—none0/10

   No evidence that Cursor Bugbot's source code is open or under an open license; it is a closed proprietary SaaS review bot with only docs, security/certification pages, and llms.txt probes present. Missing for 10: any open-source license, public source repository, or statement of code availability.

   ⚑ flag

   cubic—none0/10

   No evidence indicates cubic's source code is open or under an open license; cubic appears to be a closed, commercial SaaS product with SOC2 compliance and privacy policies but no public repository or license mentioned.

   ⚑ flag

Platforms

1. developerThe reviewer installs as a GitHub/GitLab app and posts reviews as native inline comments on my pull requests within minutes

   weight 3 · round drawn
   Cursor Bugbot✓fullcommunity8/10

   Docs confirm installation via GitHub/GitLab apps that connect repos to Bugbot, automatic reviews on every PR update, and findings posted as native inline PR comments with explanations/fix suggestions; community reports corroborate it running live in orgs' PR workflows. Minor gap: no explicit evidence of the 'within minutes' setup speed or independent onboarding walkthrough, missing for 10: independent verification of install speed/time-to-first-review, edge-case reliability data beyond mixed community sentiment.

   • [claimed-docs] “GitHub (including GitHub Enterprise Server): See the GitHub integration page”
   • [claimed-docs] “GitLab (including GitLab Self-Hosted): See the GitLab integration page”
   • [claimed-docs] “The Cursor GitHub app connects your repositories so you can use features like [Cloud Agents](/docs/cloud-agent) and [Bugbot](/docs/bugbot).”
   • [claimed-docs] “The GitLab integration connects your repositories so you can use features like [Cloud Agents](/docs/cloud-agent) and [Bugbot](/docs/bugbot).”
   • [claimed-docs] “It analyzes every pull request for bugs, security vulnerabilities, and code quality issues, leaving inline comments with explanations and su…”
   • [claimed-docs] “Runs automatic reviews on every PR update”
   • [community] “Do you have actual experience with bugbot? Its live in our org and is actually pretty good, almost none of its comments are frivolous or wro…”
   • [community] “I've found Bugbot to be shockingly effective at finding bugs in my PRs. Even when it's wrong, it's usually worth adding a comment, since it'…”

   proof ↗⚑ flag

   cubic✓fullcommunity8/10

   Docs confirm installation as a GitHub/GitLab app with automatic reviews on new PRs, inline PR comments (@cubic-dev-ai, interactive comments, Fix with cubic), and a quickstart flow explicitly framed as 'minutes' with a free trial. Community feedback corroborates real-world usefulness of PR-level comments. Missing for 10: independent third-party confirmation of install speed and hands-on GitLab app usage (most evidence is first-party docs).

   • [claimed-docs] “Once installed, cubic automatically reviews new pull requests.”
   • [claimed-docs] “Spots bugs and improvements: Comments on bugs and improvements in pull requests”
   • [claimed-docs] “Interact with cubic in PR comments to ask questions, trigger reviews, and fix issues.”
   • [claimed-docs] “Get started with cubic AI code review in minutes.”
   • [claimed-docs] “Post this comment on GitHub to start a review: text theme={null} @cubic-dev-ai review this PR ”
   • [claimed-docs] “7 days free, no credit card required.”
   • [community] “I really liked it - it hit the mark. The current balance works very well, and it genuinely surprised me. It provides more technical explanat…”

   proof ↗⚑ flag

Suggestions

1. developerReview comments include committable suggested diffs I can apply with one click

   weight 3 · round to cubic
   Cursor Bugbot~partialclaimed5/10

   Bugbot leaves inline PR comments with suggested fixes and offers 'Fix in Cursor' / 'Fix in Web' links, but these open the issue in Cursor or cursor.com/agents for the agent to implement — not a native one-click 'commit suggestion' diff applied directly in the PR review UI as the story describes. Missing for 10: evidence of a native GitHub-style committable suggestion block that can be applied with a single click directly in the PR thread, and independent confirmation of this specific commit-suggestion workflow.

   • [claimed-docs] “It analyzes every pull request for bugs, security vulnerabilities, and code quality issues, leaving inline comments with explanations and su…”
   • [claimed-docs] “Bugbot analyzes PR diffs and leaves comments with explanations and fix suggestions.”
   • [claimed-docs] “Fix in Cursor links open issues directly in Cursor”
   • [claimed-docs] “Fix in Web links open issues directly in cursor.com/agents”

   proof ↗⚑ flag

   cubic✓fullclaimed7/10

   Cubic explicitly supports one-click fixes: reviewers can click 'Fix with cubic' and cubic generates the fix and pushes it directly to the PR branch (cubic-docs-4, cubic-docs-29, cubic-docs-53), fulfilling the core 'one-click apply' story for review comments. Missing for 10: no evidence of an inline GitHub-style suggested-diff block shown for manual approval before commit, and no independent/hands-on corroboration of this specific flow beyond first-party docs.

   • [claimed-docs] “cubic generates the fix and pushes it to your PR branch.”
   • [claimed-docs] “cubic can automatically fix issues in the background. When the AI spots a problem, you can click the **Fix with cubic** button”
   • [claimed-docs] “cubic can automatically fix issues identified during code review. Request a targeted fix with one click.”
   • [claimed-docs] “Coding agents: Generate fixes when requested, using your configured provider”

   proof ↗⚑ flag

Summaries

1. developerEvery PR gets an auto-generated summary and change walkthrough so human reviewers orient fast

   weight 2 · round to cubic
   Cursor Bugbot—none0/10

   Evidence shows Bugbot analyzes PR diffs for bugs, security issues, and code quality, leaving inline comments with explanations/fixes — but nothing in the docs or community evidence describes an auto-generated PR summary or change walkthrough for reviewer orientation. Bugbot's function is bug-finding, not summarization.

   • [claimed-docs] “It analyzes every pull request for bugs, security vulnerabilities, and code quality issues, leaving inline comments with explanations and su…”
   • [claimed-docs] “Bugbot analyzes PR diffs and leaves comments with explanations and fix suggestions.”
   • [probe] “PROBE docs-md: HTTP 200 at https://cursor.com/docs/bugbot.md # Bugbot Bugbot reviews pull requests and identifies bugs, security issues, an…”

   proof ↗⚑ flag

   cubic✓fullcommunity9/10

   cubic explicitly generates PR summaries/descriptions from code changes automatically on every PR (docs-21, docs-57), plus keeps the summary visible alongside the diff while scrolling for easier orientation (docs-43), and community feedback corroborates depth of explanations (cubic-comm-1). Missing for 10: independent/hands-on review specifically confirming summary accuracy or walkthrough quality at scale beyond docs and one community quote.

   • [claimed-docs] “PR summaries: Generates PR descriptions based on code changes”
   • [claimed-docs] “cubic helps your team spend less time writing PR descriptions automatically by generating clear, concise summaries.”
   • [claimed-docs] “Now, the group description stays beside the diff as you scroll, so you can read the code and its explanation together.”
   • [claimed-docs] “Spots bugs and improvements: Comments on bugs and improvements in pull requests”
   • [community] “I really liked it - it hit the mark. The current balance works very well, and it genuinely surprised me. It provides more technical explanat…”

   proof ↗⚑ flag

Updates

1. developerPushing new commits triggers an incremental re-review that tracks what was fixed instead of repeating old comments

   weight 2 · round to Cursor Bugbot
   Cursor Bugbot✓fullprobed7/10

   Docs confirm Bugbot re-reviews automatically on every PR update and explicitly reads existing PR comments (top-level and inline) to avoid duplicate suggestions and build on prior feedback, which directly matches the incremental re-review story. Missing for 10: independent/hands-on confirmation that fixed issues are specifically marked resolved rather than re-flagged, and no detailed changelog of what 'tracking fixed' looks like in practice.

   • [claimed-docs] “Runs automatic reviews on every PR update”
   • [claimed-docs] “Uses existing PR comments as context: reads connected PR comments (top-level and inline) to avoid duplicate suggestions and build on prior f…”
   • [claimed-docs] “reads connected PR comments (top-level and inline) to avoid duplicate suggestions and build on prior feedback”
   • [probe] “PROBE docs-md: HTTP 200 at https://cursor.com/docs/bugbot.md # Bugbot Bugbot reviews pull requests and identifies bugs, security issues, an…”

   proof ↗⚑ flag

   cubic~partialclaimed6/10

   cubic auto-reviews new PRs and auto-resolves threads when issues are fixed (cubic-docs-1, cubic-docs-20), and its memory/learning system means feedback and prior comments inform future reviews (cubic-docs-10, cubic-docs-54), which together imply incremental re-review behavior rather than repeating stale comments. However, there's no explicit documentation describing a re-review triggered specifically by new commits that diffs against prior findings or explicitly states old fixed issues won't be re-flagged. missing for 10: explicit docs on commit-triggered incremental re-review logic, confirmation that previously-flagged-and-fixed issues are suppressed on subsequent pushes, and independent/hands-on evidence of this specific workflow.

   • [claimed-docs] “Once installed, cubic automatically reviews new pull requests.”
   • [claimed-docs] “Auto-resolve threads: Enable automatic thread resolution to close findings when the issue is fixed”
   • [claimed-docs] “cubic automatically learns when you: Reply to its comments... React to suggestions: Thumbs up/down help cubic calibrate what's useful vs noi…”
   • [claimed-docs] “cubic learns your team's unwritten rules from two sources: direct feedback on its comments, and patterns extracted from your senior engineer…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Cursor Bugbot—none0/10

   No evidence of data residency/region selection controls for Bugbot; only privacy-mode (no training) and certifications are mentioned, with no mention of choosing storage region. missing for 10: any documentation of regional data storage options, residency controls, or geo-specific hosting.

   ⚑ flag

   cubic—none0/10

   No evidence of data residency/region selection options in cubic's documentation; privacy/security docs mention SOC 2 compliance and no third-party model training, but nothing about choosing storage region or data residency controls.

   • [claimed-docs] “Privacy & security: "No third-party model training on Customer Code — Our AI model providers (e.g., OpenAI, Anthropic) contractually commit …”
   • [claimed-docs] “Privacy & security: "cubic is SOC 2 Type 1 compliant, demonstrating our commitment to security and trust for our customers. We maintain comp…”

   proof ↗⚑ flag

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

   weight 3 · round to cubic
   Cursor Bugbot~partialclaimed6/10

   Cursor's security docs explicitly state that enabling Privacy Mode means 'we will not train on your data,' and this is available to any account (free/Pro/team), which would extend to Bugbot's PR review data. However, the evidence pack contains no Bugbot-specific documentation confirming that Bugbot review data (PR diffs, comments) is covered under this toggle, nor independent corroboration of this behavior in practice for Bugbot specifically. Missing for 10: Bugbot-specific privacy/training documentation, independent verification that Bugbot respects Privacy Mode.

   • [claimed-docs] “Security page, Privacy Mode: "Privacy Mode can be enabled in settings or by a team or enterprise admin. Privacy Mode is available to anyone …”
   • [claimed-docs] “Security page, certifications: "Cursor holds AIUC-1, ISO/IEC 27001:2022, and ISO/IEC 42001:2023 certifications, along with a SOC 2 Type II a…”
   • [claimed-docs] “Runs automatic reviews on every PR update”

   proof ↗⚑ flag

   cubic✓fullclaimed8/10

   cubic's privacy/security docs explicitly state model providers contractually commit to not train on customer code, and offer a full opt-out to block AI features entirely for a workspace. missing for 10: independent/third-party audit confirming the no-training claim, and detail on how the opt-out mechanism is enforced technically.

   • [claimed-docs] “Privacy & security: "No third-party model training on Customer Code — Our AI model providers (e.g., OpenAI, Anthropic) contractually commit …”

   proof ↗⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Cursor Bugbot
   Cursor Bugbot~partialclaimed4/10

   Cursor's security page (shared across products) mentions Privacy Mode ('we will not train on your data') and that accounts can be deleted anytime from Settings, which offers some data-control levers, but there is no Bugbot-specific documentation on retention periods for PR review data, comment history, or deletion of stored review artifacts. Missing for 10: Bugbot-specific data retention policy, explicit deletion/export controls for review comments and analysis data, and independent confirmation these controls apply to Bugbot's PR data.

   • [claimed-docs] “Security page, Privacy Mode: "Privacy Mode can be enabled in settings or by a team or enterprise admin. Privacy Mode is available to anyone …”
   • [claimed-docs] “Security page, certifications: "Cursor holds AIUC-1, ISO/IEC 27001:2022, and ISO/IEC 42001:2023 certifications, along with a SOC 2 Type II a…”

   proof ↗⚑ flag

   cubic~partialclaimed3/10

   cubic's privacy/security docs mention no third-party model training and the ability to block AI features for a workspace, showing some data-handling controls, but there is no explicit mention of data retention periods, deletion requests, or a self-service deletion mechanism. missing for 10: explicit retention policy, user-initiated deletion process, confirmation of deletion timelines/scope.

   • [claimed-docs] “Privacy & security: "No third-party model training on Customer Code — Our AI model providers (e.g., OpenAI, Anthropic) contractually commit …”
   • [claimed-docs] “Privacy & security: "cubic is SOC 2 Type 1 compliant, demonstrating our commitment to security and trust for our customers. We maintain comp…”

   proof ↗⚑ flag

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

   weight 2 · round to Cursor Bugbot
   Cursor Bugbot~partialclaimed4/10

   Cursor's security page mentions a 'Privacy Mode' that stops training on user data and account deletion options, which is adjacent to a privacy-posture ask, but there's no explicit documentation of a telemetry/usage-tracking opt-out specific to Bugbot itself. Missing for 10: explicit Bugbot-specific telemetry/usage tracking opt-out setting, documentation distinguishing telemetry from training-data usage, and any independent confirmation that tracking can be disabled.

   • [claimed-docs] “Security page, Privacy Mode: "Privacy Mode can be enabled in settings or by a team or enterprise admin. Privacy Mode is available to anyone …”
   • [claimed-docs] “Security page, certifications: "Cursor holds AIUC-1, ISO/IEC 27001:2022, and ISO/IEC 42001:2023 certifications, along with a SOC 2 Type II a…”

   proof ↗⚑ flag

   cubic—none0/10

   Evidence covers data-training and access-control privacy commitments (no third-party model training, SOC2 compliance, ability to block AI features workspace-wide) but no documented telemetry/usage-tracking toggle or opt-out mechanism specifically for product analytics/telemetry.

   ⚑ flag

Analytics

1. engineering leadI see dashboards of findings, acceptance rates, and review coverage across my org

   weight 1 · round to cubic
   Cursor Bugbot~partialclaimed4/10

   Docs mention that Bugbot Teams includes 'analytics and reporting' alongside code reviews on all PRs, implying some org-level reporting capability, but there is no detail on dashboard content, acceptance-rate tracking, or review-coverage metrics. missing for 10: dashboard screenshots or specifics on findings/acceptance-rate/coverage metrics, independent corroboration of the analytics feature.

   • [claimed-docs] “Bugbot Teams includes code reviews on all PRs, analytics and reporting, effort level controls, and advanced rules and settings.”

   proof ↗⚑ flag

   cubic✓fullclaimed7/10

   cubic's Analytics dashboard explicitly covers PR-level findings/fixes, AI coding and AI review impact tabs, and delivery/effectiveness across repos, directly matching the engineering-lead dashboard story (cubic-docs-16, 41, 42, 59, 60). Missing for 10: explicit org-wide rollup UI screenshots, exact 'acceptance rate' terminology/metric definition, and independent/hands-on corroboration beyond vendor docs.

   • [claimed-docs] “The Analytics API gives you PR-level data on how many issues were flagged, how many were fixed, how much AI code was authored, etc.”
   • [claimed-docs] “The AI coding tab shows how AI assistants contribute to merged pull requests in your repositories.”
   • [claimed-docs] “The AI review tab shows whether cubic reviews are helping your team ship better code faster.”
   • [claimed-docs] “The analytics dashboard shows how your team ships code across three lenses: AI coding usage, AI review impact, and delivery speed.”
   • [claimed-docs] “The Delivery and effectiveness tab focuses on how quickly PRs move from creation to merge and where bottlenecks appear.”

   proof ↗⚑ flag

Gates

1. engineering leadThe reviewer can gate merges — a required status check or blocking review that enforces resolution of critical findings

   weight 2 · round drawn
   Cursor Bugbot—none0/10

   Evidence shows Bugbot posts PR comments/findings and supports manual/automatic triggers, but nothing describes it functioning as a required status check or blocking review that gates merges on resolution of critical findings — missing for 10: any mention of CI status check integration, merge-blocking configuration, or required-review enforcement.

   • [claimed-docs] “Runs automatic reviews on every PR update”
   • [claimed-docs] “It analyzes every pull request for bugs, security vulnerabilities, and code quality issues, leaving inline comments with explanations and su…”
   • [claimed-docs] “Bugbot analyzes PR diffs and leaves comments with explanations and fix suggestions.”
   • [claimed-docs] “Bugbot Teams includes code reviews on all PRs, analytics and reporting, effort level controls, and advanced rules and settings.”

   proof ↗⚑ flag

   cubic—none0/10

   Cubic documents auto-approval (skipping human review for low-risk PRs) and auto-resolving comment threads, but there is no evidence of a required GitHub status check or blocking review policy that prevents merge until critical findings are resolved — the auto-approval feature actually works in the opposite direction (approving rather than blocking). Missing for full credit: documentation of a required/blocking check integration, branch-protection enforcement, or explicit 'block merge on critical findings' policy.

   • [claimed-docs] “Enable [auto-approval](/ai-review/auto-approval) to let cubic approve PRs that meet your review policy.”
   • [claimed-docs] “Auto-resolve threads: Enable automatic thread resolution to close findings when the issue is fixed”
   • [claimed-docs] “Auto-approval lets you skip human review for pull requests that cubic determines are low risk and issue-free.”

   proof ↗⚑ flag

Detection

1. developerThe reviewer catches real bugs in my PR — logic errors, race conditions, broken edge cases — not just style nits

   weight 3 · round to cubic
   Cursor Bugbot!disputedcontradicted6/10

   Docs claim Bugbot finds real bugs, security vulnerabilities, and logic issues beyond style (docs-13, docs-24), and one HN commenter corroborates it 'finds genuine bugs most reviewers miss' (comm-2, comm-4). But other hands-on reports contradict this: one engineer says instances arose where Bugbot's own suggested fix was later contested by the LLM itself, and another says its review comments 'were all subtly wrong' (comm-1, comm-3), so accuracy in practice is inconsistent rather than uniformly reliable. Missing for 10: independent benchmark data on false-positive rate, and broader third-party validation beyond a single HN thread's mixed anecdotes.

   • [claimed-docs] “It analyzes every pull request for bugs, security vulnerabilities, and code quality issues, leaving inline comments with explanations and su…”
   • [claimed-docs] “Bugbot analyzes PR diffs and leaves comments with explanations and fix suggestions.”
   • [community] “I've witnessed numerous instances where either the cursor bugbot or Claude has found a bug and recommended a reasonable fix. The fix has bee…”
   • [community] “Do you have actual experience with bugbot? Its live in our org and is actually pretty good, almost none of its comments are frivolous or wro…”
   • [community] “I assume that this is the same as when Cursor spontaneously decides to show code review comments in the IDE as part of some upsell? In that …”
   • [community] “I've found Bugbot to be shockingly effective at finding bugs in my PRs. Even when it's wrong, it's usually worth adding a comment, since it'…”

   proof ↗⚑ flag

   cubic✓fullcommunity7/10

   Cubic's docs explicitly claim to catch logic errors, bugs, and security vulnerabilities (not just style), with deep Ultrareview passes for complex refactors, and one independent HN commenter corroborates that it 'provides more technical explanations than just basic checks' and is 'really powerful.' However, race conditions and specific edge-case handling are not explicitly evidenced, and most support is vendor documentation rather than hands-on benchmarks. Missing for 10: independent benchmark/hands-on evidence of catching race conditions or subtle logic bugs specifically, broader third-party validation beyond a single HN comment.

   • [claimed-docs] “Spots bugs and improvements: Comments on bugs and improvements in pull requests”
   • [claimed-docs] “The AI automatically scans every pull request for a wide range of issues, including logic errors, style inconsistencies, and potential secur…”
   • [claimed-docs] “When a pull request needs extra scrutiny, you can ask cubic for an Ultrareview.”
   • [claimed-docs] “Ultrareview is cubic's deepest review. It runs a longer, multi-pass analysis using cubic's most capable review models, and typically takes a…”
   • [community] “I really liked it - it hit the mark. The current balance works very well, and it genuinely surprised me. It provides more technical explanat…”

   proof ↗⚑ flag

Learning

1. developerPush back on a bad review comment and the reviewer learns — it stops repeating the same rejected feedback

   weight 2 · round to cubic
   Cursor Bugbot~partialcommunity4/10

   Docs show Bugbot reads existing PR comments (top-level and inline) to avoid duplicate suggestions and build on prior feedback, which implies some memory of prior review context within a single PR thread, and BUGBOT.md lets teams codify guidelines to steer future reviews. However, there's no evidence of a persistent learning mechanism where a developer's explicit pushback/rejection on a specific comment is remembered and stops the same feedback from recurring across PRs — community reports actually describe the opposite pattern (bot re-arguing or repeating flagged issues), and one commenter explicitly disliked its persistent review comments. missing for 10: explicit mechanism for marking a comment 'rejected' and suppressing future repeats, cross-PR memory of developer pushback, hands-on confirmation that pushback changes future behavior.

   • [claimed-docs] “Uses existing PR comments as context: reads connected PR comments (top-level and inline) to avoid duplicate suggestions and build on prior f…”
   • [claimed-docs] “Create `.cursor/BUGBOT.md` files in your repository to give Bugbot project-specific review guidelines.”
   • [community] “I've witnessed numerous instances where either the cursor bugbot or Claude has found a bug and recommended a reasonable fix. The fix has bee…”
   • [community] “I assume that this is the same as when Cursor spontaneously decides to show code review comments in the IDE as part of some upsell? In that …”

   proof ↗⚑ flag

   cubic✓fullcommunity7/10

   cubic explicitly documents that replying to its comments teaches it 'what to do differently' and it 'remembers for next time,' with learning drawn from direct feedback and thumbs up/down reactions plus senior engineers' review patterns — directly matching the story of pushing back and the reviewer not repeating rejected feedback. However, this is entirely first-party documentation with no independent/hands-on confirmation that the learning actually persists or stops repeat comments in practice; one community comment expresses general skepticism about YAML-based rule interpretation but doesn't concretely show the learning failing. Missing for 10: independent hands-on verification that cubic stops repeating rejected feedback, and details on how long/broadly the learned preference applies.

   • [claimed-docs] “cubic automatically learns when you: Reply to its comments... React to suggestions: Thumbs up/down help cubic calibrate what's useful vs noi…”
   • [claimed-docs] “Reply to its comments: Type a response explaining what cubic should do differently, and it remembers for next time”
   • [claimed-docs] “React to suggestions: Thumbs up/down help cubic calibrate what's useful vs noise for your specific codebase”
   • [claimed-docs] “cubic learns your team's unwritten rules from two sources: direct feedback on its comments, and patterns extracted from your senior engineer…”
   • [community] “The 'in-codebase' approach is the right one, but a YAML file with plain text is a half-measure. The most reliable rule that 'lives next to t…”

   proof ↗⚑ flag

Noise

1. engineering leadThe reviewer keeps noise low — few false positives, deduplicated comments, severity labels — so my team doesn't tune it out

   weight 3 · round to cubic
   Cursor Bugbot~partialcommunity5/10

   Docs show dedup mechanisms (reading existing PR comments to avoid duplicate suggestions), configurable project rules via BUGBOT.md, and verbose mode showing which rules fired — all noise-reduction levers. But there's no evidence of severity labels, and community reports are split: some engineers report Bugbot is 'shockingly effective' with 'almost none of its comments frivolous or wrong', while others report frivolous/wrong comments and one lead disabled auto-review after Bugbot argued against its own fix. Missing for 10: explicit severity-label feature, and consistent independent confirmation of low false-positive rate.

   • [claimed-docs] “Uses existing PR comments as context: reads connected PR comments (top-level and inline) to avoid duplicate suggestions and build on prior f…”
   • [claimed-docs] “Create `.cursor/BUGBOT.md` files in your repository to give Bugbot project-specific review guidelines.”
   • [claimed-docs] “Comment `cursor review verbose=true` or `bugbot run verbose=true` on the PR for detailed logs, which Bugbot rules loaded, and a request ID”
   • [community] “I've witnessed numerous instances where either the cursor bugbot or Claude has found a bug and recommended a reasonable fix. The fix has bee…”
   • [community] “Do you have actual experience with bugbot? Its live in our org and is actually pretty good, almost none of its comments are frivolous or wro…”
   • [community] “I assume that this is the same as when Cursor spontaneously decides to show code review comments in the IDE as part of some upsell? In that …”
   • [community] “I've found Bugbot to be shockingly effective at finding bugs in my PRs. Even when it's wrong, it's usually worth adding a comment, since it'…”

   proof ↗⚑ flag

   cubic~partialcommunity6/10

   cubic documents concrete noise-reduction mechanisms: it learns from thumbs-up/down and reply feedback to calibrate 'what's useful vs noise' (cubic-docs-10, cubic-docs-32/33), learns unwritten rules from senior engineers' historical reviews (cubic-docs-54), supports ignore patterns/custom agents via cubic.yaml (cubic-docs-11), and auto-resolves threads once issues are fixed (cubic-docs-20). One community reviewer corroborates quality/technical depth (cubic-comm-1), while another raises skepticism about YAML-based rule reliability (cubic-comm-2), though this doesn't concretely contradict the noise-reduction claims. Missing for 10: explicit severity labeling of comments, explicit deduplication-of-comments mechanism, and independent data/benchmarks on false-positive rates.

   • [claimed-docs] “cubic automatically learns when you: Reply to its comments... React to suggestions: Thumbs up/down help cubic calibrate what's useful vs noi…”
   • [claimed-docs] “Auto-resolve threads: Enable automatic thread resolution to close findings when the issue is fixed”
   • [claimed-docs] “Reply to its comments: Type a response explaining what cubic should do differently, and it remembers for next time”
   • [claimed-docs] “React to suggestions: Thumbs up/down help cubic calibrate what's useful vs noise for your specific codebase”
   • [claimed-docs] “cubic learns your team's unwritten rules from two sources: direct feedback on its comments, and patterns extracted from your senior engineer…”
   • [claimed-docs] “`cubic.yaml` lives in the root of your repository and becomes the source of truth for AI review behavior, ignore patterns, PR descriptions, …”
   • [community] “I really liked it - it hit the mark. The current balance works very well, and it genuinely surprised me. It provides more technical explanat…”
   • [community] “The 'in-codebase' approach is the right one, but a YAML file with plain text is a half-measure. The most reliable rule that 'lives next to t…”

   proof ↗⚑ flag

Security

1. security engineerReviews flag security problems in the diff — injection risks, leaked secrets, insecure patterns — alongside functional bugs

   weight 2 · round to Cursor Bugbot
   Cursor Bugbot✓fullprobed8/10

   Docs explicitly state Bugbot analyzes PRs for 'bugs, security vulnerabilities, and code quality issues' with inline comments and fix suggestions, directly matching the security-plus-functional review scope described; community evidence corroborates it catches genuine bugs (though some skepticism about accuracy exists). missing for 10: no explicit named example of catching leaked secrets or injection specifically, and no independent benchmark isolating security-issue detection accuracy.

   • [claimed-docs] “It analyzes every pull request for bugs, security vulnerabilities, and code quality issues, leaving inline comments with explanations and su…”
   • [claimed-docs] “Bugbot analyzes PR diffs and leaves comments with explanations and fix suggestions.”
   • [probe] “PROBE docs-md: HTTP 200 at https://cursor.com/docs/bugbot.md # Bugbot Bugbot reviews pull requests and identifies bugs, security issues, an…”
   • [community] “Do you have actual experience with bugbot? Its live in our org and is actually pretty good, almost none of its comments are frivolous or wro…”
   • [community] “I've found Bugbot to be shockingly effective at finding bugs in my PRs. Even when it's wrong, it's usually worth adding a comment, since it'…”

   proof ↗⚑ flag

   cubic~partialcommunity6/10

   cubic docs explicitly claim it scans PRs for 'security vulnerabilities' alongside logic errors and style issues, and offers an 'Ultrareview' deep-pass mode explicitly recommended for security-sensitive changes, plus custom agents to enforce org-specific rules. However, there's no documented evidence of specific detection categories like secret leakage or injection-pattern examples, nor independent/hands-on evidence confirming accuracy on real security bugs (community quotes address general usefulness, not security-specific findings). Missing for 10: explicit mention of secret-scanning/injection-detection categories, and independent verification of security-finding accuracy.

   • [claimed-docs] “The AI automatically scans every pull request for a wide range of issues, including logic errors, style inconsistencies, and potential secur…”
   • [claimed-docs] “When a pull request needs extra scrutiny, you can ask cubic for an Ultrareview.”
   • [claimed-docs] “Ultrareview is cubic's deepest review. It runs a longer, multi-pass analysis using cubic's most capable review models, and typically takes a…”
   • [claimed-docs] “Custom agents are review rules that enforce your organization's specific best practices across pull requests.”
   • [community] “I really liked it - it hit the mark. The current balance works very well, and it genuinely surprised me. It provides more technical explanat…”

   proof ↗⚑ flag

Cli

1. developerI run reviews from a CLI against local diffs or in CI scripts, with machine-readable output my tooling can consume

   weight 2 · round to cubic
   Cursor Bugbot—none0/10

   Bugbot is documented exclusively as a PR-comment-triggered reviewer integrated with GitHub/GitLab/Bitbucket/Azure DevOps, posting inline PR comments — there is no mention of a CLI, local-diff scanning, or machine-readable (JSON/SARIF) output for CI script consumption anywhere in the evidence. Missing for 10: any CLI binary/command, local diff support, structured/machine-readable output format, or CI-script-oriented API.

   • [claimed-docs] “Manual trigger by commenting `cursor review` or `bugbot run` on any PR”
   • [claimed-docs] “It analyzes every pull request for bugs, security vulnerabilities, and code quality issues, leaving inline comments with explanations and su…”
   • [claimed-docs] “Bugbot analyzes PR diffs and leaves comments with explanations and fix suggestions.”
   • [claimed-docs] “GitHub (including GitHub Enterprise Server): See the GitHub integration page”
   • [claimed-docs] “GitLab (including GitLab Self-Hosted): See the GitLab integration page”

   proof ↗⚑ flag

   cubic~partialprobed5/10

   cubic ships an official CLI (`cubic-docs-7`, `cubic-probe-5`) that reviews local diffs before push and outputs a prompt for a coding agent to fix issues, satisfying the 'local diff' half of the story. However there is no documented evidence of CI-specific usage (e.g., a CI mode/flag) or of structured machine-readable output (JSON/SARIF) that external tooling could consume — the CLI output is described as a natural-language prompt, not a machine-parseable format. missing for 10: CI integration docs/flags, machine-readable (JSON/SARIF) output format, examples of scripting/tooling consumption.

   • [claimed-docs] “The **cubic CLI** reviews local changes before you push. It finds bugs and generates a prompt that your coding agent can use to fix them.”
   • [probe] “official CLI documented at https://docs.cubic.dev/ide/cli-review”

   proof ↗⚑ flag

Ide

1. developerI get the same review inside my IDE before I push, catching issues while the code is still in my editor

   weight 2 · round to cubic
   Cursor Bugbot—none0/10

   All documentation describes Bugbot as a PR-based reviewer that runs on GitHub/GitLab/Bitbucket/Azure DevOps pull requests (post-push), triggered by PR updates or PR comments, not as an in-editor pre-push check. 'Fix in Cursor' links merely open already-found PR issues in the IDE for fixing, which happens after the code has already been pushed, contradicting the story's requirement of catching issues before pushing.

   • [claimed-docs] “Runs automatic reviews on every PR update”
   • [claimed-docs] “It analyzes every pull request for bugs, security vulnerabilities, and code quality issues, leaving inline comments with explanations and su…”
   • [claimed-docs] “Fix in Cursor links open issues directly in Cursor”
   • [claimed-docs] “Bugbot analyzes PR diffs and leaves comments with explanations and fix suggestions.”

   proof ↗⚑ flag

   cubic✓fullprobed7/10

   cubic ships a dedicated CLI that "reviews local changes before you push. It finds bugs and generates a prompt that your coding agent can use to fix them" (cubic-docs-7, cubic-probe-5), plus IDE/agent integration via cubic skills and an MCP server that lets coding agents read review findings and codebase context (cubic-docs-8, cubic-docs-35, cubic-probe-4), directly matching the story of catching issues pre-push in the editor. Missing for 10: independent/hands-on validation of the CLI's pre-push review quality and no community evidence specifically confirming the IDE experience (community citations discuss PR-level review, not the local CLI).

   • [claimed-docs] “The **cubic CLI** reviews local changes before you push. It finds bugs and generates a prompt that your coding agent can use to fix them.”
   • [claimed-docs] “Connect cubic's MCP server to your coding agent to read review findings and codebase context, request PR reviews, and triage PR or codebase …”
   • [claimed-docs] “Install and connect cubic in Cursor, Claude Code, VS Code, Codex, Gemini CLI, or another coding tool.”
   • [claimed-docs] “cubic skills give your coding agent instructions for reviewing code, handling PR comments, and using your team's codebase context.”
   • [probe] “official MCP server documented at https://docs.cubic.dev/ide/mcp-server”
   • [probe] “official CLI documented at https://docs.cubic.dev/ide/cli-review”

   proof ↗⚑ flag

Config

1. engineering leadI configure the reviewer with a versioned config file in my repo — path filters, per-path instructions, review profiles

   weight 3 · round to cubic
   Cursor Bugbot~partialclaimed5/10

   Bugbot supports a versioned `.cursor/BUGBOT.md` file for project-specific review guidelines, plus org-wide rules via Bugbot Automations and natural-language effort-level instructions, giving some per-repo/per-instruction configurability. However, there's no evidence of path-based filters, distinct 'review profiles', or per-path (as opposed to per-repo) instruction targeting within the config file. missing for 10: explicit path/glob filtering, multiple named review profiles, per-path instruction scoping, independent confirmation of BUGBOT.md schema/capabilities.

   • [claimed-docs] “Create `.cursor/BUGBOT.md` files in your repository to give Bugbot project-specific review guidelines.”
   • [claimed-docs] “Team admins can also create organization-wide rules in [Bugbot Automations](https://cursor.com/automations/from-cursor/bugbot).”
   • [claimed-docs] “Describe in natural language when Bugbot should use low, default, or high effort. Cursor will dynamically set effort levels based on your in…”
   • [claimed-docs] “Smart: Describe in natural language when Bugbot should use low, default, or high effort. Cursor will dynamically set effort levels based on …”

   proof ↗⚑ flag

   cubic✓fullcommunity7/10

   cubic.yaml is documented as a versioned, repo-root config file that is the 'source of truth for AI review behavior, ignore patterns, PR descriptions, and custom agents,' directly covering path filters (ignore patterns) and review profiles (custom agents, Ultrareview). Custom context files (README.md, AGENTS.md, .cursorrules, .ai/ dirs) further support per-path/contextual instructions. missing for 10: an explicit documented example of per-path instruction syntax within cubic.yaml, and independent/hands-on verification of the config file working as described (one community comment even questions whether YAML-based rules are as robust as code-based checks).

   • [claimed-docs] “`cubic.yaml` lives in the root of your repository and becomes the source of truth for AI review behavior, ignore patterns, PR descriptions, …”
   • [claimed-docs] “cubic.yaml lives in the root of your repository and becomes the source of truth for AI review behavior, ignore patterns, PR descriptions, an…”
   • [claimed-docs] “Custom agents are review rules that enforce your organization's specific best practices across pull requests.”
   • [claimed-docs] “Custom agents: Enforce your team's coding standards”
   • [claimed-docs] “cubic automatically detects and uses context files in your repository, including `README.md`, `context.md`, `AGENTS.md`, `.cursorrules`”
   • [claimed-docs] “cubic automatically detects and uses context files in your repository, including `README.md`, `context.md`, `AGENTS.md`, `.cursorrules`, age…”
   • [community] “The 'in-codebase' approach is the right one, but a YAML file with plain text is a half-measure. The most reliable rule that 'lives next to t…”

   proof ↗⚑ flag

Governance

1. engineering leadI roll out org-level review defaults across hundreds of repos and manage exceptions centrally

   weight 1 · round drawn
   Cursor Bugbot~partialclaimed5/10

   Cursor supports org/team-level rollout via Bugbot Teams (all-PR reviews, analytics, effort controls) and 'organization-wide rules' via Bugbot Automations, plus per-repo BUGBOT.md guideline files, giving a centralized-defaults mechanism. However there's no evidence of exception management at scale (e.g., per-repo overrides, exemption lists, staged rollout across hundreds of repos) or admin tooling for auditing/enforcing defaults across a large repo fleet. Missing for 10: documented per-repo exception/override workflow, evidence of scaling to hundreds of repos, and admin audit/reporting on rule adherence across the org.

   • [claimed-docs] “Bugbot Teams includes code reviews on all PRs, analytics and reporting, effort level controls, and advanced rules and settings.”
   • [claimed-docs] “Team admins can also create organization-wide rules in [Bugbot Automations](https://cursor.com/automations/from-cursor/bugbot).”
   • [claimed-docs] “Create `.cursor/BUGBOT.md` files in your repository to give Bugbot project-specific review guidelines.”
   • [claimed-docs] “You can enable usage-based billing for reviews on all PRs.”

   proof ↗⚑ flag

   cubic~partialclaimed5/10

   cubic.yaml provides per-repo config (source of truth for review behavior, ignore patterns, custom agents) and custom agents/RBAC roles suggest some centralized governance, but evidence shows configuration is per-repository (cubic.yaml lives in each repo root) rather than an org-level policy pushed/enforced across hundreds of repos with a central exceptions dashboard. missing for 10: an org-wide policy/template propagation mechanism across many repos, a central exceptions-management UI/workflow, and independent evidence of usage at hundreds-of-repos scale.

   • [claimed-docs] “`cubic.yaml` lives in the root of your repository and becomes the source of truth for AI review behavior, ignore patterns, PR descriptions, …”
   • [claimed-docs] “cubic.yaml lives in the root of your repository and becomes the source of truth for AI review behavior, ignore patterns, PR descriptions, an…”
   • [claimed-docs] “Custom agents are review rules that enforce your organization's specific best practices across pull requests.”
   • [claimed-docs] “cubic uses a role-based access control system to manage who can make changes to your team's subscription and settings. Every team member has…”
   • [claimed-docs] “Custom agents: Enforce your team's coding standards”

   proof ↗⚑ flag

Rules

1. engineering leadI encode my team's own review guidelines — natural-language rules, AST patterns, or linked style guides — and the reviewer enforces them

   weight 2 · round to Cursor Bugbot
   Cursor Bugbot✓fullclaimed7/10

   Bugbot supports project-specific natural-language review guidelines via .cursor/BUGBOT.md files, org-wide rules via Bugbot Automations, and verbose mode to show which rules were applied. missing for 10: no evidence of AST-pattern-based rule definitions, no support for linking external style guide documents, and no independent/hands-on verification of how well custom guidelines are actually enforced in practice.

   • [claimed-docs] “Create `.cursor/BUGBOT.md` files in your repository to give Bugbot project-specific review guidelines.”
   • [claimed-docs] “Comment `bugbot run verbose=true` or `cursor review verbose=true` on the pull request. Bugbot replies with a table of the rules included in …”
   • [claimed-docs] “Team admins can also create organization-wide rules in [Bugbot Automations](https://cursor.com/automations/from-cursor/bugbot).”
   • [claimed-docs] “Comment `cursor review verbose=true` or `bugbot run verbose=true` on the PR for detailed logs, which Bugbot rules loaded, and a request ID”
   • [claimed-docs] “Bugbot Teams includes code reviews on all PRs, analytics and reporting, effort level controls, and advanced rules and settings.”

   proof ↗⚑ flag

   cubic~partialcommunity7/10

   cubic supports engineering-lead-authored review rules via 'Custom agents' (natural-language rules enforcing team standards), a cubic.yaml as source of truth, auto-detected context files (README, context.md, AGENTS.md, .cursorrules) and cross-repo linking for shared style guides, plus adoption of community rule sets. However, there is no explicit evidence of AST-pattern-based rule authoring, and one community comment expresses skepticism that plain-text/YAML rules are a 'half-measure' versus more robust structural checks, though this is opinion rather than a documented failure. Missing for 10: explicit AST-pattern rule support, independent hands-on validation that custom agents reliably enforce guidelines in practice.

   • [claimed-docs] “Custom agents are review rules that enforce your organization's specific best practices across pull requests.”
   • [claimed-docs] “`cubic.yaml` lives in the root of your repository and becomes the source of truth for AI review behavior, ignore patterns, PR descriptions, …”
   • [claimed-docs] “Custom agents: Enforce your team's coding standards”
   • [claimed-docs] “You can also adopt existing agents from the community library with a single click.”
   • [claimed-docs] “cubic automatically detects and uses context files in your repository, including `README.md`, `context.md`, `AGENTS.md`, `.cursorrules`”
   • [claimed-docs] “cubic automatically detects and uses context files in your repository, including `README.md`, `context.md`, `AGENTS.md`, `.cursorrules`, age…”
   • [claimed-docs] “cubic.yaml lives in the root of your repository and becomes the source of truth for AI review behavior, ignore patterns, PR descriptions, an…”
   • [community] “The 'in-codebase' approach is the right one, but a YAML file with plain text is a half-measure. The most reliable rule that 'lives next to t…”

   proof ↗⚑ flag