The suggested_reviewers_instructions config option now works on GitLab. CodeRabbit resolves configured usernames to GitLab user IDs and assigns them as merge request reviewers.
Team or group reviewer handles are not supported on GitLab — they're ignored if included in the instructions.
See Suggested reviewers for usage details.
CodeRabbit now shows remaining PR review quota in review walkthroughs, including when the bucket refills. You can also comment @coderabbitai rate limit or ask a clear question like @coderabbitai reviews remaining? to get the same status without starting a new review.
CodeRabbit Agent is an AI agent for your entire SDLC right in Slack. Your team can investigate issues, generate implementation plans, and open pull requests — all from the channel or thread where the conversation is already happening.
Investigate — Ask questions about your codebase, trace features, and cross-reference Sentry errors with merged PRs and Jira issues.
Plan — Turn any Slack thread into a structured ready for any coding agent.
Act — Discuss requirements with your team, reference Linear issues or Figma designs, then ask CodeRabbit to open a pull request incorporating everything.
Every response runs within a , so the agent only sees the repositories and connections your admins have approved for a specific channel. A persistent retains what your team discovers so every conversation starts smarter.
Integrate with Jira, Linear, Notion, Sentry, Datadog, PagerDuty, Figma, Google Drive, and any MCP servers. Schedule recurring tasks — vulnerability checks, weekly summaries, periodic audits — that post results into Slack threads automatically.
See the CodeRabbit Agent documentation to get started.
CodeRabbit CLI 0.4.4 includes stability fixes for review event handling, and fixes an edge-case coderabbit auth login crash on macOS.
See the CLI documentation and CLI Command Reference for more details.
Autofix now supports GitLab. Use @coderabbitai autofix to commit fixes to the current branch, or @coderabbitai autofix stacked pr to open a separate merge request with the changes.
See the Autofix documentation for complete details.
Metrics dashboards now support selecting multiple repositories in the Repository filter. Use it to view combined metrics for several repositories in one dashboard view instead of switching filters one repo at a time.
See Dashboard overview for the updated filter description.
When your team has subject-matter experts for different areas of the codebase, you can now tell CodeRabbit exactly who to suggest for each scenario. Use suggested_reviewers_instructions in your .coderabbit.yaml to map groups of reviewers — individual users or teams — to the PR conditions where they should be assigned. When the list is empty, CodeRabbit falls back to suggestions based on prior PRs.
See Suggested reviewers for usage details.
Organization admins can now define Global overrides that enforce configuration settings across every repository and pull request in the organization. Global overrides sit at the top of the configuration priority hierarchy, superseding repository-level .coderabbit.yaml files, central configuration, and all other sources.
Set global overrides from Organization settings in the CodeRabbit web app. When an override overlaps with an existing setting, nested objects are merged together, while arrays and simple values are replaced entirely.
CodeRabbit has been available in Codex through CodeRabbit CLI, and is now also available as a dedicated Codex plugin. The plugin is more convenient to set up and use, and adds support for invoking CodeRabbit directly with @coderabbit mentions. After installing the plugin from the Codex marketplace and authenticating the CodeRabbit CLI, trigger a review with plain language or an explicit mention: Review my current changes with @CodeRabbit
The plugin verifies your CLI installation and authentication, runs the review, summarizes the diff, and reports findings with severity, file path, impact, and fix direction. Codex can then apply fixes automatically, creating a continuous build-and-fix loop without leaving your development environment.
See Codex integration for installation steps and usage examples.
Teams that reach their plan's PR review limit no longer need to wait for a billing cycle reset or upgrade their plan. Enabling the Usage-based add-on lets CodeRabbit continue reviewing pull requests past the limit, charging credits only for over-limit reviews. Regular usage stays on your plan, only the overflow is charged.
CLI-triggered reviews follow the same billing path and opt-in logic as PR reviews: one toggle, one credit balance, one billing path.
Admins enable the add-on using the pay-as-you-go toggle in Organization Settings in the CodeRabbit dashboard. See Usage-based Add-on for setup details.
CodeRabbit CLI 0.4.1 adds coderabbit stats, replaces --cwd with --dir for subdirectory-scoped reviews, and includes fixes affecting self-hosted auth and cleanup on --help.
See the CLI documentation and CLI Command Reference for more details.
CodeRabbit now supports SSH cloning for self-managed GitLab instances. If your organization requires SSH instead of HTTPS for repository access, you can configure your SSH credentials directly in the CodeRabbit web app under Account → Developer settings → SSH Clone Credentials. See the SSH Clone Credentials documentation for setup instructions.
The CLI now supports --agent mode, which outputs review results in structured JSON format for Skills and other agent integrations to consume directly.
See the CLI documentation for more details.
coderabbit auth login now completes entirely in the browser, no more copying and pasting tokens back into your terminal.
The --agent flag, introduced in version 0.3.11, now supports authentication workflows, improving compatibility with Codex, Cursor, Claude Code, OpenCode, and other coding agents.
See the CLI documentation and CLI reference for details.
CodeRabbit now supports webhook-secret management for both GitLab.com and self-managed GitLab from the Webhook Secret settings page. You can copy the exact webhook URL from the UI for manual setup, and when you rotate an existing secret, CodeRabbit attempts to refresh existing CodeRabbit-managed project and group webhooks automatically.
If a webhook was created manually, or if an automatic refresh fails, update that webhook's secret directly in GitLab.
See the GitLab and self-managed GitLab setup guides for details.
Suggested Reviewer Rules When your team has subject-matter experts for different areas of the codebase, you can now tell CodeRabbit exactly…
Autofix on GitLab | Autofix now supports GitLab. Use to commit fixes to the current branch, or to open a separate merge request with the ch…