CodeRabbit Agent for Slack now supports Google Ads as a first-class workspace connection.
Workspace admins can add a Google Ads connection from the Connections page, authenticate it with OAuth, and assign it to the Base Scope or any matching scope like other non-MCP service connections.
Google Ads connections support the account fields used during setup:
Customer ID for the target Google Ads account
Login Customer ID when the connection should use a manager account
See Connections for setup details and Scopes for how to make the connection available in Slack conversations.
CodeRabbit Agent for Slack now makes admin surfaces clearer for workspace and scope admins:
The Connections list shows linked scopes for each connection and supports searching by scope name.
Connection categories are consistent across the connection catalog and the Agent's run context.
The Usage table shows run times in the viewer's browser timezone, with UTC as a fallback.
See Connections and Usage for the updated behavior.
CodeRabbit Agent automations can now start not only on a recurring schedule or a new channel message, but also from an external webhook event. After saving a webhook trigger, CodeRabbit provides the webhook URL, required header, and a sample payload to configure in the source service.
Natively supported providers: Datadog, PagerDuty, and Pylon. Any other service can connect via a custom webhook.
Webhook triggers can match by provider event type, by JSON payload fields, or both. If no matching rule passes, the event is dropped.
Additionally, the Automations page in the web app is now available to all workspace users. Workspace admins can see every automation and trigger in the workspace; other users can see the automations and triggers they created.
See the Automations documentation for full details.
|
Change Stack is a new code review interface that reorganizes a pull request from a flat file list into a guided, layer-by-layer walkthrough, so reviewers can follow the change in the logical, explorable order, not in alphabetical file order.
AI-authored PRs tend to be larger and touch more files than handwritten ones: main changes, new migrations, consumers, call sites, and tests all in one diff. GitHub surfaces these as a flat file list, leaving reviewers to reconstruct the meaning themselves before they can evaluate anything. Change Stack is designed to assist with the review of larger, harder-to-read AI-written changes.
Change Stack organizes a PR into ordered cohorts and layers anchored to specific line ranges, each with its own range-specific summary. Diagrams are generated inline where they add value: sequence diagrams for new call flows, ERDs for data model changes.
Open it from the Review Change Stack → button in the CodeRabbit PR comment. Comments and approvals post back to GitHub natively. Change Stack is available to all users during launch and will be part of the Pro+ plan.
See the Change Stack documentation for details.
Review pull requests layer by layer with Change Stack — a new way to break down complex changes generated by coding agents into manageable chunks.
This feature is currently available on all plans during preview. It will be part of Pro Plus, and we'll be actively improving it over the coming days.
CodeRabbit CLI 0.4.5 improves reliability on large repositories, adds clearer guidance when a review payload is too large, and fixes Free-plan CLI review limits to use the expected 3 reviews per hour bucket.
This release also includes bug fixes for review event handling, macOS coderabbit auth login, plain-mode severity labels, and the non-functional --files option. Use --dir to scope reviews instead.
See the CLI documentation and CLI Command Reference for more details.
CodeRabbit Agent automations can now run on each new top-level message in their home channel, not just on a recurring schedule. Use message-triggered automations when you want CodeRabbit to react to messages in Slack, such as Datadog alerts, deployment notices, or queue-health posts. You can:
Match every new top-level message in the channel
Restrict runs to messages whose text includes specific case-insensitive substrings
Restrict runs to specific Slack bots or Slack apps with a required author allowlist
Message-triggered automations always reply in the triggering thread. Run now is not available for this trigger type; post a matching bot or app message in the channel to test it.
|
The CodeRabbit Reverse Tunnel lets Enterprise teams connect CodeRabbit to a private-network GitHub Enterprise Server without opening inbound access. A customer-hosted Reverse Tunnel Connector dials out to the CodeRabbit-managed Reverse Tunnel Gateway over WSS, and CodeRabbit routes GHES API and HTTPS Git traffic through that existing outbound session.
See the CodeRabbit Reverse Tunnel guide for architecture, network requirements, and onboarding details.
Pull request reviews now run Microsoft Presidio Analyzer to detect possible PII leaks. Supported entity types include credit card, crypto wallet addresses, email, IBAN, phone number, US bank number, US ITIN, and US SSN. Configure reviews.tools.presidio for entities and score threshold.
See the Presidio Analyzer documentation for configuration details.
CodeRabbit now offers Pro Plus as a distinct plan between Pro and Enterprise. Pro covers core AI Code Review workflows, while Pro+ adds higher-tier actions that happen before and after review, such as CodeRabbit Plan, unit test generation, Resolve Merge Conflicts, and Simplify code.
Pro+ also raises the rate limits for PR reviews, increases limits for MCP server connections and Multi-Repo Analysis. See Plans and pricing for the full comparison and upgrade details.
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.