CodeRabbit Release Notes

Connections and scopes

Connecting CodeRabbit to issue trackers, documentation systems, analytics tools, and other external services used to mean setting up the same service separately for pull request reviews, Agent for Slack, and Agent for Discord. That setup is now unified: configure each connector once as a saved connection, then use scopes to control exactly where every product can use it, whether that's a repository for Review or a channel, conversation, or server for Slack and Discord.

A Base Scope defines each product's default connection access, and named scopes can inherit, exclude, or override it for specific repositories, teams, or sub-projects, so a security-sensitive repository or channel can be kept off a connection that the rest of the organization uses freely.

See the Connections documentation and Scopes overview for setup details.

Project vocabulary |

Comment @coderabbitai generate project vocabulary on a pull request to receive an alphabetized Markdown list of up to 50 terms specific to that repository. CodeRabbit explores source code, product documentation, and configuration; preserves the selected spelling and capitalization; and leaves out generic software terminology, common frameworks and dependencies, file paths, and terms found only in instruction files.

The command requires an active Essentials plan or higher. See the Code review command reference for usage details and supported aliases.

CLI v0.7.6

CLI v0.7.6 improves large-review handling, expands security finding output, and makes usage reporting more accurate.

Large reviews send smaller requests and report oversized payloads directly instead of surfacing a generic connection error.

Security findings show their category, CWE, reachability, and exploitability in terminal output and --agent JSON when available.

coderabbit usage shows waived review spend and calculates the remaining review cap from review usage instead of unrelated product spend.

See the CLI documentation and CLI Command Reference for current usage and options.

Cross-repository targeted guidelines

Guidelines sourced from another repository in your organization previously applied globally to the reviewed repository. The { files, applyTo } object form now works for cross-repository sources too: write the guideline document reference in files using the repo:path form, and applyTo defines the source-file patterns that guidance governs in the repository being reviewed. A centralized standards repository can now declare, for example, that its Python style guide applies only to **/*.py in every consuming repository.

Cross-repository sources continue to pass the same organization-boundary and access checks as before, and string entries keep their existing global behavior with no migration needed. Object entries apply when set through configuration files, the web interface, or central configuration; pull request description overrides do not yet honor them for guideline selection, and Perforce configurations ignore repository-qualified entries. Like other cross-repository guideline features, this requires CodeRabbit Cloud.

See the Code Guidelines documentation for details.

Rate limit observability and control

Review capacity is consumed per developer over rolling windows, and most unexpected rate limiting comes from consumption a team did not intend: an incremental review on every push, reviews superseded before they produce feedback, and organizations whose pull requests all open under one bot or service identity. Two changes make that consumption measurable and adjustable.

Review Usage dashboard

Review Usage is a new dashboard under Analytics in the CodeRabbit web app, covering pull request reviews consumption over a rolling 7- or 30-day window.

It breaks consumption down per developer and across the organization, attributes every review event to the pull request that caused it, and flags consumption anti-patterns where it finds them. If your team hits rate limits regularly, start here — see Review Usage documentation for how to read each view.

Review rate limits

Review rate limits is a new page specifying what draws down the allowance, how the rolling allowance refills, Fair Usage Limits Policy, common anti-patterns and the controls that reduce consumption — batching commits into one push, using auto-pause configuration and pause command, label-based opt-in, title-based exclusions, and pull request attribution to the developer the work belongs to rather than a shared account.

Multi-Repo Analysis: automatic linking mode

Automatic repository linking for multi-repository analysis now uses knowledge_base.automatic_linking_mode configuration setting with three explicit modes:

• Auto lets private repositories link automatically to eligible public or private repositories, while public repositories link automatically only to eligible public repositories.
• Enabled lets reviews use context from any eligible public or private repository in the organization.
• Disabled creates no automatic repository links. (Default)

The legacy knowledge_base.automatic_repository_linking boolean is deprecated and has no effect. Manual repository links remain unchanged in every mode.

Automatic linking supports GitHub, GitHub Enterprise Server, Azure DevOps, and Bitbucket Data Center. It remains unavailable for GitLab and Bitbucket Cloud; manual repository links continue to work on those providers.

See Multi-Repo Analysis for configuration and behavior details.

Self-hosted CodeRabbit 20260822040711

Self-hosted administrators can now use {{ pr.url }} and {{ event.correlation_id }} in custom HTTP headers sent to MCP servers, linking tool requests to the triggering pull request and correlating customer gateway, MCP server, and CodeRabbit logs.

Self-hosted CodeRabbit logs once again preserve supported model-usage token-count fields for per-review cost calculations while continuing to redact credential-bearing token fields.

Bitbucket Data Center pull-request reviews can now apply coding guidelines from another repository after verifying that the review author has qualifying read access; the CodeRabbit bot needs REPO_ADMIN on the source repository to perform the check.