Install
npm install -g greptile@latestShowcase


Try itExperimental
See what an agent can do with Greptile before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; commands tagged live-capable can re-run against the real endpoint from our edge, right now (▶ run live — the exact same request, live and recorded lines always labeled); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -s -X POST https://api.greptile.com/v2/repositories -H 'Content-Type: application/json' -d '{}'recorded session — replayed, not liveVerified integrations
No integration evidence found in our corpus for this product yet — that means none was found, never that it doesn’t integrate.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Autofix agents — stories about autofix agents in this arenaAutofix agentsevidence →
Stories about autofix agents in this arena
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Codebase understanding — how deeply the tool maps your repo — cross-file context, architecture awareness, historyCodebase understandingevidence →
How deeply the tool maps your repo — cross-file context, architecture awareness, history
Interaction — how you steer it — commands, replies, review conversations, configurability in the loopInteractionevidence →
How you steer it — commands, replies, review conversations, configurability in the loop
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Pr integration — stories about pr integration in this arenaPr integrationevidence →
Stories about pr integration in this arena
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Quality gates — stories about quality gates in this arenaQuality gatesevidence →
Stories about quality gates in this arena
Review accuracy — stories about review accuracy in this arenaReview accuracyevidence →
Stories about review accuracy in this arena
Surfaces — where it meets your workflow — IDE, CLI, web, PR comments, CI checksSurfacesevidence →
Where it meets your workflow — IDE, CLI, web, PR comments, CI checks
Workflow config — stories about workflow config in this arenaWorkflow configevidence →
Stories about workflow config in this arena
Story verdicts — every judged story with its evidenceStory verdicts
Follow the green: where the map greys out is where Greptile stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
~6/10
unlocks → Webhooks · Official SDKs · Scoped API keys · Machine-readable spec · Versioning policy · Full data export
Subscribe to events via webhooks
—–
Build against official SDKs
—0/10
Issue scoped/least-privilege API credentials for an agent
—–
Connect an agent via an official MCP server
✓8/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
✓6/10
Explore an interactive API reference with runnable examples
—0/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓8/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
!5/10
Operate the product with natural-language commands
~5/10
Plug MCP servers into this product so it can use their tools
—0/10
Get AI-generated insights and suggestions from my data inside the product
!6/10
Set up automations that run autonomously in the background
✓7/10
Autofix agents — stories about autofix agents in this arenaAutofix agents
Stories about autofix agents in this arena
The reviewer holds the line on AI-generated PRs — it verifies agent-authored code at a volume no human team could review
✓8/10
I define custom agentic pre-merge checks in plain language — 'docs updated', 'tests cover new paths' — that run on every PR
~6/10
I turn a review finding into an applied fix — a committed patch or an agent-generated follow-up — without leaving the PR
✓8/10
Review findings hand off cleanly to my coding agent — copyable fix prompts or direct integration with Claude Code, Cursor, or Codex
✓9/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Codebase understanding — how deeply the tool maps your repo — cross-file context, architecture awareness, historyCodebase understanding
How deeply the tool maps your repo — cross-file context, architecture awareness, history
Interaction — how you steer it — commands, replies, review conversations, configurability in the loopInteraction
How you steer it — commands, replies, review conversations, configurability in the loop
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Pr integration — stories about pr integration in this arenaPr integration
Stories about pr integration in this arena
The reviewer installs as a GitHub/GitLab app and posts reviews as native inline comments on my pull requests within minutes
~7/10
Review comments include committable suggested diffs I can apply with one click
~5/10
Every PR gets an auto-generated summary and change walkthrough so human reviewers orient fast
✓7/10
Pushing new commits triggers an incremental re-review that tracks what was fixed instead of repeating old comments
~7/10
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Quality gates — stories about quality gates in this arenaQuality gates
Stories about quality gates in this arena
Review accuracy — stories about review accuracy in this arenaReview accuracy
Stories about review accuracy in this arena
The reviewer catches real bugs in my PR — logic errors, race conditions, broken edge cases — not just style nits
~6/10
Push back on a bad review comment and the reviewer learns — it stops repeating the same rejected feedback
~7/10
The reviewer keeps noise low — few false positives, deduplicated comments, severity labels — so my team doesn't tune it out
~6/10
Reviews flag security problems in the diff — injection risks, leaked secrets, insecure patterns — alongside functional bugs
✓6/10
Surfaces — where it meets your workflow — IDE, CLI, web, PR comments, CI checksSurfaces
Where it meets your workflow — IDE, CLI, web, PR comments, CI checks
Workflow config — stories about workflow config in this arenaWorkflow config
Stories about workflow config in this arena
I configure the reviewer with a versioned config file in my repo — path filters, per-path instructions, review profiles
~6/10
I roll out org-level review defaults across hundreds of repos and manage exceptions centrally
~7/10
I encode my team's own review guidelines — natural-language rules, AST patterns, or linked style guides — and the reviewer enforces them
✓8/10
Sorted by importance (agentic first) (high → low) · 53/53 stories · click a row’s chevron for the rationale and evidence
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 6/10 | Tprobed | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | disputed | 5/10 | Dcontradicted | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Cclaimed | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | disputed | 6/10 | Dcontradicted | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Xcommunity | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | full | 6/10 | Cclaimed | |
I turn a review finding into an applied fix — a committed patch or an agent-generated follow-up — without leaving the PR C Fixes | developer | Autofix agents — stories about autofix agents in this arenaAutofix agents | 3 | full | 8/10 | Cclaimed | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | full | 7/10 | Cclaimed | |
The reviewer installs as a GitHub/GitLab app and posts reviews as native inline comments on my pull requests within minutes C Platforms | developer | Pr integration — stories about pr integration in this arenaPr integration | 3 | partial | 7/10 | Xcommunity | |
I configure the reviewer with a versioned config file in my repo — path filters, per-path instructions, review profiles C Config | engineering lead | Workflow config — stories about workflow config in this arenaWorkflow config | 3 | partial | 6/10 | Cclaimed | |
Review comments reflect the whole repository — call sites, related modules, existing conventions — not just the changed hunks C Context | developer | Codebase understanding — how deeply the tool maps your repo — cross-file context, architecture awareness, historyCodebase understanding | 3 | partial | 6/10 | Xcommunity | |
The reviewer catches real bugs in my PR — logic errors, race conditions, broken edge cases — not just style nits C Detection | developer | Review accuracy — stories about review accuracy in this arenaReview accuracy | 3 | partial | 6/10 | Xcommunity | |
The reviewer keeps noise low — few false positives, deduplicated comments, severity labels — so my team doesn't tune it out C Noise | engineering lead | Review accuracy — stories about review accuracy in this arenaReview accuracy | 3 | partial | 6/10 | Xcommunity | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partial | 5/10 | Cclaimed | |
Review comments include committable suggested diffs I can apply with one click C Suggestions | developer | Pr integration — stories about pr integration in this arenaPr integration | 3 | partial | 5/10 | Cclaimed | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | partial | 4/10 | Cclaimed | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | 0/10 | ||
Review findings hand off cleanly to my coding agent — copyable fix prompts or direct integration with Claude Code, Cursor, or Codex C Handoff | ai-native user | Autofix agents — stories about autofix agents in this arenaAutofix agents | 2 | full | 9/10 | Cclaimed | |
I encode my team's own review guidelines — natural-language rules, AST patterns, or linked style guides — and the reviewer enforces them C Rules | engineering lead | Workflow config — stories about workflow config in this arenaWorkflow config | 2 | full | 8/10 | Cclaimed | |
The reviewer holds the line on AI-generated PRs — it verifies agent-authored code at a volume no human team could review C Ai authored | ai-native user | Autofix agents — stories about autofix agents in this arenaAutofix agents | 2 | full | 8/10 | Xcommunity | |
Every PR gets an auto-generated summary and change walkthrough so human reviewers orient fast C Summaries | developer | Pr integration — stories about pr integration in this arenaPr integration | 2 | full | 7/10 | Xcommunity | |
Push back on a bad review comment and the reviewer learns — it stops repeating the same rejected feedback C Learning | developer | Review accuracy — stories about review accuracy in this arenaReview accuracy | 2 | partial | 7/10 | Cclaimed | |
Pushing new commits triggers an incremental re-review that tracks what was fixed instead of repeating old comments C Updates | developer | Pr integration — stories about pr integration in this arenaPr integration | 2 | partial | 7/10 | Cclaimed | |
The reviewer builds a persistent memory of my team's conventions and past review decisions and applies it to future PRs C Memory | ai-native user | Codebase understanding — how deeply the tool maps your repo — cross-file context, architecture awareness, historyCodebase understanding | 2 | full | 7/10 | Cclaimed | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partial | 6/10 | Cclaimed | |
I define custom agentic pre-merge checks in plain language — 'docs updated', 'tests cover new paths' — that run on every PR C Checks | ai-native user | Autofix agents — stories about autofix agents in this arenaAutofix agents | 2 | partial | 6/10 | Cclaimed | |
I get the same review inside my IDE before I push, catching issues while the code is still in my editor C Ide | developer | Surfaces — where it meets your workflow — IDE, CLI, web, PR comments, CI checksSurfaces | 2 | partial | 6/10 | Tprobed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 6/10 | Cclaimed | |
Reviews flag security problems in the diff — injection risks, leaked secrets, insecure patterns — alongside functional bugs C Security | security engineer | Review accuracy — stories about review accuracy in this arenaReview accuracy | 2 | full | 6/10 | Xcommunity | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partial | 5/10 | Cclaimed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 5/10 | Tprobed | |
I reply to the reviewer in the PR thread to ask questions, get explanations, or issue commands — and it answers in context C Chat | developer | Interaction — how you steer it — commands, replies, review conversations, configurability in the loopInteraction | 2 | partial | 5/10 | Xcommunity | |
I run reviews from a CLI against local diffs or in CI scripts, with machine-readable output my tooling can consume C Cli | developer | Surfaces — where it meets your workflow — IDE, CLI, web, PR comments, CI checksSurfaces | 2 | partial | 5/10 | Tprobed | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partial | 4/10 | Cclaimed | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | none | 0/10 | ||
The reviewer understands changes that span multiple repositories or a large monorepo and reviews them coherently C Context | engineering lead | Codebase understanding — how deeply the tool maps your repo — cross-file context, architecture awareness, historyCodebase understanding | 2 | none | 0/10 | ||
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | untested | none yet | |
The reviewer can gate merges — a required status check or blocking review that enforces resolution of critical findings C Gates | engineering lead | Quality gates — stories about quality gates in this arenaQuality gates | 2 | none | untested | none yet | |
I roll out org-level review defaults across hundreds of repos and manage exceptions centrally C Governance | engineering lead | Workflow config — stories about workflow config in this arenaWorkflow config | 1 | partial | 7/10 | Cclaimed | |
I control when reviews run — skip drafts, trigger on demand, filter by branch or label — so the bot shows up only when wanted C Control | developer | Interaction — how you steer it — commands, replies, review conversations, configurability in the loopInteraction | 1 | partial | 5/10 | Cclaimed | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | partial | 4/10 | Cclaimed | |
I see dashboards of findings, acceptance rates, and review coverage across my org C Analytics | engineering lead | Quality gates — stories about quality gates in this arenaQuality gates | 1 | none | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 37 stories with headroom
What would move Greptile’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productPlug MCP servers into this product so it can use their tools
nonemoves agent-readyimpact 45
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.
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
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.
Agenticness — how well agents can access and operate the productIssue scoped/least-privilege API credentials for an agent
nonemoves agent-readyimpact 30
Missing: any documentation of API key scopes, permission levels, or least-privilege token issuance for agent access.
Agenticness — how well agents can access and operate the productBuild against official SDKs
nonemoves agent-readyimpact 30
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.
Agenticness — how well agents can access and operate the productSubscribe to events via webhooks
nonemoves agent-readyimpact 30
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.
Agenticness — how well agents can access and operate the productExplore an interactive API reference with runnable examples
nonemoves API qualityimpact 30
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.
Agenticness — how well agents can access and operate the productDownload a machine-readable API spec (OpenAPI or equivalent)
nonemoves API qualityimpact 30
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.
Agenticness — how well agents can access and operate the productRely on versioned APIs with a documented deprecation policy
nonemoves API qualityimpact 30
Missing: versioned API docs, explicit deprecation policy, changelog entries about API version sunsetting.
Showing the top 8 of 37 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map11 surfaces · 40 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
docs34 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Connect an agent via an official MCP server
- Use an official CLI
- Drive the product through a documented public API
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- I define custom agentic pre-merge checks in plain language — 'docs updated', 'tests cover new paths' — that run on every PR
- I turn a review finding into an applied fix — a committed patch or an agent-generated follow-up — without leaving the PR
- Review findings hand off cleanly to my coding agent — copyable fix prompts or direct integration with Claude Code, Cursor, or Codex
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- Version, review, and roll back my automations
- Review comments reflect the whole repository — call sites, related modules, existing conventions — not just the changed hunks
- The reviewer builds a persistent memory of my team's conventions and past review decisions and applies it to future PRs
- I reply to the reviewer in the PR thread to ask questions, get explanations, or issue commands — and it answers in context
- I control when reviews run — skip drafts, trigger on demand, filter by branch or label — so the bot shows up only when wanted
- Do everything through the API that I can do in the UI
- Self-host the core product
- The reviewer installs as a GitHub/GitLab app and posts reviews as native inline comments on my pull requests within minutes
- Review comments include committable suggested diffs I can apply with one click
- Every PR gets an auto-generated summary and change walkthrough so human reviewers orient fast
- Pushing new commits triggers an incremental re-review that tracks what was fixed instead of repeating old comments
- Choose where my data is stored (region/residency)
- Push back on a bad review comment and the reviewer learns — it stops repeating the same rejected feedback
- The reviewer keeps noise low — few false positives, deduplicated comments, severity labels — so my team doesn't tune it out
- Reviews flag security problems in the diff — injection risks, leaked secrets, insecure patterns — alongside functional bugs
- I run reviews from a CLI against local diffs or in CI scripts, with machine-readable output my tooling can consume
- I get the same review inside my IDE before I push, catching issues while the code is still in my editor
- I configure the reviewer with a versioned config file in my repo — path filters, per-path instructions, review profiles
- I roll out org-level review defaults across hundreds of repos and manage exceptions centrally
- I encode my team's own review guidelines — natural-language rules, AST patterns, or linked style guides — and the reviewer enforces them
Hacker News11 stories
- Get AI-generated insights and suggestions from my data inside the product
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- The reviewer holds the line on AI-generated PRs — it verifies agent-authored code at a volume no human team could review
- Review comments reflect the whole repository — call sites, related modules, existing conventions — not just the changed hunks
- I reply to the reviewer in the PR thread to ask questions, get explanations, or issue commands — and it answers in context
- The reviewer installs as a GitHub/GitLab app and posts reviews as native inline comments on my pull requests within minutes
- Every PR gets an auto-generated summary and change walkthrough so human reviewers orient fast
- The reviewer catches real bugs in my PR — logic errors, race conditions, broken edge cases — not just style nits
- The reviewer keeps noise low — few false positives, deduplicated comments, severity labels — so my team doesn't tune it out
- Reviews flag security problems in the diff — injection risks, leaked secrets, insecure patterns — alongside functional bugs
CLI docs11 stories
- Run the product headlessly / in CI for automation
- Use an official CLI
- Drive the product through a documented public API
- Get AI-generated insights and suggestions from my data inside the product
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- I control when reviews run — skip drafts, trigger on demand, filter by branch or label — so the bot shows up only when wanted
- Do everything through the API that I can do in the UI
- Every PR gets an auto-generated summary and change walkthrough so human reviewers orient fast
- I run reviews from a CLI against local diffs or in CI scripts, with machine-readable output my tooling can consume
- I get the same review inside my IDE before I push, catching issues while the code is still in my editor
Independence docs8 stories
- The reviewer holds the line on AI-generated PRs — it verifies agent-authored code at a volume no human team could review
- I define custom agentic pre-merge checks in plain language — 'docs updated', 'tests cover new paths' — that run on every PR
- I turn a review finding into an applied fix — a committed patch or an agent-generated follow-up — without leaving the PR
- Review findings hand off cleanly to my coding agent — copyable fix prompts or direct integration with Claude Code, Cursor, or Codex
- Perform bulk operations across many items at once
- Review comments include committable suggested diffs I can apply with one click
- Pushing new commits triggers an incremental re-review that tracks what was fixed instead of repeating old comments
- I get the same review inside my IDE before I push, catching issues while the code is still in my editor
Changelog docs5 stories
- Set up automations that run autonomously in the background
- The reviewer holds the line on AI-generated PRs — it verifies agent-authored code at a volume no human team could review
- The reviewer catches real bugs in my PR — logic errors, race conditions, broken edge cases — not just style nits
- The reviewer keeps noise low — few false positives, deduplicated comments, severity labels — so my team doesn't tune it out
- Reviews flag security problems in the diff — injection risks, leaked secrets, insecure patterns — alongside functional bugs
Security check docs5 stories
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- The reviewer holds the line on AI-generated PRs — it verifies agent-authored code at a volume no human team could review
- The reviewer catches real bugs in my PR — logic errors, race conditions, broken edge cases — not just style nits
- Reviews flag security problems in the diff — injection risks, leaked secrets, insecure patterns — alongside functional bugs
Security docs5 stories
Trex docs5 stories
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- Test against a sandbox environment without touching production data
- The reviewer holds the line on AI-generated PRs — it verifies agent-authored code at a volume no human team could review
- The reviewer catches real bugs in my PR — logic errors, race conditions, broken edge cases — not just style nits
OpenAPI spec3 stories
Learning docs3 stories
- Review comments reflect the whole repository — call sites, related modules, existing conventions — not just the changed hunks
- The reviewer builds a persistent memory of my team's conventions and past review decisions and applies it to future PRs
- I encode my team's own review guidelines — natural-language rules, AST patterns, or linked style guides — and the reviewer enforces them
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -s -X POST https://api.greptile.com/v2/repositories -H 'Content-Type: application/json' -d '{}'reproduced$ curl -s -X POST https://api.greptile.com/v2/repositories -H 'Content-Type: application/json' -d '{}'
{"error":"No API [redacted] provided"}
$npx -y greptile --versionreproduced$ npx -y greptile --version 3.5.2
$curl -s -X POST https://api.greptile.com/mcp -H 'Content-Type: application/json' -d '<jsonrpc initialize>' # FULL keyless handshakereproduced$ curl -s -X POST https://api.greptile.com/mcp -H 'Content-Type: application/json' -d '<jsonrpc initialize>' # FULL [redacted]less handshake
{"jsonrpc":"2.0","id":1,"result":{"protocolVersion":"2025-03-26","capabilities":{"tools":{}},"serverInfo":{"name":"Greptile MCP Server","version":"1.0.0"},"instructions":"Successful tool results are JSON objects encoded in the text field of the first MCP content block: parse content[0].text before reading fields. Tool errors set isError: true and return a plain-text explanation instead. List tools use either page or offset as documented; a field named total is not necessarily an organization-wide count, so follow each tool's result guidance.\n\nAccount: get_me returns the caller and every orga
$curl -s https://www.greptile.com/docs/llms.txt | head -6reproduced$ curl -s https://www.greptile.com/docs/llms.txt | head -6 # Greptile - [Overview - What is Greptile?](https://www.greptile.com/docs/introduction.md) - [5-Minute Quickstart](https://www.greptile.com/docs/quickstart.md): Set up Greptile AI code reviews in 5 minutes. Connect GitHub or GitLab, configure review triggers, and get automated feedback on your first pull request. - [CLI Onboarding](https://www.greptile.com/docs/code-review/cli-onboarding.md): 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. - [[redacted] Features](https://www.greptile.com/docs/code-review/[redacted]-features.md): Discover Greptile's [redacted] features: full codebase context, high-signal reviews, team learning, IDE integration via MCP, and enterprise-grade deployment options.
$curl -sL https://www.greptile.com/docs/quickstart.md | head -12reproduced$ curl -sL https://www.greptile.com/docs/quickstart.md | head -12 > ## Documentation Index > Fetch the complete documentation index at: https://www.greptile.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # 5-Minute Quickstart > Set up Greptile AI code reviews in 5 minutes. Connect GitHub or GitLab, configure review triggers, and get automated feedback on your first pull request. This guide covers GitHub/GitLab setup, repository configuration, and your first automated code review. ## Installation & Setup
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
10 of 20 testable claims verified · 1 contradicted → integrity 40/100
30 distinct capability claims found in Greptile’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
10
Verified
9
Unverified
1
Contradicted
19
Undersold
Verified (16)
“Automatically reviews every pull request with full understanding of the whole codebase”
Review comments reflect the whole repository — call sites, related modules, existing conventions — not just the changed hunkspartialproof ↗
“Installs by connecting GitHub or GitLab and gives automated PR feedback within minutes of setup”
The reviewer installs as a GitHub/GitLab app and posts reviews as native inline comments on my pull requests within minutespartialproof ↗
“Official CLI (`greptile onboard`) can set up the product from the terminal, usable by a coding agent”
“Review comments, fixes, and coding patterns can be accessed and managed directly from your coding agent”
“CLI command reviews the feature branch diff and returns results in about 60 seconds”
I run reviews from a CLI against local diffs or in CI scripts, with machine-readable output my tooling can consumepartialproof ↗
“Coding agents themselves can invoke the Greptile CLI to review their own generated code”
“Coding agents themselves can invoke the Greptile CLI to review their own generated code”
I run reviews from a CLI against local diffs or in CI scripts, with machine-readable output my tooling can consumepartialproof ↗
“Generates sequence diagrams and flowcharts to help explain complex PR changes”
Every PR gets an auto-generated summary and change walkthrough so human reviewers orient fastfullproof ↗
“TREX runs the PR branch in a sandbox, exercising services and UI flows to catch runtime-only bugs, attaching logs/screenshots/traces”
The reviewer catches real bugs in my PR — logic errors, race conditions, broken edge cases — not just style nitspartialproof ↗
“A strictness setting (1-3) controls how aggressively the reviewer leaves comments”
The reviewer keeps noise low — few false positives, deduplicated comments, severity labels — so my team doesn't tune it outpartialproof ↗
“Can fetch unaddressed review feedback for any PR via CLI/tooling”
I run reviews from a CLI against local diffs or in CI scripts, with machine-readable output my tooling can consumepartialproof ↗
“Cursor, Claude Code, VS Code, and Codex can connect to Greptile via an official MCP server with OAuth”
“Combines static scanning with an AI security agent to catch vulnerabilities in every PR”
Reviews flag security problems in the diff — injection risks, leaked secrets, insecure patterns — alongside functional bugsfullproof ↗
“v5 runs a swarm of narrowly scoped agents in parallel for faster reviews, more bugs caught, fewer false positives”
The reviewer keeps noise low — few false positives, deduplicated comments, severity labels — so my team doesn't tune it outpartialproof ↗
“v5 runs a swarm of narrowly scoped agents in parallel for faster reviews, more bugs caught, fewer false positives”
The reviewer catches real bugs in my PR — logic errors, race conditions, broken edge cases — not just style nitspartialproof ↗
“Detects when a PR was authored by a coding agent and routes review to a different model (e.g., GPT reviews Claude-written code)”
The reviewer holds the line on AI-generated PRs — it verifies agent-authored code at a volume no human team could reviewfullproof ↗
Unverified (15)
“Review comments include a 'Fix with your Agent' button that sends the issue with file/line context to Claude Code, Codex, Conductor, Cursor, or Devin”
Review findings hand off cleanly to my coding agent — copyable fix prompts or direct integration with Claude Code, Cursor, or Codexfullproof ↗
“Review comments include a 'Fix with your Agent' button that sends the issue with file/line context to Claude Code, Codex, Conductor, Cursor, or Devin”
I turn a review finding into an applied fix — a committed patch or an agent-generated follow-up — without leaving the PRfullproof ↗
“A 'Fix All' button sends every flagged issue in a review to the agent at once”
Perform bulk operations across many items at oncepartialproof ↗
“A 'Fix All' button sends every flagged issue in a review to the agent at once”
I turn a review finding into an applied fix — a committed patch or an agent-generated follow-up — without leaving the PRfullproof ↗
“Thumbs up/down reactions and replies teach the reviewer what to stop flagging over time”
Push back on a bad review comment and the reviewer learns — it stops repeating the same rejected feedbackpartialproof ↗
“Can be self-hosted via Docker Compose in your own AWS/GCP/Azure/air-gapped infrastructure with custom LLM configs”
“Self-hosted deployment scales from single-VM Docker Compose (up to 100 devs) to Kubernetes (100+ devs, HA)”
“Any coding agent can be launched in one click from a review comment with full context and suggested fix”
Review findings hand off cleanly to my coding agent — copyable fix prompts or direct integration with Claude Code, Cursor, or Codexfullproof ↗
“Review comments, fixes, and coding patterns can be accessed and managed directly from your coding agent”
Review findings hand off cleanly to my coding agent — copyable fix prompts or direct integration with Claude Code, Cursor, or Codexfullproof ↗
“Review comments can be viewed and resolved directly inside Claude Code”
Review findings hand off cleanly to my coding agent — copyable fix prompts or direct integration with Claude Code, Cursor, or Codexfullproof ↗
“Supports iterating on a PR until the reviewer gives a perfect score with zero unresolved comments”
Pushing new commits triggers an incremental re-review that tracks what was fixed instead of repeating old commentspartialproof ↗
“Supports creating custom rules to catch team-specific issues”
I encode my team's own review guidelines — natural-language rules, AST patterns, or linked style guides — and the reviewer enforces themfullproof ↗
“A `greptile.json` file in the repo root configures review settings, overriding dashboard defaults”
I configure the reviewer with a versioned config file in my repo — path filters, per-path instructions, review profilespartialproof ↗
“Self-hosted deployments run in the customer's own VPC and can also self-host the LLMs used for review”
“Customers can turn off logging entirely so chats are 100% private, with logs stored only on customer servers in self-hosted mode”
Contradicted (1)
“Gives each PR a 0-5 merge-safety confidence score”
The reviewer can gate merges — a required status check or blocking review that enforces resolution of critical findingsnone
Undersold (19)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationfullproof ↗
Drive the product through a documented public APIpartialproof ↗
Set up automations that run autonomously in the backgroundfullproof ↗
Operate the product with natural-language commandspartialproof ↗
Test against a sandbox environment without touching production datafullproof ↗
I define custom agentic pre-merge checks in plain language — 'docs updated', 'tests cover new paths' — that run on every PRpartialproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
The reviewer builds a persistent memory of my team's conventions and past review decisions and applies it to future PRsfullproof ↗
I reply to the reviewer in the PR thread to ask questions, get explanations, or issue commands — and it answers in contextpartialproof ↗
I control when reviews run — skip drafts, trigger on demand, filter by branch or label — so the bot shows up only when wantedpartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Review comments include committable suggested diffs I can apply with one clickpartialproof ↗
Choose where my data is stored (region/residency)partialproof ↗
Prevent my data from being used to train AI modelspartialproof ↗
I get the same review inside my IDE before I push, catching issues while the code is still in my editorpartialproof ↗
I roll out org-level review defaults across hundreds of repos and manage exceptions centrallypartialproof ↗
Claims outside our story set (3)
Real capability claims found in Greptile’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Requires allowlisting Greptile's IP range if GitHub/GitLab restricts inbound traffic”
source ↗“Automatically generates unit tests for new or changed code in a PR”
source ↗“Vendor states it may aggregate and anonymize customer data to train and improve its AI models”
source ↗
Business model
Starter free for 1 active developer; Pro $30/seat/mo with 50 review credits per seat ($1 per extra credit; a TREX sandbox review is 3 credits); self-hostable Enterprise is custom; free for qualified MIT/Apache OSS.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
Agent surface uptime MCP up · llms.txt up (tracking since Sep 11 '26)
