> ## 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.

# Changelog

> The latest updates and improvements to Greptile

<Update label="April 30, 2026" tags={["Billing"]}>
  ## Usage Limits

  You can now set a dollar cap for additional review spend. Reviews beyond the 50 credits included per active developer in a billing period are billed at \$1/credit.

  When projected spend reaches the cap, Greptile skips new reviews until the next billing period or until you raise the limit.

  [Learn about billing and usage limits →](/code-review-bot/billing-seats#usage-limits)
</Update>

<Update label="April 15, 2026" tags={["Dashboard"]}>
  ## Redesigned Web App

  The Greptile dashboard has been rebuilt with a new organization and team hierarchy. Key changes:

  * **Breadcrumb navigation** — Switch between organizations and teams from a single dropdown. The sidebar adapts to show organization-level or team-level pages.
  * **Auto-enable repositories** — Toggle in Code Review Settings to automatically enable Greptile on new repos as they're created in a GitHub org or GitLab group.
  * **Inheritance & Sync** — Team-level settings inherit from the organization. Sync a team back to org defaults with one click.
  * **Analytics dashboard** — Track PRs reviewed, addressed rate, critical bugs caught, merge times, and upvote/downvote ratios. Filter by team, repository, author, and time period. Export data.
  * **Redesigned onboarding** — New users joining an existing organization get a guided setup in Personal Settings: link a GitHub/GitLab profile, install the bridge app, and choose coding agents. Personal review preferences (summary, diagram, collapsible sections) are configured in the same flow.

  [Learn about organizations & teams →](/code-review/team-setup-basics)
  [View the analytics dashboard →](/analytics)
</Update>

<Update label="April 15, 2026" tags={["Config"]}>
  ## Multi-Repo Context

  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.

  ```json theme={}
  {
    "context": {
      "repos": ["acme/shared-types", "acme/payment-sdk"]
    }
  }
  ```

  [.greptile/ reference →](/code-review/greptile-config-reference#cross-repository-context) | [greptile.json reference →](/code-review/greptile-json-reference#cross-repository-context)
</Update>

<Update label="March 28, 2026" tags={["Code Review"]}>
  ## Severity Badges

  Inline review comments now display a severity badge — **P0** (critical), **P1** (high), or **P2** (medium) — so you can triage feedback at a glance.

  [Learn about severity levels →](/code-review/first-pr-review#severity-badges)
</Update>

<Update label="March 25, 2026" tags={["Code Review"]}>
  ## Review Footer Updates

  The review summary footer has been updated with new controls:

  * **Review counter** — Shows how many times Greptile has reviewed the PR (e.g. "Reviews (2)")
  * **Longer commit messages** — The "Last reviewed commit" link now shows more of the commit message for easier identification
  * **Re-trigger button** — Click "Re-trigger Greptile" in the footer to re-run a review without tagging @greptileai

  [See the anatomy of a review →](/code-review/first-pr-review#review-footer)
</Update>

<Update label="March 6, 2026" tags={["Code Review"]}>
  ## Greptile v4

  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.
</Update>

<Update label="March 6, 2026" tags={["Integrations"]}>
  ## Fix in Claude Code, Codex, and Cursor

  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.

  <Frame>
    <img src="https://mintcdn.com/greptile/NbRtsLvWVCnO7zAK/images/fix-in-x-pr-summary.png?fit=max&auto=format&n=NbRtsLvWVCnO7zAK&q=85&s=8b2cfc23233015db04acc8a3ab2e0b31" alt="Greptile PR summary with Fix All button" width="1766" height="1454" data-path="images/fix-in-x-pr-summary.png" />
  </Frame>

  [Set up Fix in X →](/integrations/fix-in-x)
</Update>

<Update label="February 10, 2026" tags={["Config"]}>
  ## Cascading Config Files

  `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.

  [Read the configuration reference →](/code-review/greptile-config-reference)
</Update>

<Update label="January 5, 2026" tags={["Integrations"]}>
  ## Greptile Plugin for Claude Code

  Address Greptile review comments, manage custom context, and trigger reviews directly from Claude Code. Available in the official Anthropic plugin marketplace.

  <Frame>
    <video src="https://mintcdn.com/greptile/CnQscq2HVa0gyXSi/images/claude-code-plugin-demo.mp4?fit=max&auto=format&n=CnQscq2HVa0gyXSi&q=85&s=3a560ee0a0ae3220e3d6907c16d0d7ac" autoPlay muted loop playsInline data-path="images/claude-code-plugin-demo.mp4" />
  </Frame>

  [Set up the Claude Code integration →](/mcp-v2/setup#claude-code-cli)
</Update>

<Update label="December 15, 2025" tags={["Code Review"]}>
  ## Feature Discovery

  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.
</Update>

<Update label="December 2, 2025" tags={["Config"]}>
  ## Wildcard Repository Scopes

  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.

  [Learn about custom standards →](/code-review/custom-standards)
</Update>

<Update label="November 24, 2025" tags={["Config"]}>
  ## Rule Optimization

  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](https://app.greptile.com/review/custom-context).

  <Frame>
    <video src="https://mintcdn.com/greptile/8Cym9aHLqh5ZsjNo/images/rule-optimization-demo.mov?fit=max&auto=format&n=8Cym9aHLqh5ZsjNo&q=85&s=7c5e1ff1f1d1416c7530b99674a3b382" autoPlay muted loop playsInline data-path="images/rule-optimization-demo.mov" />
  </Frame>

  [Learn about custom standards →](/code-review/custom-standards)
</Update>

<Update label="November 18, 2025" tags={["Config"]}>
  ## greptile.json v3 Support

  `greptile.json` configuration file now supports v3 code review settings, including custom instructions, skip rules, comment types, and review triggers.

  [See the full configuration reference →](/code-review/greptile-json-reference)
</Update>

<Update label="October 29, 2025" tags={["Self-Hosting"]}>
  ## GitLab Reverse Proxy Support

  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.

  [View deployment options →](/deployment-options)
</Update>

<Update label="October 16, 2025" tags={["Code Review"]}>
  ## Clarification Questions

  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.

  [See developer essentials →](/code-review/developer-essentials)
</Update>

<Update label="September 29, 2025" tags={["Code Review"]}>
  ## Thread Replies

  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.

  [See developer essentials →](/code-review/developer-essentials)
</Update>

<Update label="September 26, 2025" tags={["Config"]}>
  ## Configurable Models and Turns

  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.

  [Configure your review settings →](/code-review/greptile-config)
</Update>

<Update label="September 22, 2025" tags={["Code Review"]}>
  ## Code Review v3

  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.

  [Explore key features →](/code-review/key-features)
</Update>

<Update label="September 15, 2025" tags={["MCP"]}>
  ## Greptile MCP Server

  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.

  [Get started with the MCP server →](/mcp-v2/overview)
</Update>