> ## 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.

# Change Stack

> Change Stack is CodeRabbit's review workspace: it turns a pull request into a structured, navigable artifact you can read, question, and act on in one place.

GitHub (This feature is available on GitHub and GitHub Enterprise.) GitLab (This feature is available on GitLab.) Bitbucket (Change Stack is available on Bitbucket with authenticated access.) Azure (Azure DevOps Change Stack artifacts are read-only.) | Preview (Change Stack is in preview and still changing.)

A pull request arrives as a flat list of files in alphabetical order, and nothing about that order reflects how the change was built or how it should be read. You have to work out for yourself which files belong together, where to start, and which parts depend on others.

Change Stack is CodeRabbit's review workspace. It takes the same pull request and presents it as a structured artifact: grouped into coherent areas, ordered so foundations come before the code that depends on them, with every finding, summary, and graph anchored to the exact lines it is about.

You read the change, ask questions about it, and comment, approve, or merge without leaving the page, depending on what your [Git provider supports](https://docs.coderabbit.ai/change-stack/provider-support.md). You can also carry a review into a Slack or Discord thread, which [Collaborate in Slack and Discord](https://docs.coderabbit.ai/change-stack/notifications.md) covers.

![Change Stack Overview for web-app pull request #482, 10 files on feat/teammate-invitations, with Approve and Submit review buttons in the top bar. The left rail lists the Overview, Security blast radius, Security architecture impact, and three layers. Tiles show 3 layers, 10 files with 354 additions and 3 deletions, and 2 findings, 1 Critical and 1 Major. The summary of what changed in each layer ends with chips for 2 Critical, which include the merge conflict, and 1 Major. Below it are 2 items to act on, 1 blocking merge: the branch conflicts with its base, with Ask CodeRabbit to resolve and View on GitHub buttons, and a critical CodeRabbit finding on lines 15 to 16 of src/server/invitations/invitationService.ts, with a View comment button.](https://mintcdn.com/coderabbit/CVBNRUKgKs42eM6g/assets/images/change-stack-overview.png?fit=max\&auto=format\&n=CVBNRUKgKs42eM6g\&q=85\&s=0c1cc23dad5c792e1055ae24aedc977e)

A pull request's Overview in Change Stack, in an example repository: its layers in the rail, a summary of what changed, and what blocks the merge. The Summary's chips also count the merge conflict, rated Critical.

## Review a pull request

Every CodeRabbit review comment carries a **Review Change Stack →** button above the [walkthrough](https://docs.coderabbit.ai/pr-reviews/walkthroughs.md). You can also open Change Stack from Triage (A single cross-repository queue of open pull requests, ranked by what each one needs next and what acting on it is worth.) or from a link a teammate shares.

![CodeRabbit review comment showing the Review Change Stack button alongside Walkthrough and Pre-merge checks sections](https://mintcdn.com/coderabbit/vxxyCiPZPM0A23bY/assets/images/change-stack-button.png?fit=max\&auto=format\&n=vxxyCiPZPM0A23bY\&q=85\&s=5d925733d579ac75b11bf88aa83032dd)

The "Review Change Stack →" button in a CodeRabbit review comment

**1. Open the overview**

Start with **Overview** to see the change summary, merge readiness, and items that need your attention.

**2. Choose how to move through the change**

Use the layer rail for the intended reading order or switch to the file view when you already know where to look. See [Navigate a change](https://docs.coderabbit.ai/change-stack/navigation.md).

**3. Read the changes and findings**

Inspect the relevant diffs, then use **Needs your attention** and the finding filters to decide what matters. See [Read changes](https://docs.coderabbit.ai/change-stack/reading-diffs.md) and [Understand findings](https://docs.coderabbit.ai/change-stack/findings.md).

**4. Ask for context when you need it**

Open chat from a layer, file, or range to ask about the code in front of you. See [Ask about the change](https://docs.coderabbit.ai/change-stack/chat.md).

**5. Finish the review**

Comment, submit your review, apply an eligible suggestion, or merge when your provider supports the action. See [Review and merge](https://docs.coderabbit.ai/change-stack/reviewing.md) and [Provider support](https://docs.coderabbit.ai/change-stack/provider-support.md).

Using Change Stack is voluntary. A teammate who prefers their provider's own review interface can ignore the button and keep reviewing there.

## How a change is structured

Change Stack builds the pull request into a **stack** of numbered **layers**. A layer is a checkpoint in the change: a coherent step, with the files and review context that belong to it. Inside a layer are the changed **files**, and inside those are **ranges**: spans of source lines that carry a summary, a finding, or a review anchor.

The range is the level that makes the rest work. Because summaries and findings attach to source spans rather than to whole files, Change Stack can put a summary beside the lines it describes, jump from a finding on a dependency graph to the code that produced it, and tell you whether that finding is still open three pushes later.

![Change Stack showing layer 2, Add the invitation API and emails, with the diff of invitationService.ts. A CodeRabbit comment on lines 15 to 16 sits right under the line that builds the invite token with Math.random and says that tokens generated this way are not cryptographically secure.](https://mintcdn.com/coderabbit/CVBNRUKgKs42eM6g/assets/images/change-stack-layer.png?fit=max\&auto=format\&n=CVBNRUKgKs42eM6g\&q=85\&s=a3c5f0cfef8d200cd9135e391046d3a6)

One layer of the same example pull request, with a critical finding anchored to the lines it describes

### How the layers are chosen

CodeRabbit reads the change and groups it, rather than splitting it by file or folder. A layer is meant to be a step a developer would recognize, so a contract and the code that implements it and the tests that cover it belong in one layer, not three. The layers are numbered in the order someone would explain the change, which is roughly the order it was built rather than commit order or diff order. Where one layer genuinely depends on another, that relationship is recorded rather than inferred from the numbering.

Two consequences are worth knowing. File and directory boundaries are treated as evidence, not as rules, so a layer can span directories and a single directory can split across layers. And because the grouping is produced by a model as part of the review, it is fixed for a given snapshot but can legitimately come out differently when a later review run regenerates it. CodeRabbit is asked to keep titles and ordering that still hold, but that is not guaranteed.

> [!NOTE]
>
> Change Stack shows CodeRabbit's review scope, not necessarily every file on the pull request. Files excluded by default ignore rules or by configured [path filters](https://docs.coderabbit.ai/pr-reviews/which-files.md) do not appear in layers or file counts.

## What you read is a snapshot; what you act on is live

This is the one idea worth carrying into every other page.

Change Stack displays a **snapshot**, which is one completed review run against one head commit, and keeps earlier snapshots rather than replacing them. Everything you read comes from the snapshot you have open. Everything you *do*, such as submitting a review, applying a suggestion, or merging, targets the **live** pull request as it exists right now.

Those two things diverge the moment someone pushes. That gap is not an implementation detail leaking through; it is the reason the merge control refuses a stale artifact, the reason a chat thread keeps answering about the change as it stood when you opened it, and the reason a link you paste into a review thread may show your colleague a different snapshot next week. [Snapshots and freshness](https://docs.coderabbit.ai/change-stack/snapshots.md) covers it in full, including which capabilities are pinned and which are live.

## Availability

Change Stack is on by default. There is no plan to upgrade to and no flag to switch on. If CodeRabbit reviews your pull requests, the artifact is generated and the button is there. Being enabled is not a promise that every artifact is complete: a generation step can fail or still be running, and Change Stack says so rather than presenting a thin result as a finished one. It is supported on GitHub, GitLab, Bitbucket, and Azure DevOps, and self-hosted GitHub, GitLab, and Azure DevOps instances count as their cloud counterparts. A small number of Azure DevOps organizations are excluded from it; if the button never appears for your organization on Azure DevOps, that is the reason.

The interface labels Change Stack a **preview**. It is on for everyone, and it is still changing.

Two capabilities inside Change Stack carry their own gates rather than following the feature: **chat** is offered when your organization's [plan](https://docs.coderabbit.ai/management/plans.md) enables it, and **Coding Agent (Turns a user request, a review finding, a coding plan or a failing CI check into a task that CodeRabbit's agent implements in the cloud, then delivers as a commit or a stacked pull request for you to approve.) tasks** are offered when your plan, your repository write access, and the provider connection all allow it. You can have one without the other.

> [!WARNING]
>
> Azure DevOps Change Stack artifacts are **read-only**. You can read the change, the findings, and the graphs, but no live action is offered there: commenting, submitting a review, applying a suggestion, or merging. See [provider support](https://docs.coderabbit.ai/change-stack/provider-support.md) for the full matrix.

## What's next

> [card] [PR Walkthroughs](https://docs.coderabbit.ai/pr-reviews/walkthroughs.md)
>
> See how the walkthrough comment structures every review and feeds the layer summaries in Change Stack.

> [card] [Collaborate in Slack and Discord](https://docs.coderabbit.ai/change-stack/notifications.md)
>
> Carry a review into a chat destination and keep it fed with pull request events.

> [card] [Triage](https://docs.coderabbit.ai/triage.md)
>
> Prioritize your pull request queue and open the changes that need attention directly in Change Stack.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.