Skip to main content

​
Full codebase context

Greptile builds a graph of your repository (functions, classes, imports, dependencies) and uses it during reviews to reason about ripple effects beyond the diff.
  • Surfaces impacted callers and contracts
  • Detects cross-file inconsistencies and missing validations
  • References similar patterns already in your codebase
  • Reads related repositories you add as cross-repo context
Learn more: Graph-based context

​
End-to-end testing with TREX

TREX tests your pull requests end to end. It starts your app in a sandbox, clicks through the flows the change affects, and posts what it found with a video of each flow. Learn more: TREX

​
High-signal findings (not nitpicks)

Focus on issues that matter by default; control verbosity with strictness and comment-type filters.
  • Logic, security, performance, architectural issues by default
  • Style and syntax can be reduced or disabled
  • Per-repository rules with greptile.json
See: Controlling nitpickiness

​
Review tiers

Choose how deep Greptile goes on each pull request.
  • Base: thorough code review with full codebase context
  • Plus: a deeper review for PRs that need extra scrutiny
  • Apex: our most intensive review for large, complex PRs
  • Auto: Greptile picks a tier for each PR from its size, risk, and complexity
  • Set it for the organization, a repository, a directory, a tier rule, or one PR
See: Review tiers

​
Learns your team’s standards

Greptile adapts over time using thumbs up/down and short replies.
  • Suppresses suggestions your team routinely ignores
  • Reinforces patterns your team prefers
  • Auto-discovers custom rules from team discussions
See: Memory and learning

​
Fix All with AI

Every review comment includes a Fix with your Agent button that sends the issue — with file paths, line numbers, and suggested code — directly to your coding agent. A Fix All button in the review summary sends every issue at once.
  • Supports Claude Code, OpenAI Codex, Conductor, Cursor, and Devin
  • Agent receives full context and applies fixes automatically
  • Comments resolve when you push the fix
Default Coding Agents settings: prompt to Fix with AI and org-wide agent defaults
Get started: Fix with your Agent →

​
Auto-resolution from your IDE (MCP)

Resolve Greptile comments without leaving your editor.
  • Open files, apply suggested fixes, mark threads resolved
  • Works with Cursor, Windsurf, Claude Desktop, Codex CLI
Get started: Auto-resolve with MCP

​
Auto-approve low-risk PRs (Beta)

Auto-approve lets Greptile approve pull requests that it rates as low-risk and bug-free. It only approves PRs with a clean 5/5 Greptile review. Use it for changes where an automatic approval is acceptable, like docs, tests, styling, or small code changes.
  • Set the maximum risk level Greptile can approve
  • Add filters to exclude specific labels, branches, files, and authors from auto-approval
  • Leave it off for broad or high-risk review flows. We recommend auto-approve only for low-risk changes
Auto-approve settings: toggle auto-approve, set the maximum risk to auto-approve, and add filters
Turn it on in Auto-approve settings.

​
Enterprise-grade deployment

  • Cloud (SOC2 Type II), self-hosted Docker/Kubernetes, air-gapped
  • SSO/SAML, audit logging, role-based access
  • Customer-managed PostgreSQL + pgvector, Redis (self-hosted)
See: Self-hosting overview

​
Configuration you control

Use greptile.json for repo-level behavior.
greptile.json
Reference: greptile.json configuration