# CodeRabbit

> AI code review on every pull request

Source: https://aistack.sh/tool/coderabbit
Category: Coding agents
Site: https://coderabbit.link/aistacksh
Status: active
Last verified by a human: 2026-09-05

GitHub-native AI reviewer that reads diffs, leaves line-by-line comments, and suggests fixes. Catches bugs, security issues, and style drift before a human looks at the PR.

## Pricing

As published on the tool page: Free for OSS · $30/mo per dev Essentials ($24 billed annually) · $60/mo Team · $90/mo Advanced

Read from https://www.coderabbit.ai/pricing on 2026-09-09:

- Essentials: $24 per year
- Team: $48 per year
- Advanced: $72 per year
- Enterprise: custom / contact per year
- Essentials Annual: $288 per year
- Team Annual: $576 per year

## Alternatives

- Claude — https://aistack.sh/tool/claude

## Head-to-head comparisons

- [Claude Code vs CodeRabbit](https://aistack.sh/compare/claude-code-vs-coderabbit) (markdown: https://aistack.sh/compare/claude-code-vs-coderabbit/llms.txt)
- [Claude vs CodeRabbit](https://aistack.sh/compare/claude-vs-coderabbit) (markdown: https://aistack.sh/compare/claude-vs-coderabbit/llms.txt)
- [CodeRabbit vs Codex](https://aistack.sh/compare/coderabbit-vs-codex) (markdown: https://aistack.sh/compare/coderabbit-vs-codex/llms.txt)
- [CodeRabbit vs GitHub Copilot](https://aistack.sh/compare/coderabbit-vs-github-copilot) (markdown: https://aistack.sh/compare/coderabbit-vs-github-copilot/llms.txt)

## Used in 5 tested stacks

- [Claude Code MCP setup](https://aistack.sh/stack/claude-code-mcp-setup) — Review, $50/mo
- [Claude Code setup](https://aistack.sh/stack/claude-code-setup) — Review, $50/mo
- [Cursor rules](https://aistack.sh/stack/cursor-rules) — Review, $50/mo
- [Claude Code only](https://aistack.sh/stack/ship-code-claude-code) — Automated PR review, $50/mo
- [Ship code with AI](https://aistack.sh/stack/ship-code-with-ai) — Automated PR review, $50/mo

## Recent changes

- **Unified connection management with scopes across CodeRabbit products** (2026-09-10, feature) — Configure external service connectors once, then use scopes to control access across Review, Slack, and Discord. Base and named scopes let security-sensitive repositories or channels be excluded from shared connections, reducing duplicate setup across products. Source: https://docs.coderabbit.ai/changelog
- **Custom Jira issue template configuration for CodeRabbit** (2026-09-10, feature) — Teams can now configure chat.integrations.jira.issue_template to define custom Jira issue structures, ensuring CodeRabbit-created issues follow team standards instead of using default formatting. Source: https://docs.coderabbit.ai/changelog
- **CodeRabbit unified external service configuration with scopes for access control across products** (2026-09-10, feature) — Service configuration is now centralized with a single setup per connector, with scopes controlling usage across repositories and chat platforms. Base scopes define defaults while named scopes can override or exclude access for specific repositories or teams, allowing security-sensitive areas to restrict connector access. Source: https://docs.coderabbit.ai/changelog
- **CodeRabbit supports custom Jira issue templates for team-specific standards** (2026-09-10, feature) — Developers can configure custom Jira issue description structures through the chat.integrations.jira.issue_template setting instead of using CodeRabbit defaults. This ensures created issues match team formatting and field requirements. Source: https://docs.coderabbit.ai/changelog
- **CodeRabbit unifies connector configuration with connections and scopes** (2026-09-10, feature) — Developers can now configure connectors once instead of separately for pull request reviews, Slack, and Discord. Named scopes control which products can use each connector in specific repositories or channels, eliminating duplicate setup and improving security control for sensitive repositories. Source: https://docs.coderabbit.ai/changelog
- **Review comment metrics API provides finding-level insights for enterprise organizations** (2026-09-09, feature) — Enterprise organizations can now retrieve finding-level metadata for CodeRabbit review comments on merged pull requests through GET /v1/metrics/review-comments, including severity, category, resolution outcome, and comment URL. This enables programmatic analysis of code review findings without accessing comment text. Source: https://docs.coderabbit.ai/changelog
- **Review comment metrics API for enterprise organizations** (2026-09-09, feature) — Enterprise orgs can retrieve finding-level metadata (severity, category, resolution outcome, comment URL) for CodeRabbit review comments via GET /v1/metrics/review-comments without exposing comment text, enabling analytics and auditing. Source: https://docs.coderabbit.ai/changelog
- **Project vocabulary command generates repository-specific terminology** (2026-09-09, feature) — Comment @coderabbitai generate project vocabulary to receive an alphabetized list of up to 50 project-specific terms extracted from source code and documentation, automatically excluding generic frameworks and dependencies. Source: https://docs.coderabbit.ai/changelog
- **CodeRabbit adds review comment metrics API for enterprise finding-level analysis** (2026-09-09, feature) — Enterprise organizations can retrieve metadata for CodeRabbit findings on merged PRs via GET /v1/metrics/review-comments, including severity, category, resolution outcomes, and comment URLs. This enables programmatic tracking and analysis of code review findings. Source: https://docs.coderabbit.ai/changelog
- **CodeRabbit CLI v0.7.6 improves large-review handling and security output** (2026-09-04, release) — Large reviews now send smaller requests and report oversized payloads directly instead of generic errors. Security findings display category, CWE, reachability, and exploitability information. Usage reporting more accurately reflects actual review spending. Source: https://docs.coderabbit.ai/changelog

---

From aistack.sh. Last updated 2026-09-04.