Greptile vs Graphite

Agent access

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

   weight 2 · round to Greptile
   Greptile✓fullprobed8/10

   Greptile has a confirmed llms.txt at the root (HTTP 200) plus per-page .md variants (e.g. docs/introduction.md) and a documentation index at docs/llms.txt, explicitly designed for agents to fetch; docs also explicitly invite handing pages to a coding agent to run setup. Missing for 10: independent/community confirmation that an external agent successfully consumed llms.txt end-to-end, and no evidence of an OpenAPI spec to complement it.

   • [probe] “PROBE llms.txt: HTTP 200 at https://www.greptile.com/llms.txt # Greptile > Greptile is an independent AI code validation platform for GitHu…”
   • [probe] “PROBE docs-md: HTTP 200 at https://www.greptile.com/docs/introduction.md > ## Documentation Index > Fetch the complete documentation index a…”
   • [claimed-docs] “Set up Greptile from your terminal with `greptile onboard` — or hand this page to your coding agent and have it run the setup for you.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Greptile
   Greptile✓fullprobed8/10

   Greptile ships an official CLI (`greptile review`, `greptile onboard`) that runs headlessly against a diff in ~60 seconds and is explicitly designed for coding agents to invoke on their own code, plus automated PR-triggered reviews on GitHub/GitLab that require no human interaction — both classic CI/automation patterns. missing for 10: explicit CI pipeline example (e.g., GitHub Actions/GitLab CI YAML snippet) and independent third-party confirmation of headless CI usage

   • [claimed-docs] “Run `greptile review`, get a review of the feature branch diff in 60 seconds.”
   • [claimed-docs] “Coding agents can use the greptile cli to review their own code”
   • [claimed-docs] “Set up Greptile AI code reviews in 5 minutes. Connect GitHub or GitLab, configure review triggers, and get automated feedback on your first …”
   • [claimed-docs] “`greptile onboard` creates your organization, connects GitHub or GitLab, enables repositories, and imports your existing AI rules files — th…”
   • [probe] “official CLI documented at https://www.greptile.com/docs/code-review/greptile-cli”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Greptile—none0/10

   All MCP-related evidence describes Greptile exposing its own MCP server so other tools (Cursor, Claude Code, VS Code, Codex) can pull Greptile's review data and fixes (docs-23, docs-24, probe-4) — this is Greptile acting as the MCP server, not as a client that consumes external MCP servers' tools. There is no evidence Greptile itself can be configured to plug in and use third-party MCP servers/tools.

   • [claimed-docs] “Fetch PR comments - Get unaddressed Greptile feedback for any PR”
   • [claimed-docs] “Connect Cursor, Claude Code, VS Code, or Codex to Greptile MCP with OAuth.”
   • [probe] “official MCP server documented at https://www.greptile.com/docs/mcp-v2/overview”

   proof ↗⚑ flag

   Graphite—none0/10

   Evidence shows Graphite ships its own 'GT MCP' server so that external AI agents can call Graphite's tools (graphite-docs-30, graphite-probe-4), which is the reverse direction of the story — Graphite acting as an MCP server, not as a client that lets users plug external MCP servers into Graphite's own agents/chat. There is no evidence that Graphite's Agents or Chat features can consume third-party MCP servers' tools.

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

   proof ↗⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Greptile
   Greptile✓fullprobed8/10

   Greptile documents an official MCP server (mcp-v2) with OAuth-based connection for Cursor, Claude Code, VS Code, and Codex, exposing tools to fetch PR comments, apply fixes, and manage patterns from the agent's IDE. This is well-documented first-party functionality with multiple docs pages (overview, setup, auto-fix, custom-context) and a probe confirming the endpoint exists. Missing for 10: independent/hands-on community verification that the MCP server works as described, and a fuller list of exposed tools/capabilities beyond the docs summaries.

   • [claimed-docs] “Fetch PR comments - Get unaddressed Greptile feedback for any PR”
   • [claimed-docs] “Connect Cursor, Claude Code, VS Code, or Codex to Greptile MCP with OAuth.”
   • [claimed-docs] “List unaddressed Greptile comments for PR #5 in owner/repo”
   • [claimed-docs] “With MCP, you can view, search, and create patterns from your IDE.”
   • [probe] “official MCP server documented at https://www.greptile.com/docs/mcp-v2/overview”

   proof ↗⚑ flag

   Graphite✓fullprobed6/10

   Graphite documents an official MCP server at /docs/gt-mcp, directly matching the story of connecting an agent via an official MCP server, and Graphite is a dev-tool/platform (not itself an agent) so this axis applies. However, the evidence pack only confirms the page exists (probe) without excerpting its content, and there is no independent/hands-on corroboration of using it to connect an agent. Missing for 10: detailed docs content describing the MCP server's tools/capabilities, and community or hands-on confirmation of successful agent connection.

   • [probe] “official MCP server documented at https://graphite.com/docs/gt-mcp”
   • [claimed-docs] “Install the Graphite CLI using either Homebrew or npm”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round to Graphite
   Greptile✓fullprobed8/10

   Greptile documents an official CLI (`greptile onboard`, `greptile review`) that sets up the org and runs full PR reviews with confidence scores, diagrams, and test generation in ~60 seconds, and explicitly positions it for agentic use ('Coding agents can use the greptile cli to review their own code'). This is well-documented first-party functionality with a dedicated docs page and probe confirmation. Missing for 10: independent/hands-on community verification specifically of the CLI (community evidence covers the web product, not CLI usage) and no public API/OpenAPI spec surfaced for deeper CLI-adjacent automation.

   • [claimed-docs] “Set up Greptile from your terminal with `greptile onboard` — or hand this page to your coding agent and have it run the setup for you.”
   • [claimed-docs] “Run `greptile review`, get a review of the feature branch diff in 60 seconds.”
   • [claimed-docs] “Coding agents can use the greptile cli to review their own code”
   • [claimed-docs] “`greptile onboard` creates your organization, connects GitHub or GitLab, enables repositories, and imports your existing AI rules files — th…”
   • [probe] “official CLI documented at https://www.greptile.com/docs/code-review/greptile-cli”

   proof ↗⚑ flag

   Graphite✓fullprobed9/10

   Graphite ships a well-documented official CLI (`gt`) installable via npm/Homebrew, fully git-compatible, with configuration (`gt config`) and a full command reference, and this is corroborated by extensive hands-on community use praising the CLI workflow. It also integrates with AI agent workflows via GT MCP for stacked PR creation, reinforcing agentic use. Missing for 10: no independent benchmark of CLI performance/reliability beyond anecdotal community reports (e.g., some bug reports on rebase/signing edge cases).

   • [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.”
   • [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] “official CLI documented at https://graphite.com/docs/install-the-cli”
   • [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 …”
   • [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…”

   proof ↗⚑ flag

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

   weight 3 · round to Greptile
   Greptile~partialprobed6/10

   Greptile exposes a documented MCP v2 server (fetch PR comments, apply fixes, manage patterns) and a CLI (`greptile review`, `greptile onboard`) that let an AI agent drive the product programmatically, which functions as a de-facto public API for agentic use, but explicit REST/OpenAPI documentation was probed and returned 404s, meaning no conventional public API spec is confirmed. missing for 10: a documented REST/OpenAPI-style public API, independent confirmation that the MCP/CLI interfaces are being used as a full 'public API' by third parties.

   • [claimed-docs] “Fetch PR comments - Get unaddressed Greptile feedback for any PR”
   • [claimed-docs] “Connect Cursor, Claude Code, VS Code, or Codex to Greptile MCP with OAuth.”
   • [claimed-docs] “List unaddressed Greptile comments for PR #5 in owner/repo”
   • [claimed-docs] “With MCP, you can view, search, and create patterns from your IDE.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.greptile.com/openapi.json, https://www.greptile.com/swagger.json, https://www.greptile.c…”
   • [probe] “official MCP server documented at https://www.greptile.com/docs/mcp-v2/overview”
   • [probe] “official CLI documented at https://www.greptile.com/docs/code-review/greptile-cli”
   • [claimed-docs] “Run `greptile review`, get a review of the feature branch diff in 60 seconds.”
   • [claimed-docs] “Coding agents can use the greptile cli to review their own code”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Greptile—none0/10

   No evidence of scoped or least-privilege API credential/token issuance for agents; MCP setup mentions OAuth connection but nothing about scoping permissions or credential granularity. Missing for 10: any documentation of API key scopes, permission levels, or least-privilege token issuance for agent access.

   ⚑ flag

   Graphite—none0/10

   No evidence describes scoped or least-privilege API credential/token issuance for agents; authentication is via GitHub App installation (org-wide) or MCP setup, with no mention of granular permission scoping for AI agent credentials. missing for 10: scoped/least-privilege credential issuance mechanism, token/permission granularity controls, any documentation of credential scoping for agents.

   • [claimed-docs] “you'll need to authenticate by installing the Graphite App (a GitHub App) on your organization.”
   • [claimed-docs] “you'll need to authenticate by installing the Graphite App (a GitHub App) on your organization”
   • [claimed-docs] “GT MCP allows AI agents to automatically create stacked PRs, breaking down large AI-generated changes into smaller, reviewable stacked pull …”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Graphite
   Greptile—none0/10

   Evidence shows Greptile offers a CLI and an MCP server for agent integration, but no official SDKs (client libraries) are documented anywhere, and the openapi probe returned 404 for all candidate API-spec paths, indicating no public API/SDK surface to build against.

   • [probe] “PROBE openapi: all candidate paths 404 (https://www.greptile.com/openapi.json, https://www.greptile.com/swagger.json, https://www.greptile.c…”
   • [probe] “official MCP server documented at https://www.greptile.com/docs/mcp-v2/overview”
   • [probe] “official CLI documented at https://www.greptile.com/docs/code-review/greptile-cli”
   • [claimed-docs] “Run `greptile review`, get a review of the feature branch diff in 60 seconds.”
   • [claimed-docs] “Connect Cursor, Claude Code, VS Code, or Codex to Greptile MCP with OAuth.”

   proof ↗⚑ flag

   Graphite~partialprobed6/10

   Graphite ships an official CLI (gt) with npm/Homebrew install and documented config, plus a documented MCP server (gt-mcp), giving AI-native users official tooling to build against. However, there is no evidence of a general-purpose SDK (e.g., Python/JS client library) or public API/OpenAPI spec — probes for openapi.json all 404'd. missing for 10: official SDK/client libraries beyond the CLI, public API reference/OpenAPI spec, independent developer corroboration of building against these interfaces.

   • [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.”
   • [probe] “official MCP server documented at https://graphite.com/docs/gt-mcp”
   • [probe] “official CLI documented at https://graphite.com/docs/install-the-cli”
   • [probe] “PROBE openapi: all candidate paths 404 (https://graphite.com/openapi.json, https://graphite.com/swagger.json, https://graphite.com/api/opena…”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Greptile—none0/10

   No evidence of any webhook subscription mechanism for events; Greptile's integrations documented are MCP, CLI, and agent 'Fix with your Agent' flows, but no docs mention webhooks for subscribing to review or event notifications.

   ⚑ flag

   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

Agentic features

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

   weight 2 · round to Graphite
   Greptile!disputedcontradicted6/10

   Greptile's core product surfaces AI-generated insights from codebase data — review comments, 0-5 confidence scores, sequence diagrams, auto-generated tests, security findings, and a learning system that improves suggestions from feedback (greptile-docs-16/17/18/25/33, comm-1, comm-8). However, hands-on community reports document concrete failures of this insight-generation capability: repos stuck processing or erroring out, incomplete/incorrect answers on template-heavy code, and search bugs on multi-branch repos (greptile-comm-3/4/5/6/7), directly contradicting the polished vendor narrative for at least some users. Missing for 10: consistent independent verification that insights are reliably accurate across codebases, resolution of the documented processing/error failures, and more recent hands-on corroboration beyond mixed 2024 anecdotes.

   • [claimed-docs] “Greptile is an AI code review agent that automatically reviews every pull request with complete understanding of your codebase.”
   • [claimed-docs] “Know how safe a PR is to merge at a glance with a 0-5 score”
   • [claimed-docs] “Parse complex changes with sequence diagrams and flowcharts generated for every PR”
   • [claimed-docs] “Automatically generate unit tests for new and changed code in every PR”
   • [claimed-docs] “Greptile pairs static scanning with an AI security agent to catch vulnerabilities in every pull request.”
   • [claimed-docs] “Greptile learns from your team's feedback to provide increasingly relevant suggestions. The primary training methods are emoji reactions and…”
   • [community] “Asked Greptile about how BigDecimal is encoded in as_json in Rails; got an accurate answer matching what user learned from PRs/issues/code r…”
   • [community] “My employer uses greptile and I'm pretty happy with it. Sometimes it can be a bit overzealous but more often than not it catches real issues…”
   • [community] “Tried it on my own C++ codebase - impressed it found the C++ standard used, but it's really bad at analyzing templates; answers always incom…”
   • [community] “Not a single repo I've tried works. A lot of them seem not to have finished processing, but even the ones that have finished don't work.”
   • [community] “Ran it on my OSS project - stuck at 99% loading for ~30 minutes, then got 'Error: Internal error while locating sources' on every query. 'Th…”
   • [community] “Loading a repo with many branches (cassandra), searching for 'vsearch' surfaced branch-named results (CNDB-8708-vsearch, DSP-23946-vsearch) …”
   • [community] “Getting 'Error: Internal error while processing request' while trying on my personal public github repo.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Greptile
   Greptile✓fullclaimed7/10

   Greptile's core product is background automation: it automatically reviews every PR once triggers are configured (greptile-docs-1, greptile-docs-5), runs an autonomous sandboxed runtime-testing agent (TREX, greptile-docs-19), pairs static+security agents run automatically per PR (greptile-docs-25), and routes reviews to different models autonomously based on PR author (greptile-docs-27) - all without manual per-run invocation. Custom rules, strictness controls, and greptile.json let users configure how these background automations behave (greptile-docs-20, greptile-docs-21, greptile-docs-22). missing for 10: independent/hands-on confirmation that the automation runs reliably unattended over time (community evidence only covers review quality/accuracy, not background reliability), and no evidence of general-purpose scheduled/triggered automations beyond PR-review-centric events

   • [claimed-docs] “Greptile is an AI code review agent that automatically reviews every pull request with complete understanding of your codebase.”
   • [claimed-docs] “Set up Greptile AI code reviews in 5 minutes. Connect GitHub or GitLab, configure review triggers, and get automated feedback on your first …”
   • [claimed-docs] “TREX runs your PR branch in a sandbox to find the bugs that only show up at runtime. It starts services, mocks inputs, clicks through UI flo…”
   • [claimed-docs] “Greptile pairs static scanning with an AI security agent to catch vulnerabilities in every pull request.”
   • [claimed-docs] “v5 is faster, catches more bugs, and flags fewer false positives by running a swarm of narrowly scoped agents in parallel.”
   • [claimed-docs] “Greptile can now detect when a PR was authored by a coding agent and route the review to a different model. If Claude wrote it, GPT reviews …”
   • [claimed-docs] “Control how strict Greptile is about leaving comments with the strictness setting (1–3).”
   • [claimed-docs] “Place `greptile.json` in your repository root. Settings are read from the source branch of the PR and override dashboard settings.”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Graphite
   Greptile!disputedcontradicted5/10

   Greptile's docs strongly position it as a built-in AI agent you delegate to — it reviews PRs, generates unit tests, runs sandboxed dynamic tests (TREX), answers codebase questions, and iterates fixes (greptile-docs-1, 18, 19, 33). Community reports include successful task delegation (accurate Q&A, catching real issues in production use) but also concrete hands-on failures — repos stuck processing, 'Internal error' responses, incomplete/incorrect analysis on complex code like C++ templates — directly contradicting reliability of the delegated-task experience. Missing for 10: consistent reliability across codebases/languages, resolution of reported internal errors, and independent benchmarks confirming task success rates.

   • [claimed-docs] “Greptile is an AI code review agent that automatically reviews every pull request with complete understanding of your codebase.”
   • [claimed-docs] “Automatically generate unit tests for new and changed code in every PR”
   • [claimed-docs] “TREX runs your PR branch in a sandbox to find the bugs that only show up at runtime. It starts services, mocks inputs, clicks through UI flo…”
   • [claimed-docs] “Greptile learns from your team's feedback to provide increasingly relevant suggestions. The primary training methods are emoji reactions and…”
   • [community] “Asked Greptile about how BigDecimal is encoded in as_json in Rails; got an accurate answer matching what user learned from PRs/issues/code r…”
   • [community] “Tried it on my own C++ codebase - impressed it found the C++ standard used, but it's really bad at analyzing templates; answers always incom…”
   • [community] “Not a single repo I've tried works. A lot of them seem not to have finished processing, but even the ones that have finished don't work.”
   • [community] “Ran it on my OSS project - stuck at 99% loading for ~30 minutes, then got 'Error: Internal error while locating sources' on every query. 'Th…”
   • [community] “Getting 'Error: Internal error while processing request' while trying on my personal public github repo.”
   • [community] “My employer uses greptile and I'm pretty happy with it. Sometimes it can be a bit overzealous but more often than not it catches real issues…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Graphite
   Greptile~partialcommunity5/10

   Greptile supports natural-language interaction for codebase Q&A (comm-1 shows a user asking an English question and getting an accurate answer) and lets teams define custom review rules in plain language (greptile-docs-21), but its primary interfaces (CLI commands like `greptile review`, MCP tool calls, PR-trigger automation) are structured, not conversational commands. missing for 10: a documented chat/command interface for issuing arbitrary natural-language instructions to control reviews or agent actions, and independent verification that NL querying works reliably at scale.

   • [community] “Asked Greptile about how BigDecimal is encoded in as_json in Rails; got an accurate answer matching what user learned from PRs/issues/code r…”
   • [claimed-docs] “Create custom rules that catch team-specific issues”
   • [claimed-docs] “Your 👍/👎 reactions and replies teach Greptile what matters. After 2-3 weeks, it stops commenting on things you don't care about.”
   • [claimed-docs] “Run `greptile review`, get a review of the feature branch diff in 60 seconds.”

   proof ↗⚑ flag

   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

Api quality

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

   weight 2 · round drawn
   Greptile—none0/10

   No evidence of an interactive API reference or runnable examples; the openapi.json/swagger.json probe explicitly returned 404s across all candidate paths, and docs only describe CLI/MCP/dashboard workflows, not an API explorer.

   • [probe] “PROBE openapi: all candidate paths 404 (https://www.greptile.com/openapi.json, https://www.greptile.com/swagger.json, https://www.greptile.c…”

   proof ↗⚑ flag

   Graphite—none0/10

   No evidence of an interactive API reference or runnable examples; OpenAPI/swagger probes returned 404 and no such documentation is mentioned anywhere in the pack.

   • [probe] “PROBE openapi: all candidate paths 404 (https://graphite.com/openapi.json, https://graphite.com/swagger.json, https://graphite.com/api/opena…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Greptile—none0/10

   A direct probe found no OpenAPI/Swagger spec at any standard location (all 404s), and no other evidence mentions a machine-readable API spec being available for download.

   • [probe] “PROBE openapi: all candidate paths 404 (https://www.greptile.com/openapi.json, https://www.greptile.com/swagger.json, https://www.greptile.c…”

   proof ↗⚑ flag

   Graphite—none0/10

   Probe explicitly found no OpenAPI/swagger spec at any standard path and no llms.txt, and no documentation references a machine-readable API spec download; only an MCP server and CLI are documented.

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

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Greptile
   Greptile✓fullclaimed6/10

   Greptile's TREX feature explicitly runs the PR branch in an isolated sandbox—starting services, mocking inputs, and exercising UI flows—to surface runtime bugs without touching production, directly matching the story. Missing for 10: independent/hands-on confirmation of TREX's sandbox isolation and explicit statements about production-data exclusion beyond vendor docs.

   • [claimed-docs] “TREX runs your PR branch in a sandbox to find the bugs that only show up at runtime. It starts services, mocks inputs, clicks through UI flo…”

   proof ↗⚑ flag

   Graphite—none0/10

   Graphite's docs describe AI code review, chat, and agents that create draft PRs, but nothing in the evidence pack describes a sandbox/staging environment distinct from production for testing AI-native workflows. Missing for 10: any mention of a sandbox mode, test/staging environment, or isolated execution context that avoids touching production data.

   ⚑ flag

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

   weight 2 · round drawn
   Greptile—none0/10

   No evidence of API versioning scheme or a documented deprecation policy; the openapi probe returned 404s and no changelog entries mention API versioning/deprecation. Missing for 10: versioned API docs, explicit deprecation policy, changelog entries about API version sunsetting.

   • [probe] “PROBE openapi: all candidate paths 404 (https://www.greptile.com/openapi.json, https://www.greptile.com/swagger.json, https://www.greptile.c…”

   proof ↗⚑ flag

   Graphite—none0/10

   No evidence of any versioned API, API changelog, or documented deprecation policy — OpenAPI probes return 404 and no docs reference API versioning or deprecation practices.

   • [probe] “PROBE openapi: all candidate paths 404 (https://graphite.com/openapi.json, https://graphite.com/swagger.json, https://graphite.com/api/opena…”

   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 Greptile
   Greptile✓fullcommunity8/10

   Greptile explicitly documents detecting when a PR was AI-authored and routing it to a different model for review (docs-27), reviews every PR automatically at scale via parallel agent swarms (docs-26), runs runtime sandbox testing (TREX, docs-19), and offers an iterative 'Greplooping' fix cycle until a PR hits 5/5 confidence with zero unresolved comments (docs-13/28) — directly matching the 'holds the line on agent PRs at volume' story. Community evidence corroborates real-world catch-rate value (comm-8) though some older reports cite reliability/error issues unrelated specifically to this agent-detection feature. Missing for 10: independent hands-on verification of the specific agent-authorship detection/routing feature and concrete volume/throughput metrics.

   • [claimed-docs] “Greptile can now detect when a PR was authored by a coding agent and route the review to a different model. If Claude wrote it, GPT reviews …”
   • [claimed-docs] “v5 is faster, catches more bugs, and flags fewer false positives by running a swarm of narrowly scoped agents in parallel.”
   • [claimed-docs] “TREX runs your PR branch in a sandbox to find the bugs that only show up at runtime. It starts services, mocks inputs, clicks through UI flo…”
   • [claimed-docs] “Iteratively fix a PR until Greptile gives a perfect review: 5/5 confidence, zero unresolved comments.”
   • [claimed-docs] “Greplooping Iteratively fix a PR until Greptile gives a perfect review: 5/5 confidence, zero unresolved comments.”
   • [claimed-docs] “Greptile pairs static scanning with an AI security agent to catch vulnerabilities in every pull request.”
   • [community] “My employer uses greptile and I'm pretty happy with it. Sometimes it can be a bit overzealous but more often than not it catches real issues…”

   proof ↗⚑ flag

   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

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

   Greptile supports custom, team-defined rules in plain language ('Create custom rules that catch team-specific issues') configured via greptile.json, and these run automatically on every PR alongside a confidence score/unresolved-comment gate that can act as a de facto merge check (docs-21, docs-22, docs-13). However, there's no explicit evidence of a dedicated 'pre-merge check' construct with pass/fail CI status gating, nor examples matching the story's specific phrasing (e.g., 'docs updated', 'tests cover new paths') as discrete named checks. Missing for 10: explicit merge-blocking/CI-status-check integration tied to named custom checks, and concrete examples/documentation of plain-language check definitions beyond generic 'custom rules'.

   • [claimed-docs] “Create custom rules that catch team-specific issues”
   • [claimed-docs] “Place `greptile.json` in your repository root. Settings are read from the source branch of the PR and override dashboard settings.”
   • [claimed-docs] “Iteratively fix a PR until Greptile gives a perfect review: 5/5 confidence, zero unresolved comments.”
   • [claimed-docs] “Control how strict Greptile is about leaving comments with the strictness setting (1–3).”
   • [claimed-docs] “With noise control, Greptile limits reviews to high-signal insights, skipping low impact or repetitive feedback.”

   proof ↗⚑ flag

   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

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 Greptile
   Greptile✓fullclaimed8/10

   Docs describe a complete in-PR fix loop: each review comment has a 'Fix with your Agent' button that sends file paths/lines/suggested code to Claude Code, Codex, Cursor, or Devin, a 'Fix All' button for batch fixes, MCP integration to fetch/resolve comments from the IDE, and 'Greplooping' to iteratively fix until a perfect review score—all without leaving the PR context. Missing for 10: independent/hands-on evidence confirming the fix-apply workflow works reliably in practice (community evidence in the pack addresses general review quality/accuracy, not this specific fix-application flow).

   • [claimed-docs] “Every review comment includes a Fix with your Agent button that sends the issue — with file paths, line numbers, and suggested code — straig…”
   • [claimed-docs] “A Fix All button in the review summary sends every issue at once.”
   • [claimed-docs] “Launch any agent in one click with a Greptile comment, full context, and suggested fix.”
   • [claimed-docs] “Access Greptile review comments, apply fixes, and manage coding patterns directly from your agent of choice.”
   • [claimed-docs] “Iteratively fix a PR until Greptile gives a perfect review: 5/5 confidence, zero unresolved comments.”
   • [claimed-docs] “Fetch PR comments - Get unaddressed Greptile feedback for any PR”
   • [claimed-docs] “Greplooping Iteratively fix a PR until Greptile gives a perfect review: 5/5 confidence, zero unresolved comments.”
   • [claimed-docs] “Org admins can go to **Settings → Code Review → Default Coding Agents** to turn on Fix with your Agent for the org.”
   • [claimed-docs] “Every Greptile review comment includes a **Fix with your Agent** button. Click it, and the issue gets sent straight to your coding agent wit…”

   proof ↗⚑ flag

   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

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 Greptile
   Greptile✓fullclaimed9/10

   Greptile documents a 'Fix with your Agent' button on every review comment that sends file paths, line numbers, and suggested code directly to Claude Code, Cursor, Codex, Devin, or Conductor, plus a 'Fix All' button for batch handoff, and an MCP v2 server letting agents fetch/resolve unaddressed comments with OAuth support for Cursor/Claude Code/VS Code/Codex. This directly matches the story's clean hand-off requirement with both one-click integration and MCP-based programmatic access. Missing for 10: independent/hands-on community verification that the 'Fix with your Agent' handoff works reliably in practice (only vendor docs cited).

   • [claimed-docs] “Every review comment includes a Fix with your Agent button that sends the issue — with file paths, line numbers, and suggested code — straig…”
   • [claimed-docs] “A Fix All button in the review summary sends every issue at once.”
   • [claimed-docs] “Launch any agent in one click with a Greptile comment, full context, and suggested fix.”
   • [claimed-docs] “Access Greptile review comments, apply fixes, and manage coding patterns directly from your agent of choice.”
   • [claimed-docs] “View and resolve review comments directly from Claude Code.”
   • [claimed-docs] “Fetch PR comments - Get unaddressed Greptile feedback for any PR”
   • [claimed-docs] “Connect Cursor, Claude Code, VS Code, or Codex to Greptile MCP with OAuth.”
   • [claimed-docs] “Org admins can go to **Settings → Code Review → Default Coding Agents** to turn on Fix with your Agent for the org.”
   • [claimed-docs] “Every Greptile review comment includes a **Fix with your Agent** button. Click it, and the issue gets sent straight to your coding agent wit…”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Greptile~partialclaimed6/10

   Greptile documents a 'Fix All' button that sends every issue in a review at once to a coding agent, and `greptile onboard` can enable multiple repositories and import existing AI rules files in one command — both genuine bulk operations. However, evidence doesn't show bulk actions across many PRs, repos, or reviews simultaneously (e.g., batch-reviewing multiple PRs, mass-applying custom rules across repos), and there's no independent/hands-on confirmation of these bulk features working at scale. missing for 10: cross-PR/cross-repo bulk review or fix operations, evidence of bulk custom-rule application across an org, independent verification of Fix All/onboard at scale.

   • [claimed-docs] “A Fix All button in the review summary sends every issue at once.”
   • [claimed-docs] “Iteratively fix a PR until Greptile gives a perfect review: 5/5 confidence, zero unresolved comments.”
   • [claimed-docs] “Greplooping Iteratively fix a PR until Greptile gives a perfect review: 5/5 confidence, zero unresolved comments.”
   • [claimed-docs] “`greptile onboard` creates your organization, connects GitHub or GitLab, enables repositories, and imports your existing AI rules files — th…”
   • [claimed-docs] “Org admins can go to **Settings → Code Review → Default Coding Agents** to turn on Fix with your Agent for the org.”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Greptile~partialclaimed5/10

   Greptile lets users configure review triggers, custom standards/rules (greptile.json, custom-standards docs), strictness/noise control, and automated actions like Fix with your Agent triggered on review events, which is a form of rule-based automation tied to PR events. However, this is scoped to code review workflows only (triggering on PR open/comment events) rather than a general-purpose event/rule engine for arbitrary automation actions. missing for 10: evidence of a broader/generic rules engine spanning multiple event types beyond PR review, user-defined conditional logic beyond review strictness/custom standards, and independent confirmation these triggers work reliably as described.

   • [claimed-docs] “Set up Greptile AI code reviews in 5 minutes. Connect GitHub or GitLab, configure review triggers, and get automated feedback on your first …”
   • [claimed-docs] “Create custom rules that catch team-specific issues”
   • [claimed-docs] “Place `greptile.json` in your repository root. Settings are read from the source branch of the PR and override dashboard settings.”
   • [claimed-docs] “Control how strict Greptile is about leaving comments with the strictness setting (1–3).”
   • [claimed-docs] “With noise control, Greptile limits reviews to high-signal insights, skipping low impact or repetitive feedback.”
   • [claimed-docs] “Every Greptile review comment includes a **Fix with your Agent** button. Click it, and the issue gets sent straight to your coding agent wit…”
   • [claimed-docs] “Org admins can go to **Settings → Code Review → Default Coding Agents** to turn on Fix with your Agent for the org.”

   proof ↗⚑ flag

   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

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Greptile—none0/10

   Greptile's automation is event-triggered (runs on every PR, via CLI or CI), not evidence of user-defined recurring/scheduled jobs or cron-like workflows; no docs mention scheduling, cron triggers, or periodic batch runs.

   ⚑ flag

   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

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

   weight 1 · round to Graphite
   Greptile~partialclaimed4/10

   Greptile's automation config (`greptile.json`) lives in the repo root and is read per-branch, which implicitly gives git-based versioning and revertibility, and dashboard settings like strictness/custom rules can presumably be changed — but there is no explicit dashboard version history, audit log, or documented rollback feature for automation settings themselves. Missing for 10: explicit versioning/audit-trail UI for automation configs, a documented rollback/undo mechanism, and any review workflow for changes to the automation rules beyond relying on git for the JSON file.

   • [claimed-docs] “Place `greptile.json` in your repository root. Settings are read from the source branch of the PR and override dashboard settings.”
   • [claimed-docs] “Control how strict Greptile is about leaving comments with the strictness setting (1–3).”
   • [claimed-docs] “Create custom rules that catch team-specific issues”
   • [claimed-docs] “Greptile learns from your team's feedback to provide increasingly relevant suggestions. The primary training methods are emoji reactions and…”

   proof ↗⚑ flag

   Graphite~partialclaimed5/10

   Graphite's AI Agents and GT MCP generate changes as ordinary PR/stack commits (graphite-docs-12, graphite-docs-22, graphite-docs-30), which are then subject to Graphite's git-based versioning, AI/human review (graphite-docs-4, graphite-docs-27) and standard git rollback (amend/rebase, graphite-docs-36). However there is no dedicated feature for versioning, auditing, or rolling back the automations/agent configurations themselves (e.g. custom review rules, agent settings) — the 'Automations' pricing bullet (graphite-docs-33) is undetailed. Missing for 10: explicit docs on automation config version history, audit trail of rule changes, and a rollback mechanism for automation behavior itself.

   • [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] “GT MCP allows AI agents to automatically create stacked PRs, breaking down large AI-generated changes into smaller, reviewable stacked pull …”
   • [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 powered by Graphite Agent help your team build better software by automatically reviewing pull requests and catching bugs before …”
   • [claimed-docs] “Amend staged changes to the relevant commits in the current stack.”
   • [claimed-docs] “Unlimited AI Reviews * AI Review customizations * Automations * Merge Queue”

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

   Greptile's evidence covers per-PR review, codebase-wide Q&A, and self-hosted deployment for large dev teams, but there is no documentation or feature description addressing coherent review of changes spanning multiple repositories or explicit monorepo-scale review orchestration. The only tangentially relevant community evidence (greptile-comm-6) reports a bug where searching a large, many-branch repo (Cassandra) failed to surface correct results, which does not support (and mildly undercuts) coherent large-scale/monorepo understanding.

   • [claimed-docs] “Greptile is an AI code review agent that automatically reviews every pull request with complete understanding of your codebase.”
   • [community] “Loading a repo with many branches (cassandra), searching for 'vsearch' surfaced branch-named results (CNDB-8708-vsearch, DSP-23946-vsearch) …”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Graphite
   Greptile~partialcommunity6/10

   Greptile's docs explicitly claim reviews use 'complete understanding of your codebase' (greptile-docs-1), index existing rule/convention files like AGENTS.md/cursor.rules (greptile-docs-35), and support custom team-specific rules (greptile-docs-21) that presumably span beyond the diff. A community hands-on report corroborates deep repo-level Q&A accuracy (greptile-comm-1), but other hands-on reports describe incomplete/incorrect answers on complex code (templates) and reliability failures on some repos (greptile-comm-3, greptile-comm-4, greptile-comm-5), showing the whole-repo understanding is inconsistent in practice. Missing for 10: independent verification specifically that PR review COMMENTS (not just Q&A) cite call sites/related modules beyond the diff, and resolution of the negative reliability reports.

   • [claimed-docs] “Greptile is an AI code review agent that automatically reviews every pull request with complete understanding of your codebase.”
   • [claimed-docs] “Automatically index existing rule files like Claude.md, AGENTS.md, and cursor.rules for richer review context.”
   • [claimed-docs] “Create custom rules that catch team-specific issues”
   • [community] “Asked Greptile about how BigDecimal is encoded in as_json in Rails; got an accurate answer matching what user learned from PRs/issues/code r…”
   • [community] “Tried it on my own C++ codebase - impressed it found the C++ standard used, but it's really bad at analyzing templates; answers always incom…”
   • [community] “Not a single repo I've tried works. A lot of them seem not to have finished processing, but even the ones that have finished don't work.”

   proof ↗⚑ flag

   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

Memory

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

   weight 2 · round to Greptile
   Greptile✓fullclaimed7/10

   Greptile documents a persistent-learning system: thumbs up/down reactions and comments train the model over weeks (docs-4, docs-33), custom rules/patterns can be created and searched via MCP (docs-21, docs-30), team conventions are codified in a `greptile.json` config that overrides defaults per-repo (docs-22), and existing rule files like CLAUDE.md/AGENTS.md/cursor.rules are auto-indexed for context (docs-35, docs-31). This directly matches the story of building and applying a persistent memory of conventions/past decisions to future PRs. Missing for 10: independent/hands-on confirmation that the learning system measurably reduces noise over time as claimed, and community evidence is mixed/dated rather than specifically validating the memory feature.

   • [claimed-docs] “Your 👍/👎 reactions and replies teach Greptile what matters. After 2-3 weeks, it stops commenting on things you don't care about.”
   • [claimed-docs] “Greptile learns from your team's feedback to provide increasingly relevant suggestions. The primary training methods are emoji reactions and…”
   • [claimed-docs] “Create custom rules that catch team-specific issues”
   • [claimed-docs] “Place `greptile.json` in your repository root. Settings are read from the source branch of the PR and override dashboard settings.”
   • [claimed-docs] “With MCP, you can view, search, and create patterns from your IDE.”
   • [claimed-docs] “Automatically index existing rule files like Claude.md, AGENTS.md, and cursor.rules for richer review context.”
   • [claimed-docs] “`greptile onboard` creates your organization, connects GitHub or GitLab, enables repositories, and imports your existing AI rules files — th…”
   • [claimed-docs] “With noise control, Greptile limits reviews to high-signal insights, skipping low impact or repetitive feedback.”

   proof ↗⚑ flag

   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

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

   Docs confirm the PR-thread reply channel exists and is used to tune reviews (👍/👎 and replies 'teach' Greptile, greptile-docs-4/33), and one community report shows Greptile answering a direct codebase question accurately (greptile-comm-1), while another notes it gives authors 'a chance to reply' during review (greptile-comm-8). However, there's no explicit documentation of replying with a question/command in-thread and receiving a contextual answer (as opposed to reaction-based learning), and other community reports show inconsistent/failed query handling (greptile-comm-3,4,5,7). Missing for 10: first-party docs explicitly describing PR-thread Q&A/command handling and consistent independent confirmation of in-context answers.

   • [claimed-docs] “Your 👍/👎 reactions and replies teach Greptile what matters. After 2-3 weeks, it stops commenting on things you don't care about.”
   • [claimed-docs] “Greptile learns from your team's feedback to provide increasingly relevant suggestions. The primary training methods are emoji reactions and…”
   • [community] “Asked Greptile about how BigDecimal is encoded in as_json in Rails; got an accurate answer matching what user learned from PRs/issues/code r…”
   • [community] “My employer uses greptile and I'm pretty happy with it. Sometimes it can be a bit overzealous but more often than not it catches real issues…”
   • [community] “Tried it on my own C++ codebase - impressed it found the C++ standard used, but it's really bad at analyzing templates; answers always incom…”
   • [community] “Not a single repo I've tried works. A lot of them seem not to have finished processing, but even the ones that have finished don't work.”

   proof ↗⚑ flag

   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

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

   Greptile supports on-demand review via CLI (`greptile review`), configurable strictness/noise control, custom rules, and per-branch settings via greptile.json read from the source branch, plus generic 'configure review triggers' in quickstart — giving developers some control over when/how reviews run. However there is no explicit evidence of skipping draft PRs or filtering by label, which the story specifically calls out. Missing for 10: explicit draft-PR skip toggle, label-based filtering, and independent confirmation these controls work as documented.

   • [claimed-docs] “Set up Greptile AI code reviews in 5 minutes. Connect GitHub or GitLab, configure review triggers, and get automated feedback on your first …”
   • [claimed-docs] “Run `greptile review`, get a review of the feature branch diff in 60 seconds.”
   • [claimed-docs] “Control how strict Greptile is about leaving comments with the strictness setting (1–3).”
   • [claimed-docs] “Create custom rules that catch team-specific issues”
   • [claimed-docs] “Place `greptile.json` in your repository root. Settings are read from the source branch of the PR and override dashboard settings.”
   • [claimed-docs] “With noise control, Greptile limits reviews to high-signal insights, skipping low impact or repetitive feedback.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Greptile
   Greptile~partialprobed5/10

   Greptile exposes significant non-UI surfaces — a CLI (`greptile onboard`, `greptile review`) and an official MCP server (fetch PR comments, apply fixes, manage patterns) — that mirror parts of the UI experience (docs-14, docs-23, docs-24, docs-31, probe-4, probe-5). However, no OpenAPI/REST API spec was found (all candidate paths 404'd, greptile-probe-3), and several admin-level settings (e.g., 'Default Coding Agents' toggle, org onboarding via dashboard) are documented as UI-only (Settings → Code Review, docs-34), suggesting incomplete API/CLI parity for configuration and org management. missing for 10: a documented general-purpose REST/GraphQL API or OpenAPI spec, and evidence that all dashboard admin settings (strictness, default agents, org config) can be set via CLI/MCP rather than only the web UI.

   • [claimed-docs] “Run `greptile review`, get a review of the feature branch diff in 60 seconds.”
   • [claimed-docs] “Fetch PR comments - Get unaddressed Greptile feedback for any PR”
   • [claimed-docs] “Connect Cursor, Claude Code, VS Code, or Codex to Greptile MCP with OAuth.”
   • [claimed-docs] “`greptile onboard` creates your organization, connects GitHub or GitLab, enables repositories, and imports your existing AI rules files — th…”
   • [claimed-docs] “Org admins can go to **Settings → Code Review → Default Coding Agents** to turn on Fix with your Agent for the org.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.greptile.com/openapi.json, https://www.greptile.com/swagger.json, https://www.greptile.c…”
   • [probe] “official MCP server documented at https://www.greptile.com/docs/mcp-v2/overview”
   • [probe] “official CLI documented at https://www.greptile.com/docs/code-review/greptile-cli”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Graphite
   Greptile—none0/10

   No evidence of any data export feature or open-format data portability for user data (reviews, patterns, learned rules, etc.); self-hosting only affects where data lives, not exportability. Self-hosted deployment keeps logs on customer servers, but there's no documented export mechanism or open-format dump users can take with them if they leave.

   • [claimed-docs] “Security page, self-hosting and logging: "For self-hosted Greptile services, Custom Apps are hosted using your own infrastructure - such as …”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Greptile—none0/10

   Greptile is a closed, commercial SaaS/self-hosted product (deployed via Docker Compose/Kubernetes) with no evidence of an open-source license or publicly readable source code; self-hosting means running their binaries, not accessing source.

   • [claimed-docs] “Deploy Greptile in your own infrastructure with Docker Compose. Supports AWS, GCP, Azure, air-gapped environments, and custom LLM configurat…”
   • [claimed-docs] “Docker Compose: Up to 100 developers. Single VM, simpler operations. Kubernetes: 100+ developers. Horizontal scaling, high availability.”
   • [claimed-docs] “Security page, self-hosting and logging: "For self-hosted Greptile services, Custom Apps are hosted using your own infrastructure - such as …”

   proof ↗⚑ flag

   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

4. ai-native userSelf-host the core product

   weight 3 · round to Greptile
   Greptile✓fullclaimed7/10

   Greptile documents a self-hosted deployment option via Docker Compose or Kubernetes, supporting AWS/GCP/Azure/air-gapped environments and custom/self-hosted LLMs, with logs stored only on customer servers. This is first-party documentation only, without independent/hands-on corroboration of a working self-hosted deployment. Missing for 10: independent verification that self-hosting actually works end-to-end, and clarity on whether 'core product' (all review/agent features) is fully feature-complete in self-hosted mode.

   • [claimed-docs] “Deploy Greptile in your own infrastructure with Docker Compose. Supports AWS, GCP, Azure, air-gapped environments, and custom LLM configurat…”
   • [claimed-docs] “Docker Compose: Up to 100 developers. Single VM, simpler operations. Kubernetes: 100+ developers. Horizontal scaling, high availability.”
   • [claimed-docs] “If your GitHub or GitLab instance restricts inbound traffic to specific IP addresses, you need to allowlist Greptile's IP range for code rev…”
   • [claimed-docs] “Security page, self-hosting and logging: "For self-hosted Greptile services, Custom Apps are hosted using your own infrastructure - such as …”

   proof ↗⚑ flag

   Graphite—none0/10

   Graphite is a cloud SaaS product (CLI + hosted review/merge queue service) with no evidence of a self-hostable server/core; docs describe hosted authentication via GitHub App, cloud-based AI review, and pricing tiers, none of which mention on-prem or self-hosted deployment options.

   • [claimed-docs] “you'll need to authenticate by installing the Graphite App (a GitHub App) on your organization.”
   • [claimed-docs] “you'll need to authenticate by installing the Graphite App (a GitHub App) on your organization”
   • [claimed-docs] “Unlimited AI Reviews * AI Review customizations * Automations * Merge Queue”
   • [probe] “PROBE openapi: all candidate paths 404 (https://graphite.com/openapi.json, https://graphite.com/swagger.json, https://graphite.com/api/opena…”

   proof ↗⚑ 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 Greptile
   Greptile~partialcommunity7/10

   Docs clearly describe installing via GitHub/GitLab, automated PR reviews within 5 minutes (greptile-docs-5), and native review comments with actionable buttons (greptile-docs-1, greptile-docs-2, greptile-docs-36). Community testimony (greptile-comm-8) corroborates real-world use catching issues on PRs, but other community reports describe reliability issues (stuck processing, internal errors) with the underlying platform, and no independent source specifically confirms the 'minutes to install' claim or inline-comment UX end-to-end. missing for 10: independent hands-on confirmation of install speed and native inline-comment rendering, and resolution of community-reported reliability issues.

   • [claimed-docs] “Greptile is an AI code review agent that automatically reviews every pull request with complete understanding of your codebase.”
   • [claimed-docs] “Every review comment includes a Fix with your Agent button that sends the issue — with file paths, line numbers, and suggested code — straig…”
   • [claimed-docs] “Set up Greptile AI code reviews in 5 minutes. Connect GitHub or GitLab, configure review triggers, and get automated feedback on your first …”
   • [claimed-docs] “Every Greptile review comment includes a **Fix with your Agent** button. Click it, and the issue gets sent straight to your coding agent wit…”
   • [community] “My employer uses greptile and I'm pretty happy with it. Sometimes it can be a bit overzealous but more often than not it catches real issues…”
   • [community] “Not a single repo I've tried works. A lot of them seem not to have finished processing, but even the ones that have finished don't work.”
   • [community] “Ran it on my OSS project - stuck at 99% loading for ~30 minutes, then got 'Error: Internal error while locating sources' on every query. 'Th…”

   proof ↗⚑ flag

   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

Suggestions

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

   weight 3 · round to Graphite
   Greptile~partialclaimed5/10

   Greptile's review comments include a one-click 'Fix with your Agent' button that sends suggested code with file/line context to an external coding agent (Claude Code, Cursor, Codex, Devin) to apply the fix, and a 'Fix All' button for bulk sends (greptile-docs-2, greptile-docs-3, greptile-docs-36, greptile-docs-10). This is a one-click flow but requires routing through a separate coding agent to actually commit the change, rather than a native inline 'commit suggestion' diff applied directly in the PR. Missing for 10: evidence of a native GitHub-style suggested-diff with a direct 'commit suggestion' button that applies without invoking an external agent, and independent/hands-on confirmation that the agent-applied fix actually commits cleanly.

   • [claimed-docs] “Every review comment includes a Fix with your Agent button that sends the issue — with file paths, line numbers, and suggested code — straig…”
   • [claimed-docs] “A Fix All button in the review summary sends every issue at once.”
   • [claimed-docs] “Launch any agent in one click with a Greptile comment, full context, and suggested fix.”
   • [claimed-docs] “Every Greptile review comment includes a **Fix with your Agent** button. Click it, and the issue gets sent straight to your coding agent wit…”
   • [claimed-docs] “Org admins can go to **Settings → Code Review → Default Coding Agents** to turn on Fix with your Agent for the org.”

   proof ↗⚑ flag

   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

Summaries

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

   weight 2 · round to Greptile
   Greptile✓fullcommunity7/10

   Greptile's docs describe automatic review of every PR with full codebase context, a 0-5 merge-safety score, and auto-generated sequence diagrams/flowcharts for every PR specifically to help parse complex changes — directly matching the 'summary + walkthrough' story. Community evidence (comm-8) corroborates real-world use where Greptile catches issues before human review, giving reviewers a head start. Missing for 10: no independent verification of diagram/summary quality or accuracy, and no evidence separating 'summary' as a distinct named artifact from the diagrams/score/comments bundle.

   • [claimed-docs] “Greptile is an AI code review agent that automatically reviews every pull request with complete understanding of your codebase.”
   • [claimed-docs] “Know how safe a PR is to merge at a glance with a 0-5 score”
   • [claimed-docs] “Parse complex changes with sequence diagrams and flowcharts generated for every PR”
   • [community] “My employer uses greptile and I'm pretty happy with it. Sometimes it can be a bit overzealous but more often than not it catches real issues…”

   proof ↗⚑ flag

   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

Updates

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

   weight 2 · round to Greptile
   Greptile~partialclaimed7/10

   Docs describe Greptile tracking 'unaddressed' vs resolved comments and iterating until a PR reaches a perfect review (zero unresolved comments), implying it distinguishes fixed issues from outstanding ones across pushes, and the learning system adapts based on reactions to avoid repeating unwanted comments. However, there's no explicit first-party statement that a new commit push specifically triggers a fresh incremental review pass distinct from prior comments, and no independent/hands-on evidence confirming this exact re-review behavior in practice. Missing for 10: explicit doc on push-triggered incremental review mechanics, and community/hands-on confirmation that old fixed comments are not repeated after new commits.

   • [claimed-docs] “Iteratively fix a PR until Greptile gives a perfect review: 5/5 confidence, zero unresolved comments.”
   • [claimed-docs] “Fetch PR comments - Get unaddressed Greptile feedback for any PR”
   • [claimed-docs] “Greplooping Iteratively fix a PR until Greptile gives a perfect review: 5/5 confidence, zero unresolved comments.”
   • [claimed-docs] “List unaddressed Greptile comments for PR #5 in owner/repo”
   • [claimed-docs] “Your 👍/👎 reactions and replies teach Greptile what matters. After 2-3 weeks, it stops commenting on things you don't care about.”
   • [claimed-docs] “Greptile learns from your team's feedback to provide increasingly relevant suggestions. The primary training methods are emoji reactions and…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Greptile
   Greptile~partialclaimed6/10

   Greptile lets customers self-host the entire platform on their own infrastructure (AWS, GCP, Azure, or air-gapped) inside their own VPC, which effectively gives full control over where data physically resides, and logging can be disabled entirely in that mode. However, there is no documented region-selection feature for the standard hosted/SaaS offering (e.g., no EU vs US data-residency toggle) — residency is achieved only via the heavier self-hosting path, not as a first-class SaaS setting. Missing for 10: explicit hosted multi-region data residency options, third-party confirmation of self-host residency compliance (SOC2/GDPR data residency certifications).

   • [claimed-docs] “Deploy Greptile in your own infrastructure with Docker Compose. Supports AWS, GCP, Azure, air-gapped environments, and custom LLM configurat…”
   • [claimed-docs] “Docker Compose: Up to 100 developers. Single VM, simpler operations. Kubernetes: 100+ developers. Horizontal scaling, high availability.”
   • [claimed-docs] “Security page, self-hosting and logging: "For self-hosted Greptile services, Custom Apps are hosted using your own infrastructure - such as …”
   • [claimed-docs] “Security page, De-Identified Data and AI Training (vendor's own carve-out): "Greptile may aggregate and anonymize Customer Data ('De-Identif…”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Graphite
   Greptile~partialclaimed4/10

   Greptile's own security page states it may use de-identified customer data for 'AI Training and Learnings' as a standing carve-out, with no explicit toggle to opt out of this for standard hosted customers — only self-hosted deployments (with logging fully disabled and data kept in the customer's own VPC) offer a documented path to keep data out of Greptile's hands. This gives privacy-focused users a workaround (self-host) but not a clean, guaranteed 'no AI training' control for the mainstream SaaS offering. Missing for 10: an explicit opt-out/toggle for hosted customers to disable AI-training use of their (even de-identified) data, and independent confirmation that self-hosted mode fully excludes any data from training.

   • [claimed-docs] “Security page, self-hosting and logging: "For self-hosted Greptile services, Custom Apps are hosted using your own infrastructure - such as …”
   • [claimed-docs] “Security page, De-Identified Data and AI Training (vendor's own carve-out): "Greptile may aggregate and anonymize Customer Data ('De-Identif…”

   proof ↗⚑ flag

   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

3. ai-native userControl data retention and deletion

   weight 2 · round to Greptile
   Greptile~partialclaimed5/10

   Greptile's security docs let customers self-host so logs stay only on their own servers and let customers turn off logging entirely for 100% private chats, which is meaningful retention control (greptile-supp-1). However, the same page discloses a standing carve-out that Greptile may aggregate/anonymize Customer Data for AI training even when logging is limited (greptile-supp-2), and there is no documented self-service deletion mechanism, retention period, or explicit 'delete my data' control for the standard SaaS offering. Missing for 10: explicit data-deletion API/workflow for cloud customers, documented retention windows, and clarity on how the AI-training carve-out interacts with opt-out settings.

   • [claimed-docs] “Security page, self-hosting and logging: "For self-hosted Greptile services, Custom Apps are hosted using your own infrastructure - such as …”
   • [claimed-docs] “Security page, De-Identified Data and AI Training (vendor's own carve-out): "Greptile may aggregate and anonymize Customer Data ('De-Identif…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Greptile
   Greptile~partialclaimed4/10

   Self-hosted deployments let customers 'turn off logging and make chats 100% private' (greptile-supp-1), but the standard/SaaS offering explicitly reserves the right to aggregate and anonymize customer data for 'AI Training and Learnings' (greptile-supp-2) with no documented opt-out mechanism for that telemetry. Missing for 10: an explicit SaaS-tier telemetry/usage-tracking opt-out toggle, and independent confirmation that opting out actually stops data collection.

   • [claimed-docs] “Security page, self-hosting and logging: "For self-hosted Greptile services, Custom Apps are hosted using your own infrastructure - such as …”
   • [claimed-docs] “Security page, De-Identified Data and AI Training (vendor's own carve-out): "Greptile may aggregate and anonymize Customer Data ('De-Identif…”

   proof ↗⚑ flag

   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

Analytics

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

   weight 1 · round to Graphite
   Greptile—none0/10

   The evidence describes per-PR review comments, strictness/noise-control settings, learning from feedback, and CLI/MCP integrations, but no org-level dashboard aggregating findings, acceptance rates, or review coverage metrics across teams/repos is documented anywhere in the pack.

   ⚑ flag

   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

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

   Greptile documents review scoring (0-5 safety score, 5/5 confidence) and comment resolution tracking, but no evidence describes a required GitHub/GitLab status check, branch-protection integration, or a blocking review mechanism that would actually prevent a merge until critical findings are resolved.

   ⚑ flag

   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

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

   Docs describe substantive bug-catching capability beyond style — TREX runtime sandbox that surfaces race conditions/logic bugs via traces and screenshots, static+AI security scanning, and v5's parallel agent swarm claiming fewer false positives and more real bugs caught. Community evidence partially corroborates real-world value (comm-8: 'catches real issues... gives author a chance to fix before human reviews') but also shows mixed accuracy experiences on complex code (comm-3: incomplete/incorrect answers on C++ templates) and reliability hiccups reported for the platform generally. Missing for 10: independent, PR-review-specific benchmarks or hands-on accounts confirming it reliably finds logic errors/race conditions (not just Q&A accuracy), and no rebuttal to the noted accuracy gaps.

   • [claimed-docs] “TREX runs your PR branch in a sandbox to find the bugs that only show up at runtime. It starts services, mocks inputs, clicks through UI flo…”
   • [claimed-docs] “Greptile pairs static scanning with an AI security agent to catch vulnerabilities in every pull request.”
   • [claimed-docs] “v5 is faster, catches more bugs, and flags fewer false positives by running a swarm of narrowly scoped agents in parallel.”
   • [community] “My employer uses greptile and I'm pretty happy with it. Sometimes it can be a bit overzealous but more often than not it catches real issues…”
   • [community] “Tried it on my own C++ codebase - impressed it found the C++ standard used, but it's really bad at analyzing templates; answers always incom…”

   proof ↗⚑ flag

   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

Learning

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

   weight 2 · round to Greptile
   Greptile~partialclaimed7/10

   Docs explicitly describe a learning loop where 👍/👎 reactions and reply comments train Greptile to stop repeating feedback team members don't want, with noise control filtering repetitive comments (greptile-docs-4, greptile-docs-33, greptile-docs-32). However, this is described as a team-wide, multi-week aggregate learning process rather than an immediate per-developer 'push back once and it never repeats' guarantee, and no independent/hands-on evidence confirms the mechanism works as described. Missing for 10: independent corroboration of the learning behavior, and clarity on whether a single developer's pushback (vs. team consensus over weeks) suppresses a specific rejected comment.

   • [claimed-docs] “Your 👍/👎 reactions and replies teach Greptile what matters. After 2-3 weeks, it stops commenting on things you don't care about.”
   • [claimed-docs] “Greptile learns from your team's feedback to provide increasingly relevant suggestions. The primary training methods are emoji reactions and…”
   • [claimed-docs] “With noise control, Greptile limits reviews to high-signal insights, skipping low impact or repetitive feedback.”

   proof ↗⚑ flag

   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

Noise

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

   weight 3 · round to Greptile
   Greptile~partialcommunity6/10

   Greptile documents multiple noise-reduction mechanisms: adjustable strictness/nitpickiness (docs-20, docs-32), a learning system trained via 👍/👎 reactions that stops flagging things teams don't care about (docs-4, docs-33), custom rules to catch team-specific issues (docs-21), and a v5 update claiming 'fewer false positives' via parallel narrow-scope agents (docs-26). However, hands-on community evidence is mixed: one enterprise user reports Greptile is 'sometimes overzealous' even while generally catching real issues (greptile-comm-8), indicating the noise-reduction promise isn't fully realized in practice, and there's no independent data on deduplication or severity-labeling accuracy. Missing for 10: independent verification of false-positive rate reduction, evidence of comment deduplication specifically, and confirmation severity labels are reliably applied and trusted by teams.

   • [claimed-docs] “Your 👍/👎 reactions and replies teach Greptile what matters. After 2-3 weeks, it stops commenting on things you don't care about.”
   • [claimed-docs] “Control how strict Greptile is about leaving comments with the strictness setting (1–3).”
   • [claimed-docs] “With noise control, Greptile limits reviews to high-signal insights, skipping low impact or repetitive feedback.”
   • [claimed-docs] “Greptile learns from your team's feedback to provide increasingly relevant suggestions. The primary training methods are emoji reactions and…”
   • [claimed-docs] “v5 is faster, catches more bugs, and flags fewer false positives by running a swarm of narrowly scoped agents in parallel.”
   • [claimed-docs] “Create custom rules that catch team-specific issues”
   • [community] “My employer uses greptile and I'm pretty happy with it. Sometimes it can be a bit overzealous but more often than not it catches real issues…”

   proof ↗⚑ flag

   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

Security

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

   weight 2 · round to Greptile
   Greptile✓fullcommunity6/10

   Greptile has a dedicated security-check feature explicitly pairing static scanning with an AI security agent to catch vulnerabilities on every PR, alongside its general review pipeline that flags functional bugs and code-quality issues in the same diff comments. However, missing for 10: independent/hands-on evidence confirming detection of specific vuln classes like injection or leaked secrets, and no community reports specifically validating security-finding accuracy (community feedback only covers general bug-catching, not security).

   • [claimed-docs] “Greptile pairs static scanning with an AI security agent to catch vulnerabilities in every pull request.”
   • [claimed-docs] “Greptile is an AI code review agent that automatically reviews every pull request with complete understanding of your codebase.”
   • [claimed-docs] “v5 is faster, catches more bugs, and flags fewer false positives by running a swarm of narrowly scoped agents in parallel.”
   • [community] “My employer uses greptile and I'm pretty happy with it. Sometimes it can be a bit overzealous but more often than not it catches real issues…”

   proof ↗⚑ flag

   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

Cli

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

   weight 2 · round to Greptile
   Greptile~partialprobed5/10

   Greptile ships an official CLI (`greptile review`, `greptile onboard`) that reviews local/feature-branch diffs and returns a 0-5 safety score, and docs note coding agents can invoke the CLI to review their own code, implying scriptable/automatable use. However, there is no explicit documentation of a machine-readable output format (e.g., JSON flag) or dedicated CI pipeline integration examples — only an OpenAPI/CLI probe confirming the CLI page exists with no schema found. Missing for 10: documented JSON/structured output mode, explicit CI script examples, and independent confirmation of CLI reliability in automation contexts.

   • [claimed-docs] “Run `greptile review`, get a review of the feature branch diff in 60 seconds.”
   • [claimed-docs] “Coding agents can use the greptile cli to review their own code”
   • [claimed-docs] “Set up Greptile from your terminal with `greptile onboard` — or hand this page to your coding agent and have it run the setup for you.”
   • [claimed-docs] “`greptile onboard` creates your organization, connects GitHub or GitLab, enables repositories, and imports your existing AI rules files — th…”
   • [probe] “official CLI documented at https://www.greptile.com/docs/code-review/greptile-cli”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.greptile.com/openapi.json, https://www.greptile.com/swagger.json, https://www.greptile.c…”

   proof ↗⚑ flag

   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

Ide

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

   weight 2 · round to Greptile
   Greptile~partialprobed6/10

   Greptile's core product reviews pull requests after they are opened, but its CLI (`greptile review`) can review a feature-branch diff locally in ~60 seconds, and its MCP server lets Cursor/Claude Code/VS Code/Codex surface review comments and patterns directly in the editor, which together approximate a pre-push, in-IDE review loop. However, this is CLI/MCP-triggered rather than a live, continuous in-editor reviewer, and there is no independent/hands-on evidence confirming the pre-push workflow works as described. Missing for 10: evidence of automatic/real-time in-editor annotations (not just CLI/MCP triggered), independent user confirmation of the pre-push flow, and clarity that MCP comments are available before a PR/push exists rather than only fetching existing PR feedback.

   • [claimed-docs] “Run `greptile review`, get a review of the feature branch diff in 60 seconds.”
   • [claimed-docs] “Coding agents can use the greptile cli to review their own code”
   • [claimed-docs] “Connect Cursor, Claude Code, VS Code, or Codex to Greptile MCP with OAuth.”
   • [claimed-docs] “With MCP, you can view, search, and create patterns from your IDE.”
   • [claimed-docs] “View and resolve review comments directly from Claude Code.”
   • [probe] “official MCP server documented at https://www.greptile.com/docs/mcp-v2/overview”
   • [probe] “official CLI documented at https://www.greptile.com/docs/code-review/greptile-cli”

   proof ↗⚑ flag

   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

Config

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

   weight 3 · round to Greptile
   Greptile~partialclaimed6/10

   Greptile documents a versioned `greptile.json` config file placed in the repo root that is read from the PR's source branch and overrides dashboard settings, supporting per-repo, version-controlled configuration; related settings like custom rules and strictness/nitpickiness controls are also documented as configurable dials. However, the evidence pack never explicitly confirms path-based filters, per-path instructions, or named 'review profiles' within that config schema — only that dashboard-level settings (rules, strictness) can be overridden via the file. Missing for 10: explicit greptile.json schema showing path-filter syntax, per-path instruction blocks, and named review-profile support.

   • [claimed-docs] “Place `greptile.json` in your repository root. Settings are read from the source branch of the PR and override dashboard settings.”
   • [claimed-docs] “Create custom rules that catch team-specific issues”
   • [claimed-docs] “Control how strict Greptile is about leaving comments with the strictness setting (1–3).”
   • [claimed-docs] “`greptile onboard` creates your organization, connects GitHub or GitLab, enables repositories, and imports your existing AI rules files — th…”

   proof ↗⚑ flag

   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

Governance

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

   weight 1 · round to Greptile
   Greptile~partialclaimed7/10

   Docs show org-level dashboard settings that apply by default, with per-repo greptile.json files that override those defaults for exceptions (greptile-docs-22), org admin controls like Settings → Code Review → Default Coding Agents (greptile-docs-34), and CLI onboarding that creates an org, connects GitHub/GitLab, and enables repositories in bulk (greptile-docs-31). This covers the core mechanics of setting org-wide defaults and per-repo exceptions, but there's no direct evidence of managing hundreds of repos at scale, bulk exception dashboards, role-based admin permissions, or audit/reporting tools for centralized governance. Missing for 10: explicit multi-repo/org-scale management UI, RBAC for admins, and evidence of exception tracking across hundreds of repos.

   • [claimed-docs] “Place `greptile.json` in your repository root. Settings are read from the source branch of the PR and override dashboard settings.”
   • [claimed-docs] “Org admins can go to **Settings → Code Review → Default Coding Agents** to turn on Fix with your Agent for the org.”
   • [claimed-docs] “`greptile onboard` creates your organization, connects GitHub or GitLab, enables repositories, and imports your existing AI rules files — th…”
   • [claimed-docs] “Control how strict Greptile is about leaving comments with the strictness setting (1–3).”
   • [claimed-docs] “Create custom rules that catch team-specific issues”

   proof ↗⚑ flag

   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

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 Greptile
   Greptile✓fullclaimed8/10

   Greptile supports custom rules for team-specific issues, a greptile.json config file that overrides dashboard settings, indexing of existing rule files (Claude.md, AGENTS.md, cursor.rules), strictness/noise-control tuning, and a learning system that adapts from emoji reactions/comments — collectively covering natural-language rules, linked style-guide-like imports, and reinforcement learning of preferences. Missing for 10: explicit documentation of AST-pattern-based rule authoring and independent/community validation that custom rules are reliably enforced in practice.

   • [claimed-docs] “Create custom rules that catch team-specific issues”
   • [claimed-docs] “Place `greptile.json` in your repository root. Settings are read from the source branch of the PR and override dashboard settings.”
   • [claimed-docs] “Automatically index existing rule files like Claude.md, AGENTS.md, and cursor.rules for richer review context.”
   • [claimed-docs] “Control how strict Greptile is about leaving comments with the strictness setting (1–3).”
   • [claimed-docs] “With noise control, Greptile limits reviews to high-signal insights, skipping low impact or repetitive feedback.”
   • [claimed-docs] “Greptile learns from your team's feedback to provide increasingly relevant suggestions. The primary training methods are emoji reactions and…”
   • [claimed-docs] “Your 👍/👎 reactions and replies teach Greptile what matters. After 2-3 weeks, it stops commenting on things you don't care about.”

   proof ↗⚑ flag

   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