The latest updates and improvements to Greptile.
Greptile now has a free Starter plan for individual developers. Starter includes unlimited repositories and 50 standard reviews per month for a single developer, with no team creation. Key details:
Greptile can now review code with insider context for the third-party APIs your product depends on. When a PR touches a supported partner API, SDK, config, or integration, Greptile reviews the change against partner-maintained docs, implementation rules, and common failure patterns. Key details:
TREX is now available in public beta. With TREX enabled, Greptile doesn't just review your PR, it writes and runs targeted tests in a sandbox, resulting in 20% more bugs caught in evals. Key changes:
You can now run a full Greptile review from your terminal. Install the CLI, check out a branch, and run greptile review to review your current branch against its base branch.
npm i -g greptile
greptile login
greptile reviewKey commands:
greptile review -b main: compare your current branch against a specific base branch.greptile review --resume: continue the latest unfinished review.greptile review --diff: show findings inline with the relevant code.greptile review --json: print machine-readable output.greptile review --agent: print plain text for agent workflows or scripts.You can now create Repo Clusters so Greptile can read related repositories as context during reviews. Group tightly coupled repos once, and whenever Greptile reviews a PR in one of them, it automatically reads the others as read-only context. Key details:
context.repos: define a group once instead of pointing each repo at the others manually.context.repos entries.The .greptile/ folder is now the recommended way to configure Greptile. Place it at the root or in any directory; settings cascade from root to leaf, so child directories inherit parent config and override what they need.
.greptile/
├── config.json # Review settings and structured rules
├── rules.md # Rules written as plain markdown
└── files.json # Existing files the reviewer should read for contextKey details:
config.json: review settings, structured rules, severity, and disable-by-ID.rules.md: plain-English rules scoped to the directory containing the .greptile/ folder.files.json: existing repo files Greptile should read for context, like schemas, API specs, or architecture docs.Greptile's improved memory system learns from your team's comments, replies, reactions, and commits to deliver increasingly personalized review suggestions. Over time, Greptile adapts to your team's coding style, filters suggestions your team ignores, and focuses on the issues that matter to your team. Greptile learns from:
You can now set a dollar cap for flex review spend. Flex reviews are reviews beyond the 50 included reviews per active developer in a billing period.
When projected flex review spend reaches the cap, Greptile skips new flex reviews until the next billing period or until you raise the limit. Included reviews still run.
The Greptile dashboard has been rebuilt with a new organization and team hierarchy. Key changes:
You can now give Greptile read-only access to related repositories during reviews. Add a context.repos field to your .greptile/config.json or greptile.json to reference shared libraries, SDKs, or other repos that help Greptile understand your code.
{
"context": {
"repos": ["acme/shared-types", "acme/payment-sdk"]
}
}Greptile now has security-focused reviews in beta for all users. The new reviewer is better at detecting and surfacing potential vulnerabilities, including preventative patterns that are not vulnerabilities yet but could make future vulnerabilities more likely. Key changes:
Every Greptile review can send review comments straight to Claude Code, OpenAI Codex, Conductor, Cursor, or Devin with full context: the file, line numbers, the comment, and the suggested fix. Key changes:
Inline review comments now display a severity badge, P0 (critical), P1 (high), or P2 (medium), so you can triage feedback at a glance.
The review summary footer has been updated with new controls:
Major upgrade to the review engine. v4 delivers significantly more actionable feedback across the board:
| Metric | Before | After | Change |
|---|---|---|---|
| Addressed comments per PR | 0.92 | 1.60 | +74% |
| Comments addressed by author | 30% | 43% | +43% |
| Positive replies per PR | 0.31 | 0.52 | +68% |
| Upvote reactions per PR | 0.05 | 0.08 | +60% |
"Addressed" is determined by an LLM-as-judge evaluating whether the author acted on each comment.
Every Greptile review comment now includes a Fix in X button. Click it, and the issue gets sent straight to your coding agent (Claude Code, OpenAI Codex, or Cursor) with full context: file paths, line numbers, the review comment, and suggested fixes. Your agent opens, applies the fix, and you review the diff. A Fix All button in the review summary sends every issue at once.
greptile.json files can now be placed in subdirectories to override parent-level review configuration. Settings cascade from root to subdirectory, allowing teams to define org-wide defaults while customizing review behavior for specific folders or modules.
Address Greptile review comments, manage custom context, and trigger reviews directly from Claude Code. Available in the official Anthropic plugin marketplace.
Code reviews now surface contextual tips highlighting relevant Greptile features based on the content of each review, such as custom rules, greptile.json configuration options, and integration capabilities.
Apply rules across all repositories in an organization or group using wildcards (e.g. myorg/* or groupa/subgroupb/*). Wildcard options are automatically generated based on your connected repositories.
Rules can now be generated and refined using AI directly from the custom context dashboard. Try it in the + Add Context dialog at app.greptile.com/review/custom-context.
greptile.json configuration file now supports v3 code review settings, including custom instructions, skip rules, comment types, and review triggers.
Greptile can now connect to self-hosted GitLab instances routed through reverse proxies, supporting environments where GitLab is not directly accessible from the public internet. Configure your reverse proxy URL in your integration settings.
Reviews can now append a clarification question to an inline comment when change intent is ambiguous. Follow-up discussion happens in the same thread via implicit thread replies, with no retrigger required.
Greptile now responds to follow-up comments in review threads. Ask a question, request a revision, or push back on a suggestion and Greptile replies in-thread. A classifier decides whether to respond and skips acknowledgments, approvals, or human-to-human discussion.
Choose which AI model powers your reviews and set the maximum number of agentic turns per review. Configure both in your review settings to balance speed, depth, and cost.
Completely rebuilt review engine around an agentic workflow. Reviews now learn your team's standards from past GitHub and GitLab PR comments, pull context from tools like Jira and Notion, auto-detect project rule files (e.g. CLAUDE.md, .cursor/rules), and include a copy-prompt action on each comment for quick fixes in your editor.
Greptile is now available as an MCP server, bringing code reviews into your AI-powered development environment. Trigger and re-run reviews, inspect results, manage custom context, and update repository rules without leaving your editor.