What it does
Greptile reviews pull requests using the context of your whole codebase. It builds a graph of your repository's files, functions and dependencies, then runs parallel agents that look at each change, judge how it affects code outside the diff and raise problems. It learns your standards by reading your engineers' comments, and you can also write rules in plain English. A feature called TREX, marked beta, runs the pull request branch in a sandbox to catch bugs that appear only when the code runs. Review context can be sent from the IDE to Claude Code, Cursor, Codex or Devin, shared with other agents through the Greptile MCP, or handled by a Claude Code plugin. A /greploop command lets a coding agent keep going with Greptile until every issue is fixed. Greptile supports GitHub, GitLab, Bitbucket and Cursor Origin, with more self-managed hosts on the Enterprise plan. Python, JavaScript, TypeScript, Go, Elixir, Java, C, C++, C#, Swift, PHP and Rust get full support, and most other languages are handled with slightly lower response quality. It can be self-hosted in your own AWS environment, optionally with your own LLM providers, and the site lists SOC 2 compliance, SSO and audit logs.
Capabilities
- Graph index of the repository used as review context
- Parallel review agents that flag issues beyond the diff
- Plain-English custom rules and learning from team comments
- TREX sandbox testing of PR branches (beta)
- IDE, MCP and Claude Code plugin links for coding agents
- Self-hosted deployment option
When to use it
- You want pull requests checked with whole-repository context before human review
- You use coding agents and want a validation step that feeds comments back to them
- You need to enforce team-specific coding standards on every pull request
- Your organisation needs code review in a self-hosted or air-gapped environment
