> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coderabbit.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Triage

> Prioritize your PR queue by value and risk, surface the changes that need attention, and route each pull request to the right reviewer.

export const OpenBetaBadge = ({tip = "This feature is currently in open beta. We are actively improving it based on your feedback. If you encounter any issues or have suggestions, please share them on our Discord community or visit the support page.", title = "Open Beta", cta = "Contact support", href = "/support", disabled = false}) => {
  return <Tooltip tip={tip} cta={cta} href={href}>
        <Badge icon="badge-alert" disabled={disabled || undefined}>
            {title}
        </Badge>
    </Tooltip>;
};

export const ProPlusPlanBadge = ({tip = "This feature is available as part of the Pro+ plan and Enterprise plan. Please refer to our pricing page for more information about our plans and features.", title = "Pro+ Plan", cta = "Read more", href = "https://coderabbit.ai/pricing", disabled = false}) => {
  return <Tooltip tip={tip} cta={cta} href={href}>
        <Badge icon="shield-plus" disabled={disabled || undefined}>
            {title}
        </Badge>
    </Tooltip>;
};

export const GitLabBadge = ({tip = "This feature is available on GitLab.", title = "GitLab", cta, href, disabled = false}) => {
  return <Tooltip tip={tip} cta={cta} href={href}>
        <Badge icon="gitlab" disabled={disabled || undefined}>
            {title}
        </Badge>
    </Tooltip>;
};

export const GitHubBadge = ({tip = "This feature is available on GitHub and GitHub Enterprise.", title = "GitHub", cta, href, disabled = false}) => {
  return <Tooltip tip={tip} cta={cta} href={href}>
        <Badge icon="github" disabled={disabled || undefined}>
            {title}
        </Badge>
    </Tooltip>;
};

<GitHubBadge title="GitHub Cloud" tip="Triage is available on GitHub Cloud." /> <GitLabBadge title="GitLab Cloud" tip="Triage is available on GitLab Cloud." /> | <ProPlusPlanBadge tip="Triage is available to organizations with Pro+ entitlement." /> <OpenBetaBadge tip="Triage is in beta." />

<Info>
  Triage is available in beta to organizations with Pro+ entitlement on GitHub Cloud and GitLab Cloud.
</Info>

## Overview

Triage is CodeRabbit's reviewer-first prioritization layer for agent-generated pull requests. It gives reviewers, maintainers, code owners, and team leads a self-updating, cross-repository queue that helps them decide which pull request to review next, how deeply to review it, and which pull requests may be safe to close.

Find Triage in the sidebar under **Review**, or go directly to [app.coderabbit.ai/triage](https://app.coderabbit.ai/triage).

## Why Triage

Agent-generated pull request volume grows faster than human review capacity. Git providers organize PRs by repository and mechanical state, but they do not combine CodeRabbit's analysis of value, review evidence, architecture, risk, reviewer expertise, and cross-pull-request relationships. Triage brings those signals into one queue so teams spend review time on work that needs human judgment.

## Access and permissions

Members of an eligible CodeRabbit organization can view Triage without an active review seat. An active organization seat is required for actions that call the Git provider or use model capacity, such as starting a CodeRabbit review, closing an eligible pull request, or changing requested reviewers. Repairing a pull request does not require a seat.

Triage follows the pull requests tracked for the organization, excluding archived repositories. On GitHub.com, it's also limited to repositories the signed-in GitHub account can access.

Triage refreshes provider state continuously, but a card can briefly lag GitHub or GitLab. Confirm the current provider state before closing or merging a pull request.

## Built-in views

Triage includes four views for common review responsibilities:

| View                | What it shows                                                                                                                         |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| **Needs my review** | Open pull requests where you are a requested reviewer, reviewer, approver, or change requester, excluding pull requests you authored. |
| **Authored by me**  | Open pull requests you authored. This is the default view.                                                                            |
| **All reviews**     | Open pull requests in non-archived repositories available to the organization or signed-in user.                                      |
| **Safe to close**   | Open pull requests that CodeRabbit recommends reviewing for closure.                                                                  |

**Safe to close is a recommendation. CodeRabbit does not automatically close these pull requests.** You decide whether to close, ignore, or restore each candidate and can report a false positive.

## Saved Views

Saved views preserve your current Triage board setup so you can reopen it later. Each saved view belongs to one user within one organization, with up to 50 saved views per user per organization.

Select **Save current view** to save the current Triage board setup as a saved view.

At the limit, **Save current view** is disabled and the interface shows "50-view limit reached. Delete a view to save another." Existing saved views remain available to apply, rename, update, and delete. Deleting a saved view frees capacity to save another.

## Layout, grouping, and ordering

Switch between **list** and **board** layouts without changing the underlying queue. Triage saves layout and display preferences so each view can stay optimized for its purpose. The **Review workflow** display preference applies in both layouts and persists in saved views.

Group the queue by review workflow, review guidance, risk, security risk, priority, repository, or author, or use no grouping. Order results by last activity, priority, created, pull request number, or title. The Safe to close view defaults to repository grouping and oldest activity first; the other built-in views prioritize higher-ranked work.

## Filters and search

Use filters to narrow the queue by:

* Repository, author, or reviewer
* Title
* Priority or review guidance
* Risk or security risk
* Review workflow or change type

In include mode, the queue shows only pull requests whose titles match the filter. In exclude mode, the queue hides pull requests whose titles match the filter.

Unlike the dedicated Title filter's include and exclude modes, free-text search performs a separate substring match across the fields described below.

Search matches pull request titles, `owner/repository` names, and pull request references such as `#123`.

## Card information

Every card shows the repository, pull request number, author, and title. Display settings and saved views control which additional fields appear, including the summary, last activity, change type, review guidance, risk, security risk, blast radius, review effort, issue severity, priority, diff size, reviewers, and **Review workflow**, which is visible by default.

The summary and priority fields show the card's selected explanation text; see [How card explanation text is selected](/triage/prioritization#how-card-explanation-text-is-selected).

**Review workflow** controls the **Needs human review** and **Needs author action** next-action tags on each card or row. Hiding **Review workflow** removes only these two tags; the separate explanation shown while CodeRabbit is waiting to review a pull request remains visible. Cards can also show the number of downstream pull requests blocked by the change and whether the pull request is a close candidate. Review-derived signals appear only while they cover the latest reviewable commit.

On each row, a color-coded review-decision label appears before the check-status indicator and summarizes the pull request's review state at a glance, without opening the pull request. The label is **Changes requested**, **Review required**, or **Approved**. Hover over **Changes requested** or **Approved** to see how many reviews requested changes or granted approval when participant data is available. **Review required** explains that review is needed before merging. Stale approvals show no label.

The check-status indicator summarizes the latest GitHub check set as loading, in progress, passed, failed, or neutral. A failure takes precedence over pending work. The indicator appears only for GitHub pull requests that report checks and is hidden when GitHub reports no checks. It reflects live check results rather than the older status stored on the card.

## Queue actions

Triage keeps common pull request actions next to the queue so you can move work forward without first finding it in the provider.

### Open a pull request

Opening a card takes you to [Change Stack](/pr-reviews/change-stack) when it is available for that pull request. Otherwise, Triage opens the pull request in GitHub or GitLab.

### Start a CodeRabbit review

Request a CodeRabbit review for an eligible pull request and follow its state from the card while the review runs. See [CodeRabbit's pull request review workflow](/guides/code-review-overview) for the full review lifecycle.

### Repair a pull request

Use repair actions to [resolve merge conflicts](/finishing-touches/resolve-merge-conflict) or [fix failing CI checks](/finishing-touches/fix-ci) where the provider supports the action.

### View checks

Open the check-status indicator to view a panel that lists each reported check's name, provider (the reporting GitHub App), status or outcome, duration when timestamps are available, provider-supplied summary, and link to the check's GitHub details page.

Opening the panel immediately refreshes the pull request's check results. While the panel remains open and at least one check is pending, it polls every five seconds; polling stops when all checks finish or the panel closes. The panel shows loading and provider-error states and offers a manual retry when live results cannot be loaded.

### Close safely

Use **Close PR** in the action menu of any open pull request card. Close-candidate cards also keep an inline close button. Closing is immediate and comment-free. Direct close runs as the signed-in user with that user's GitHub access. Closure always requires a user action; there is no automatic close.

### Follow a pull request in Slack

Use **Follow** on a tracked, open pull request card to select a Slack channel or direct-message group and receive pull request activity in a dedicated thread. The direct-message option preselects you, and the picker lists recently used, accessible channels before you search. For the shared destination, identity-linking, and event-preference mechanics, see [Slack discussion threads](/pr-reviews/change-stack#slack-discussion-threads) and [PR auto fix settings](/pr-reviews/change-stack#pr-auto-fix-settings).

Starting a follow thread requires:

* A tracked, open GitHub.com pull request
* Stored Change Stack review data for that pull request
* A connected and configured Slack workspace
* Your linked Slack identity
* CodeRabbit bot access to the selected channel

### Manage reviewers

Request or remove reviewers, or suggest another reviewer where the provider and your permissions support the operation. Triage reviewer suggestions consider review history, repository ownership, and contribution context; see [How prioritization works](/triage/prioritization#reviewer-suggestions).

### Provider limitations

* **GitHub:** Triage can resolve merge conflicts and fix failing CI checks where those repair actions are available. Direct close and **Follow** are supported on GitHub.com only. **Follow** targets tracked, open GitHub.com pull requests.
* **GitLab:** Triage can resolve merge conflicts where supported. Fixing CI, direct close, **Follow**, and requesting or removing reviewers from Triage are not currently available.
* **Reviewers:** Requesting and removing reviewers from Triage is currently available on GitHub only. Suggestions remain visible where generated; applying them still requires provider support and repository permissions.
* **Check status:** The live check indicator and details panel are currently available on GitHub only.
* **Diff size:** The diff size card property is currently available on GitHub only.
* **Self-hosted deployments:** Triage beta is not currently available for self-hosted GitHub or GitLab deployments.

## What's next

<CardGroup cols={1}>
  <Card title="How prioritization works" href="/triage/prioritization" icon="list-ordered" horizontal>
    Learn how Triage combines workflow, activity, risk, effort, and dependency context into priority and close recommendations.
  </Card>

  <Card title="Change Stack" href="/pr-reviews/change-stack" icon="layers-3" horizontal>
    Inspect a pull request as logical cohorts and layers after opening it from Triage.
  </Card>

  <Card title="PR Walkthroughs" href="/pr-reviews/walkthroughs" icon="list-tree" horizontal>
    Understand the CodeRabbit review signals that Triage can surface on pull request cards.
  </Card>
</CardGroup>