Graphite vs Cursor Bugbot

Agent access

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

   weight 2 · round to Cursor Bugbot
   Graphite~partialprobed5/10

   The standard llms.txt at the root domain returns 404, but probes show agent-friendly markdown docs (docs/get-started.md returns 200) that point to a Mintlify-hosted llms index, meaning an agent could be pointed at machine-readable docs via an indirect path rather than a canonical llms.txt. Missing for 10: a working llms.txt at the expected root URL, and clear first-party documentation advertising this llms/agent-doc endpoint as a supported entry point.

   • [probe] “PROBE llms.txt: HTTP 404 at https://graphite.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 200 at https://graphite.com/docs/get-started.md > ## Documentation Index > Fetch the complete documentation index at: ht…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Cursor Bugbot
   Graphite~partialprobed4/10

   Graphite's CLI is git-compatible and configurable (gt config, gt commands) and is scriptable in principle, and features like merge queue/automations suggest some CI-style automation, but there is no explicit documentation of headless/non-interactive CLI flags, CI pipeline examples, or a documented automation API for running Graphite entirely without a human in CI. missing for 10: explicit CI/headless mode docs, non-interactive flag examples, dedicated automation/CI integration guide.

   • [claimed-docs] “The Graphite CLI is fully compatible with git—just install it on an existing repository and begin using our suite of gt commands.”
   • [claimed-docs] “Run gt config to open an interactive menu which lets you configure your Graphite CLI.”
   • [claimed-docs] “The Graphite CLI is a tool to help you break up large engineering tasks into a series of small, incremental code changes directly from the c…”
   • [claimed-docs] “Unlimited AI Reviews * AI Review customizations * Automations * Merge Queue”
   • [probe] “official CLI documented at https://graphite.com/docs/install-the-cli”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Graphite
   Graphite~partialprobed5/10

   Graphite offers a documented CLI (gt commands) and an MCP server (gt-mcp) that let AI/agentic tooling drive the product, but there is no public REST/GraphQL/OpenAPI API — probes for openapi.json/swagger.json all 404. missing for 10: a documented general-purpose public API (REST/GraphQL) with endpoint reference, authentication scopes, and independent/hands-on corroboration of programmatic API usage beyond CLI/MCP.

   • [probe] “PROBE openapi: all candidate paths 404 (https://graphite.com/openapi.json, https://graphite.com/swagger.json, https://graphite.com/api/opena…”
   • [probe] “official MCP server documented at https://graphite.com/docs/gt-mcp”
   • [probe] “official CLI documented at https://graphite.com/docs/install-the-cli”
   • [claimed-docs] “Install the Graphite CLI using either Homebrew or npm”
   • [claimed-docs] “The Graphite CLI is fully compatible with git—just install it on an existing repository and begin using our suite of gt commands.”
   • [claimed-docs] “Run gt config to open an interactive menu which lets you configure your Graphite CLI.”

   proof ↗⚑ flag

   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

4. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Graphite—none0/10

   The only webhook-related evidence describes Graphite *receiving* GitHub webhooks for CI/mergeability updates (graphite-docs-24), not Graphite exposing its own webhook subscription system for external/AI-native consumers to receive events. No documentation of an outbound webhook API, event types, or subscription mechanism is present.

   • [claimed-docs] “Receive GitHub webhooks for real-time updates on CI status, mergeability, and push events.”

   proof ↗⚑ flag

   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

Agentic features

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

   weight 2 · round drawn
   Graphite✓fullcommunity8/10

   Graphite ships AI Reviews that automatically analyze PRs and suggest fixes, a Graphite Chat that summarizes changes, suggests fixes, and explains code context, plus a dedicated 'Insights' feature to measure and optimize developer productivity — all directly generating AI insights/suggestions from repo data. Community feedback largely praises the stacking workflow with only general skepticism about AI additions, not a concrete failure of the insight/suggestion features themselves. Missing for 10: independent hands-on validation specifically of the Insights analytics dashboard and richer detail on what data-driven suggestions it surfaces beyond code review.

   • [claimed-docs] “AI reviews analyze every pull request in your repositories, identifying potential issues and suggesting fixes instantly - no manual configur…”
   • [claimed-docs] “Ask for suggested fixes and apply them in one click right from the review page.”
   • [claimed-docs] “InsightsMeasure and optimize your team's developer productivity.”
   • [claimed-docs] “Get immediate, actionable feedback with Graphite’s codebase-aware AI code review agent.”
   • [claimed-docs] “Ask Graphite to explain what changed in a pull request, highlight potential issues, or provide context about specific code sections.”
   • [claimed-docs] “Get help understanding and implementing feedback from your teammates and reviewers.”
   • [community] “This is annoying, Graphite's core feature of stacked PRs is really good despite all the AI things they've added around their review UI. I do…”
   • [community] “i mentioned a few months ago that it was a shame where graphite was headed re: AI... this appears to be the final nail in the original produ…”

   proof ↗⚑ flag

   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

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

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

   Graphite documents automation that runs without manual intervention: AI review agent automatically reviews all new PRs once enabled (graphite-docs-18, graphite-docs-19) and a stack-aware merge queue that lands PRs in the background (graphite-docs-10), plus Agents that autonomously generate PRs from a prompt (graphite-docs-12). This is real background automation, but scoped narrowly to PR review/merge events rather than a general-purpose 'set up any automation' framework with custom triggers/scheduling. Missing for 10: evidence of configurable triggers/schedules beyond PR events, and independent/hands-on confirmation that these automations reliably run unattended over time.

   • [claimed-docs] “AI reviews can be enabled in just a few clicks, with no configuration required to start catching bugs in your pull requests.”
   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”
   • [claimed-docs] “Our stack-aware merge queue lands PRs in order and keeps branches green, helping you gain momentum.”
   • [claimed-docs] “Describe what you want built or fixed in plain language, and Agents will pull context from your repository, generate the changes, and open a…”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Graphite
   Graphite✓fullcommunity8/10

   Graphite documents two built-in AI assistant surfaces: 'Graphite Agents' that take plain-language task descriptions, pull repo context, generate changes, and open a draft PR (graphite-docs-12, graphite-docs-22), and 'Graphite Chat' that can be asked to summarize PRs, suggest/apply fixes, and diagnose CI failures (graphite-docs-6/7/8/15/21) — directly matching task delegation to a built-in assistant. Community evidence shows real usage of Graphite generally but is skeptical/critical of the AI additions rather than confirming hands-on success (graphite-comm-10, graphite-comm-13), so independent corroboration of the delegation flow itself is thin. Missing for 10: independent/hands-on verification that Agents reliably complete delegated tasks end-to-end, and detail on failure modes.

   • [claimed-docs] “Describe what you want built or fixed in plain language, and Agents will pull context from your repository, generate the changes, and open a…”
   • [claimed-docs] “Make direct code changes right from your PR page. Click Agent on the right side of the PR to get started.”
   • [claimed-docs] ““Summarize the changes in this PR””
   • [claimed-docs] “Ask for suggested fixes and apply them in one click right from the review page.”
   • [claimed-docs] “Diagnose and resolve failing checks directly from your PR page with full context from your CI results.”
   • [claimed-docs] “Find related files, understand dependencies, and get context from other PRs without switching tabs.”
   • [claimed-docs] “Ask Graphite to explain what changed in a pull request, highlight potential issues, or provide context about specific code sections.”
   • [community] “This is annoying, Graphite's core feature of stacked PRs is really good despite all the AI things they've added around their review UI. I do…”
   • [community] “i mentioned a few months ago that it was a shame where graphite was headed re: AI... this appears to be the final nail in the original produ…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Graphite
   Graphite✓fullclaimed7/10

   Graphite Chat lets users ask natural-language questions and request fixes ('Summarize the changes', 'Ask for suggested fixes and apply them in one click'), and Graphite Agents let users 'describe what you want built or fixed in plain language' to generate a draft PR — both are documented natural-language interaction surfaces layered on top of the core git/CLI workflow. Missing for 10: independent/hands-on corroboration that NL commands reliably work in practice (community evidence focuses on the CLI stacking workflow, not the NL chat/agent features) and clarity on how much of daily operation still requires explicit `gt` CLI commands rather than NL.

   • [claimed-docs] ““Summarize the changes in this PR””
   • [claimed-docs] “Ask for suggested fixes and apply them in one click right from the review page.”
   • [claimed-docs] “Diagnose and resolve failing checks directly from your PR page with full context from your CI results.”
   • [claimed-docs] “Describe what you want built or fixed in plain language, and Agents will pull context from your repository, generate the changes, and open a…”
   • [claimed-docs] “Ask Graphite to explain what changed in a pull request, highlight potential issues, or provide context about specific code sections.”
   • [claimed-docs] “Make direct code changes right from your PR page. Click Agent on the right side of the PR to get started.”
   • [claimed-docs] “With Graphite Chat, you can ask for context on code changes, get instant feedback, and make edits directly from the chat interface without l…”

   proof ↗⚑ flag

   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

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 Graphite
   Graphite~partialcommunity6/10

   Graphite's AI reviews automatically scan every PR with no configuration, offer custom rules/comment exclusions, and GT MCP explicitly supports breaking large AI-agent-generated changes into reviewable stacked PRs — directly addressing reviewing agent-authored code. However, evidence is entirely first-party docs with no independent benchmarking of review accuracy/volume specifically for AI-generated code, and community commentary shows some skepticism about the direction of AI features (though not a concrete failure report). Missing for 10: independent/hands-on validation of review quality at scale on AI-authored PRs specifically, and any metrics on catch-rate or false-positive rate.

   • [claimed-docs] “AI reviews analyze every pull request in your repositories, identifying potential issues and suggesting fixes instantly - no manual configur…”
   • [claimed-docs] “AI reviews can be enabled in just a few clicks, with no configuration required to start catching bugs in your pull requests.”
   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”
   • [claimed-docs] “AI reviews powered by Graphite Agent help your team build better software by automatically reviewing pull requests and catching bugs before …”
   • [claimed-docs] “GT MCP allows AI agents to automatically create stacked PRs, breaking down large AI-generated changes into smaller, reviewable stacked pull …”
   • [claimed-docs] “Custom rules allow you to define explicit guidelines for Graphite Agent to follow when reviewing your code.”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should not leave comments.”
   • [community] “i mentioned a few months ago that it was a shame where graphite was headed re: AI... this appears to be the final nail in the original produ…”

   proof ↗⚑ flag

   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

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 Cursor Bugbot
   Graphite~partialclaimed5/10

   Graphite Agent supports 'Custom rules' where users define plain-language guidelines for the AI reviewer to follow on every PR (graphite-docs-5, graphite-docs-20/28), and AI reviews run automatically on all PRs with no configuration (graphite-docs-18/19). However, these are review comments/guidelines, not documented as blocking, pass/fail 'checks' that gate merge like a CI status (e.g., 'docs updated' or 'tests cover new paths' as enforced gates) — the merge queue and check-diagnosis features are separate from these custom rules. Missing for 10: explicit documentation of custom rules acting as blocking/required pre-merge gates rather than advisory review comments, and examples matching the exact 'docs updated'/'tests cover new paths' framing.

   • [claimed-docs] “Custom rules allow you to define explicit guidelines for Graphite Agent to follow when reviewing your code.”
   • [claimed-docs] “AI reviews can be enabled in just a few clicks, with no configuration required to start catching bugs in your pull requests.”
   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should not leave comments.”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should **not** leave comments.”
   • [claimed-docs] “Unlimited AI Reviews * AI Review customizations * Automations * Merge Queue”

   proof ↗⚑ flag

   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

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

   Docs explicitly describe applying AI-suggested fixes in one click from the PR review page and making direct agent-driven code changes without leaving the PR (docs-7, docs-22), plus diagnosing/resolving failing checks in-PR (docs-8). This directly matches the story of turning a review finding into an applied fix in-place. Missing for 10: independent/hands-on corroboration of the one-click apply-fix and in-PR agent edit flow (community evidence only covers stacking, not this AI-fix feature), and no detail on how committed-patch fixes are verified/tested post-apply.

   • [claimed-docs] “Ask for suggested fixes and apply them in one click right from the review page.”
   • [claimed-docs] “Make direct code changes right from your PR page. Click Agent on the right side of the PR to get started.”
   • [claimed-docs] “Diagnose and resolve failing checks directly from your PR page with full context from your CI results.”
   • [claimed-docs] “Describe what you want built or fixed in plain language, and Agents will pull context from your repository, generate the changes, and open a…”

   proof ↗⚑ flag

   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

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 Cursor Bugbot
   Graphite~partialprobed5/10

   Graphite offers its own Agent that applies suggested fixes in one click and opens draft PRs from review feedback, plus a GT MCP server that lets external AI agents interact with Graphite to create stacked PRs — this provides a form of agent handoff. However, there is no explicit documentation of copyable fix prompts or named integrations with Claude Code, Cursor, or Codex; the flow relies on Graphite's own in-house Agent or generic MCP tooling rather than a documented direct connector to those specific coding agents. Missing for 10: explicit copyable fix-prompt format, named integration/setup docs for Claude Code/Cursor/Codex, and independent evidence such handoffs work in practice.

   • [claimed-docs] “Ask for suggested fixes and apply them in one click right from the review page.”
   • [claimed-docs] “Make direct code changes right from your PR page. Click Agent on the right side of the PR to get started.”
   • [claimed-docs] “GT MCP allows AI agents to automatically create stacked PRs, breaking down large AI-generated changes into smaller, reviewable stacked pull …”
   • [probe] “official MCP server documented at https://graphite.com/docs/gt-mcp”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Graphite
   Graphite~partialcommunity6/10

   Graphite's CLI and stacking model let users manipulate many branches/PRs at once (community confirms 'rebase multiple branches at the same time'), the merge queue lands multiple PRs in order, and cross-repo PR tracking/AI review runs across all PRs in a repo automatically. However, the AI/agent features (Graphite Agent, chat, fix suggestions) are documented as per-PR actions, not as a bulk/batch operation across many items simultaneously. Missing for 10: explicit bulk AI-agent operations (e.g., batch-generate or batch-fix across many PRs/repos in one command), and independent evidence of scale beyond git-stack rebasing.

   • [claimed-docs] “Our stack-aware merge queue lands PRs in order and keeps branches green, helping you gain momentum.”
   • [claimed-docs] “Stay up-to-date with PRs across many repos using custom filters and rules.”
   • [community] “Ive been using it since mote than a year and it has become part of my toolbelt. Especially the cli that allow to seemlessly rebase multiple …”
   • [claimed-docs] “AI reviews analyze every pull request in your repositories, identifying potential issues and suggesting fixes instantly - no manual configur…”
   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”

   proof ↗⚑ flag

   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

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

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

   Graphite ships some rule/event-driven automation: AI review auto-triggers on new PRs with no configuration (docs-19, docs-18), custom rules constrain when the review agent comments (docs-5, docs-20, docs-28), and a named 'Automations' feature appears in pricing (docs-33) alongside webhook-driven CI/merge event handling (docs-24) and stack-aware merge queue automation (docs-10). However, there is no dedicated documentation describing a general-purpose rules engine where a user defines arbitrary event→action triggers beyond PR-review and merge behaviors. Missing for 10: dedicated docs for the 'Automations' feature explaining supported trigger events/actions, evidence of custom/arbitrary action definitions beyond review-comment suppression, and independent confirmation of automation reliability.

   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”
   • [claimed-docs] “AI reviews can be enabled in just a few clicks, with no configuration required to start catching bugs in your pull requests.”
   • [claimed-docs] “Custom rules allow you to define explicit guidelines for Graphite Agent to follow when reviewing your code.”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should not leave comments.”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should **not** leave comments.”
   • [claimed-docs] “Unlimited AI Reviews * AI Review customizations * Automations * Merge Queue”
   • [claimed-docs] “Receive GitHub webhooks for real-time updates on CI status, mergeability, and push events.”
   • [claimed-docs] “Our stack-aware merge queue lands PRs in order and keeps branches green, helping you gain momentum.”

   proof ↗⚑ flag

   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

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Graphite—none0/10

   No evidence of any scheduling, cron-like, or recurring job/workflow capability; Graphite's automation is event-triggered (PR opened, review requested) via AI reviews, merge queue, and MCP-driven agent actions, not time-based recurring jobs. Missing for 10: any documentation of scheduled/recurring triggers, cron syntax, or periodic workflow execution.

   ⚑ flag

   Cursor Bugbot—none0/10

   Bugbot's docs describe event-triggered reviews (automatic on PR update, or manual comment trigger) and org-wide 'Automations' rules, but there is no evidence of true recurring/scheduled job execution (e.g., cron-like or time-based triggers) as opposed to PR-event triggers.

   • [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).”

   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 Graphite
   Graphite~partialclaimed4/10

   Graphite offers cross-repo PR tracking with custom filters (docs-11) and a codebase-aware AI reviewer that pulls related files/dependencies/context from other PRs (docs-15, docs-16), which helps a lead follow changes broadly, but there is no evidence of explicit monorepo-scale review tooling, cross-repo stack visualization, or dependency mapping across repositories in a single coherent review flow. Missing for 10: monorepo-specific review features, cross-repo diff/stack visualization, and independent evidence that reviewers actually use it to understand large or multi-repo spans coherently.

   • [claimed-docs] “Stay up-to-date with PRs across many repos using custom filters and rules.”
   • [claimed-docs] “Find related files, understand dependencies, and get context from other PRs without switching tabs.”
   • [claimed-docs] “Get immediate, actionable feedback with Graphite’s codebase-aware AI code review agent.”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Graphite
   Graphite✓fullclaimed7/10

   Graphite's AI review docs explicitly claim a 'codebase-aware AI code review agent' (docs-16) and Graphite Chat can 'find related files, understand dependencies, and get context from other PRs without switching tabs' (docs-15) plus explain code sections and highlight issues with repo context (docs-21), directly supporting whole-repo-aware review beyond the diff. Missing for 10: independent/hands-on validation that reviews actually surface call sites and existing conventions (not just vendor claims), and no explicit mention of 'existing conventions' detection.

   • [claimed-docs] “Get immediate, actionable feedback with Graphite’s codebase-aware AI code review agent.”
   • [claimed-docs] “Find related files, understand dependencies, and get context from other PRs without switching tabs.”
   • [claimed-docs] “Ask Graphite to explain what changed in a pull request, highlight potential issues, or provide context about specific code sections.”
   • [claimed-docs] “AI reviews analyze every pull request in your repositories, identifying potential issues and suggesting fixes instantly - no manual configur…”

   proof ↗⚑ flag

   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

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 drawn
   Graphite~partialclaimed4/10

   Graphite lets teams define persistent 'custom rules' and comment exclusions that the AI reviewer follows across future PRs, which is a form of encoded team convention (graphite-docs-5, graphite-docs-20), and AI reviews run automatically without reconfiguration per PR (graphite-docs-19). However, there is no evidence this memory is built from or updates based on past review decisions/outcomes—rules must be manually authored, not learned—so the 'past review decisions' half of the story is unsupported. missing for 10: evidence of automatic learning from historical review decisions, evidence of memory evolving over time without manual rule-writing, independent confirmation that custom rules persist and are applied consistently across many PRs.

   • [claimed-docs] “Custom rules allow you to define explicit guidelines for Graphite Agent to follow when reviewing your code.”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should not leave comments.”
   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”
   • [claimed-docs] “AI reviews analyze every pull request in your repositories, identifying potential issues and suggesting fixes instantly - no manual configur…”

   proof ↗⚑ flag

   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

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

   Graphite Chat is documented to let developers ask questions, get explanations of changes, request suggested fixes, get help implementing reviewer feedback, and diagnose CI issues directly from the PR page in context — matching the interaction story closely (graphite-docs-6,7,8,15,21,29,35). Missing for 10: independent/hands-on user testimony specifically validating Graphite Chat's conversational quality (community evidence covers CLI/stacking, not chat interactions), and no detail on command-issuing reliability via replies.

   • [claimed-docs] ““Summarize the changes in this PR””
   • [claimed-docs] “Ask for suggested fixes and apply them in one click right from the review page.”
   • [claimed-docs] “Diagnose and resolve failing checks directly from your PR page with full context from your CI results.”
   • [claimed-docs] “Find related files, understand dependencies, and get context from other PRs without switching tabs.”
   • [claimed-docs] “Ask Graphite to explain what changed in a pull request, highlight potential issues, or provide context about specific code sections.”
   • [claimed-docs] “With Graphite Chat, you can ask for context on code changes, get instant feedback, and make edits directly from the chat interface without l…”
   • [claimed-docs] “Get help understanding and implementing feedback from your teammates and reviewers.”

   proof ↗⚑ flag

   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

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
   Graphite~partialclaimed4/10

   Graphite lets teams turn AI review on per selected repository and use custom rules/comment exclusions to shape what the Agent flags (graphite-docs-19, graphite-docs-5, graphite-docs-20), giving some control over when/where the bot comments. However there is no documented ability to skip draft PRs, trigger a review on demand, or filter specifically by branch or label as the story requires. Missing for 10: draft-PR skip toggle, on-demand/manual trigger command, and branch/label-based filtering rules.

   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”
   • [claimed-docs] “Custom rules allow you to define explicit guidelines for Graphite Agent to follow when reviewing your code.”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should not leave comments.”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should **not** leave comments.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Graphite
   Graphite~partialprobed4/10

   Graphite ships a git-compatible CLI (`gt` commands) covering the core stacking workflow and an MCP server that lets AI agents create stacked PRs programmatically, but there is no documented public REST/GraphQL API (openapi probe returned 404 on all candidate paths) covering UI-only features like AI review customization, Insights, merge queue configuration, or Graphite Chat — these appear web/GUI-only. missing for 10: a documented general-purpose API or OpenAPI spec exposing AI reviews, custom rules, insights, and merge queue equivalently to the UI; evidence that MCP/CLI cover the full breadth of UI functionality rather than just stacking.

   • [claimed-docs] “The Graphite CLI is fully compatible with git—just install it on an existing repository and begin using our suite of gt commands.”
   • [claimed-docs] “The Graphite CLI is a tool to help you break up large engineering tasks into a series of small, incremental code changes directly from the c…”
   • [claimed-docs] “GT MCP allows AI agents to automatically create stacked PRs, breaking down large AI-generated changes into smaller, reviewable stacked pull …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://graphite.com/openapi.json, https://graphite.com/swagger.json, https://graphite.com/api/opena…”
   • [probe] “official MCP server documented at https://graphite.com/docs/gt-mcp”
   • [probe] “official CLI documented at https://graphite.com/docs/install-the-cli”
   • [claimed-docs] “InsightsMeasure and optimize your team's developer productivity.”
   • [claimed-docs] “AI reviews analyze every pull request in your repositories, identifying potential issues and suggesting fixes instantly - no manual configur…”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Graphite
   Graphite~partialcommunity4/10

   Graphite stores stacking metadata directly in git refs and its CLI is fully git-compatible, meaning core stack/branch data is inherently portable and not locked in a proprietary format (graphite-docs-3, graphite-comm-6), and community members have in fact migrated away to alternatives like git-spice/jujutsu without apparent data-loss complaints (graphite-comm-13). However, there is no explicit documented export feature for other Graphite-held data (AI review comments, insights/analytics, custom rules configs) in open formats. Missing for 10: a documented data-export tool/API for non-git data (reviews, insights, settings), explicit open-format guarantees, and hands-on confirmation of a full account data export.

   • [claimed-docs] “The Graphite CLI is fully compatible with git—just install it on an existing repository and begin using our suite of gt commands.”
   • [community] “The main thing I found to be an improvement is that Graphite maintains all the stacking metadata in git refs. With the other tools, I did no…”
   • [community] “i mentioned a few months ago that it was a shame where graphite was headed re: AI... this appears to be the final nail in the original produ…”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Graphite—none0/10

   No evidence indicates Graphite's source code is published under an open license; Graphite is a commercial SaaS/CLI product with docs, pricing, and GitHub App integration, but nothing about an open-source repository or license.

   ⚑ flag

   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

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 to Cursor Bugbot
   Graphite~partialcommunity6/10

   Graphite documents GitHub App installation, automatic AI reviews on all new PRs with no configuration needed and quick 'few clicks' setup (graphite-docs-9, graphite-docs-18, graphite-docs-19), and comment exclusion rules imply it posts comments directly on PRs. However, there is no GitLab app support — community evidence explicitly notes Graphite lacks GitLab integration (graphite-comm-4) — and no explicit confirmation that comments are rendered as native inline PR comments or evidence of real-world review latency. Missing for 10: GitLab app support, explicit inline-comment rendering confirmation, independent verification of 'within minutes' turnaround.

   • [claimed-docs] “you'll need to authenticate by installing the Graphite App (a GitHub App) on your organization.”
   • [claimed-docs] “AI reviews can be enabled in just a few clicks, with no configuration required to start catching bugs in your pull requests.”
   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should not leave comments.”
   • [community] “I've followed Graphite for a while, and I just wish they supported GitLab. I know why they don't, but my current employer uses it and I've g…”

   proof ↗⚑ flag

   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

Suggestions

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

   weight 3 · round to Graphite
   Graphite✓fullclaimed7/10

   Graphite's docs explicitly describe AI review suggestions with one-click apply ('Ask for suggested fixes and apply them in one click right from the review page') and AI reviews that 'suggest fixes instantly,' matching the story's core capability. Missing for 10: independent/hands-on confirmation that the applied fix is an actual committable diff (vs. just a chat suggestion) and no community citation validating the one-click apply UX in practice.

   • [claimed-docs] “Ask for suggested fixes and apply them in one click right from the review page.”
   • [claimed-docs] “AI reviews analyze every pull request in your repositories, identifying potential issues and suggesting fixes instantly - no manual configur…”
   • [claimed-docs] “Get immediate, actionable feedback with Graphite’s codebase-aware AI code review agent.”

   proof ↗⚑ flag

   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

Summaries

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

   weight 2 · round to Graphite
   Graphite~partialclaimed6/10

   Graphite auto-runs AI reviews on every PR with no configuration needed (graphite-docs-4, graphite-docs-18, graphite-docs-19) and Graphite Chat can generate a PR summary/walkthrough on request ('Summarize the changes in this PR', 'explain what changed... highlight potential issues' — graphite-docs-6, graphite-docs-21, graphite-docs-15). However the summary/walkthrough capability appears to be a chat-driven, on-demand feature rather than an automatically-posted summary comment on every PR, and no evidence shows a structured 'walkthrough' artifact attached automatically like some competitors. Missing for 10: evidence of an automatically-posted summary/walkthrough comment on every PR (not just on-demand chat), and independent/hands-on confirmation of this specific behavior.

   • [claimed-docs] “AI reviews analyze every pull request in your repositories, identifying potential issues and suggesting fixes instantly - no manual configur…”
   • [claimed-docs] “AI reviews can be enabled in just a few clicks, with no configuration required to start catching bugs in your pull requests.”
   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”
   • [claimed-docs] ““Summarize the changes in this PR””
   • [claimed-docs] “Ask Graphite to explain what changed in a pull request, highlight potential issues, or provide context about specific code sections.”
   • [claimed-docs] “Find related files, understand dependencies, and get context from other PRs without switching tabs.”
   • [claimed-docs] “Get immediate, actionable feedback with Graphite’s codebase-aware AI code review agent.”

   proof ↗⚑ flag

   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

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
   Graphite—none0/10

   Docs confirm Graphite Agent automatically reviews all new pull requests and re-reviews on updates, but no evidence describes tracking which prior comments were resolved versus re-flagging them, or any incremental diff-aware re-review logic distinguishing fixed vs. unfixed issues.

   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”
   • [claimed-docs] “AI reviews powered by Graphite Agent help your team build better software by automatically reviewing pull requests and catching bugs before …”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Graphite—none0/10

   No evidence of data residency/region selection controls; docs cover AI opt-in/no-training privacy but never mention where data is stored or region choice.

   ⚑ flag

   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

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

   weight 3 · round to Graphite
   Graphite✓fullclaimed8/10

   Graphite's docs explicitly state AI features are opt-in, do not train on user data, and contractually prohibit its subprocessors (Anthropic, OpenAI) from training on customer data, plus an org-wide opt-out via support request. Missing for 10: independent/third-party verification of these claims and no self-serve UI toggle (requires emailing support to disable).

   • [claimed-docs] “AI privacy and security: Graphite's AI features "are opt-in and do not store or train on your data"; "Neither Graphite nor any of its subpro…”
   • [claimed-docs] “To disable AI features across your entire organization, please email support@graphite.com and request a complete block of all AI features fo…”

   proof ↗⚑ flag

   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

3. ai-native userControl data retention and deletion

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

   Evidence shows a privacy statement about not training on data (opt-in, no training), but there is no mention of data retention controls, deletion mechanisms, or user-facing settings to purge stored data — the core of this story is unaddressed.

   ⚑ flag

   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

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

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

   Evidence covers AI-feature opt-in/no-training privacy policy (graphite-supp-1) but nothing documents a telemetry/usage-tracking opt-out mechanism for the CLI or platform itself. missing for 10: explicit telemetry/usage-analytics opt-out setting or documentation, any CLI flag or config for disabling usage tracking.

   ⚑ flag

   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

Analytics

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

   weight 1 · round to Cursor Bugbot
   Graphite~partialclaimed3/10

   Graphite docs reference an 'Insights' feature to 'measure and optimize your team's developer productivity' and a way to track PRs across repos, suggesting some org-level visibility, but there is no documentation describing dashboards for AI-review findings, acceptance rates of suggestions, or review-coverage metrics specifically. Missing for 10: concrete dashboard screenshots/specs for findings and acceptance-rate tracking, review-coverage metrics, and any independent corroboration of the Insights feature's content.

   • [claimed-docs] “InsightsMeasure and optimize your team's developer productivity.”
   • [claimed-docs] “Measure and optimize your team’s developer productivity.”
   • [claimed-docs] “InsightsMeasure and optimize your team’s developer productivity.”
   • [claimed-docs] “Insights Measure and optimize your team’s developer productivity.”
   • [claimed-docs] “Stay up-to-date with PRs across many repos using custom filters and rules.”

   proof ↗⚑ flag

   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

Gates

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

   weight 2 · round to Graphite
   Graphite~partialclaimed5/10

   Graphite offers merge queue and AI review functionality that surfaces issues, plus CI status checks via GitHub webhooks, but the evidence does not document a specific 'required status check' or 'blocking review' setting that enforces resolution of AI/critical findings before merge — the merge queue is about ordering/keeping branches green rather than gating on unresolved findings. missing for 10: explicit documentation of a required-check/blocking-review policy tied to AI review findings, admin controls to enforce this gate, and independent confirmation it blocks merges when findings are unresolved.

   • [claimed-docs] “Our stack-aware merge queue lands PRs in order and keeps branches green, helping you gain momentum.”
   • [claimed-docs] “AI reviews can be enabled in just a few clicks, with no configuration required to start catching bugs in your pull requests.”
   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”
   • [claimed-docs] “Receive GitHub webhooks for real-time updates on CI status, mergeability, and push events.”
   • [claimed-docs] “Get immediate, actionable feedback with Graphite’s codebase-aware AI code review agent.”

   proof ↗⚑ flag

   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

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 Graphite
   Graphite~partialcommunity4/10

   Graphite's docs claim its AI reviewer 'identifies potential issues,' 'catches bugs,' and is 'codebase-aware,' but no evidence—vendor or independent—specifically demonstrates it catching logic errors, race conditions, or edge-case bugs versus superficial/style comments. One community comment expresses skepticism that the AI review features add lasting value, but this is general sentiment, not a concrete counter-example, so it doesn't rise to disputed. missing for 10: independent/hands-on examples of the reviewer catching genuine logic/concurrency bugs, benchmark or comparison data on false-positive/style-vs-substance ratio.

   • [claimed-docs] “AI reviews analyze every pull request in your repositories, identifying potential issues and suggesting fixes instantly - no manual configur…”
   • [claimed-docs] “Get immediate, actionable feedback with Graphite’s codebase-aware AI code review agent.”
   • [claimed-docs] “AI reviews can be enabled in just a few clicks, with no configuration required to start catching bugs in your pull requests.”
   • [community] “This is annoying, Graphite's core feature of stacked PRs is really good despite all the AI things they've added around their review UI. I do…”

   proof ↗⚑ flag

   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

Learning

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

   weight 2 · round drawn
   Graphite~partialclaimed4/10

   Graphite offers 'comment exclusions' and 'custom rules' letting developers manually configure the AI reviewer to stop leaving certain kinds of comments, which can approximate 'the reviewer learns' — but this is a manual rule-writing workaround, not an automatic learning loop triggered by pushing back in a review thread. missing for 10: evidence of automatic memory/learning from in-thread pushback, evidence that a rejected comment is not repeated without manual rule creation, any hands-on/community confirmation this actually works as claimed.

   • [claimed-docs] “Custom rules allow you to define explicit guidelines for Graphite Agent to follow when reviewing your code.”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should not leave comments.”

   proof ↗⚑ flag

   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

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 drawn
   Graphite~partialcommunity5/10

   Graphite lets teams reduce noise via custom rules and comment exclusions (specifying when Agent should not comment) and codebase-aware review context, which addresses false positives to some degree, but there is no documented deduplication mechanism or severity/priority labeling on comments, and community reaction (e.g. mixed sentiment about the AI review additions) is vague rather than a concrete accuracy failure. missing for 10: explicit severity/priority labeling of comments, deduplication logic across review passes, independent benchmarking or hands-on evidence of false-positive rates.

   • [claimed-docs] “Custom rules allow you to define explicit guidelines for Graphite Agent to follow when reviewing your code.”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should not leave comments.”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should **not** leave comments.”
   • [claimed-docs] “Get immediate, actionable feedback with Graphite’s codebase-aware AI code review agent.”
   • [community] “This is annoying, Graphite's core feature of stacked PRs is really good despite all the AI things they've added around their review UI. I do…”
   • [community] “i mentioned a few months ago that it was a shame where graphite was headed re: AI... this appears to be the final nail in the original produ…”

   proof ↗⚑ flag

   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

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
   Graphite—none0/10

   Graphite's AI review docs describe catching 'bugs' and general 'potential issues' in PRs, but nothing in the evidence pack specifically claims detection of security-specific problems like injection risks, leaked secrets, or insecure coding patterns; custom rules/comment exclusions are the only customization levers mentioned, not security-focused presets.

   • [claimed-docs] “AI reviews analyze every pull request in your repositories, identifying potential issues and suggesting fixes instantly - no manual configur…”
   • [claimed-docs] “AI reviews can be enabled in just a few clicks, with no configuration required to start catching bugs in your pull requests.”
   • [claimed-docs] “AI reviews powered by Graphite Agent help your team build better software by automatically reviewing pull requests and catching bugs before …”
   • [claimed-docs] “Custom rules allow you to define explicit guidelines for Graphite Agent to follow when reviewing your code.”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should not leave comments.”

   proof ↗⚑ flag

   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

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 drawn
   Graphite—none0/10

   Graphite's AI review capability is documented as PR-triggered via the GitHub App/web UI (automatically reviewing pull requests), not as a CLI command usable against local diffs or in CI scripts with machine-readable output. The `gt` CLI documented is for stack management (branch creation, submission, config) with no review subcommand or structured/JSON output format mentioned anywhere in the evidence.

   • [claimed-docs] “AI reviews analyze every pull request in your repositories, identifying potential issues and suggesting fixes instantly - no manual configur…”
   • [claimed-docs] “AI reviews can be enabled in just a few clicks, with no configuration required to start catching bugs in your pull requests.”
   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”
   • [claimed-docs] “you'll need to authenticate by installing the Graphite App (a GitHub App) on your organization.”
   • [claimed-docs] “The Graphite CLI is a tool to help you break up large engineering tasks into a series of small, incremental code changes directly from the c…”
   • [claimed-docs] “Run gt config to open an interactive menu which lets you configure your Graphite CLI.”

   proof ↗⚑ flag

   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

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 drawn
   Graphite—none0/10

   Graphite's AI review (Agent) explicitly runs on pull requests after they are opened on GitHub, not inside the IDE before push; the only 'IDE' touchpoint documented is a GUI for visualizing stacks, not a pre-push review mechanism. No evidence of an IDE plugin or pre-commit hook that surfaces the same AI review before pushing.

   • [claimed-docs] “AI reviews analyze every pull request in your repositories, identifying potential issues and suggesting fixes instantly - no manual configur…”
   • [claimed-docs] “A GUI designed to make stacking visual and simple, right from your IDE.”
   • [claimed-docs] “AI reviews can be enabled in just a few clicks, with no configuration required to start catching bugs in your pull requests.”
   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”

   proof ↗⚑ flag

   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

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 drawn
   Graphite~partialclaimed5/10

   Graphite supports custom rules and comment exclusions for the AI review agent (graphite-docs-5, graphite-docs-20), which covers per-repo instruction customization, but there is no evidence of a versioned config file checked into the repo, nor of path-based filters or multiple named review profiles selectable per path. missing for 10: evidence of a repo-committed/versioned config file format, path-level filtering rules, and support for multiple distinct review profiles.

   • [claimed-docs] “Custom rules allow you to define explicit guidelines for Graphite Agent to follow when reviewing your code.”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should not leave comments.”
   • [claimed-docs] “AI reviews can be enabled in just a few clicks, with no configuration required to start catching bugs in your pull requests.”
   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”

   proof ↗⚑ flag

   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

Governance

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

   weight 1 · round drawn
   Graphite~partialclaimed5/10

   Graphite supports org-wide GitHub App installation and enabling AI review across 'selected repositories' with per-repo custom rules and comment exclusions, and org-wide AI-disable requires emailing support — but there is no documented centralized dashboard for setting org-level review defaults and managing per-repo exceptions at scale across hundreds of repos. missing for 10: evidence of a bulk/org-level policy management UI, audit of exceptions across many repos, and any customer testimonial about managing hundreds of repos centrally.

   • [claimed-docs] “you'll need to authenticate by installing the Graphite App (a GitHub App) on your organization.”
   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should not leave comments.”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should **not** leave comments.”
   • [claimed-docs] “To disable AI features across your entire organization, please email support@graphite.com and request a complete block of all AI features fo…”
   • [claimed-docs] “you'll need to authenticate by installing the Graphite App (a GitHub App) on your organization”

   proof ↗⚑ flag

   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

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
   Graphite~partialclaimed6/10

   Graphite's AI review docs confirm a 'Custom rules' feature letting teams define explicit natural-language guidelines for the review agent, plus 'comment exclusions' to tune behavior, which covers the natural-language rules part of the story. However, there is no evidence of AST-pattern-based rule definition or linking external/style-guide documents for enforcement. Missing for 10: AST pattern rule support, ability to link external style guides, and independent/hands-on confirmation that custom rules are reliably enforced.

   • [claimed-docs] “Custom rules allow you to define explicit guidelines for Graphite Agent to follow when reviewing your code.”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should not leave comments.”
   • [claimed-docs] “AI reviews analyze every pull request in your repositories, identifying potential issues and suggesting fixes instantly - no manual configur…”

   proof ↗⚑ flag

   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