20 releases · 1 product · 2 Preview · 2 Beta
Triage for GitLab | is now available in beta for GitLab Cloud and self-managed GitLab organizations on the Team plan and higher. The Triage documentation covers access requirements, prioritization, views, and supported actions.
CLI v0.8.0 Deep review: Added cr review --deep . Included-review availability: Run cr usage to see available included reviews, the rolling window, and when capacity returns. Add --agent for structured output.
CLI v0.8.1 Continue local work in the cloud: Use cr code handoff --summary to start a new cloud Coding Agent task with your session summary, an optional plan, and an automatically discovered transcript when available. Clearer handoff results: See transfer progress, the branch and commit, transferred filenames, and a direct link to the cloud task.
Share TypeScript configuration from another repository Programmatic .coderabbit.config.ts files can now load shared fragments from an authorized repository selected with includeRemote({ repo, path, ref? }) . Omit repo to keep using your organization's central coderabbit repository.
CodeRabbit Triage | CodeRabbit Triage is a single queue of every open pull request your organization is tracking, across repositories, ordered by what each one needs next and what acting on it is worth. It is built for reviewers, code owners, maintainers, and team leads who have more pull requests in front of them than review hours.
Dynamic CodeRabbit configuration with TypeScript Define CodeRabbit settings in a programmatic .coderabbit.config.ts , with PR-aware conditions, reusable merged fragments, local TypeScript/YAML includes, and shared includes from the organization’s coderabbit config repository!
CLI v0.7.7 Review without a local clone: Use cr review --remote owner/repo --base main --source-branch feature to review an installed GitHub repository from any directory. See remote reviews for requirements and limits. Configure reviews from the CLI: Run cr config to create or update repository settings with a preview before saving.
Requested team overrides When Pre-Merge Check override access is restricted with reviews.pre_merge_checks.override_requested_reviewers_only: true , members of a requested GitHub reviewer team can now ignore failing checks. Individually requested reviewers remain eligible, and the pull request author remains excluded. See Pre-Merge Checks for details.
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.
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.
Attack surface map | The attack surface map is a living view of the security-relevant parts of that repository: CodeRabbit groups mapped code locations into subsystems, sorts each one into a lane , entry points, trust boundaries, access controls, sinks, or security configuration , and overlays open findings.
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...
Releasesby Glyph