Greptile Docs

Appearance

Key Features ​

Fresh

Discover Greptile's key features: full codebase context, high-signal reviews, team learning, IDE integration via MCP, and enterprise-grade deployment options.

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

Learn more: Graph-based context

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

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

!Claude Code receiving a detailed fix prompt from Greptile

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

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.

json
{
  "strictness": 2,
  "commentTypes": ["logic", "syntax", "style", "info"],
  "triggerOnUpdates": true,
  "ignorePatterns": "**/*.test.js\n**/vendor/**"
}

Reference: greptile.json configuration

Source

Mirrored from the official Greptile documentation. Self-contained reference copy.