Skip to main content
The setup flow connects your Slack workspace to a Git provider, makes provider-authorized repositories available to CodeRabbit Agent, and creates a that defines which repositories, connections, and spend controls apply by default. Once the Base Scope is saved, anyone in the workspace can mention @coderabbit in a channel, or open the CodeRabbit app to start a direct conversation.

Prerequisites

Before you start, make sure you have:
  • Permission to install or reauthorize apps in the Slack workspace
  • Access to the Git organization, workspace, or account whose repositories CodeRabbit Agent should use
  • Permission to install or configure CodeRabbit for those repositories
  • A CodeRabbit organization admin who can configure Agent; billing-only admins cannot manage connections or scopes

Setup steps

1

Select your CodeRabbit organization

Sign in to CodeRabbit, select the organization whose repositories Agent should use, and open Slack. The setup flow uses that organization’s Git platform: GitHub, GitLab (cloud or self-managed), Bitbucket Cloud, or Azure DevOps.
2

Connect Slack

Choose Add to Slack to install the app and grant the required Slack permissions. If the workspace is already connected and you need to link your own account, choose Connect Slack. An existing installation resumes at its next incomplete setup step.
3

Complete provider setup

For GitHub, Bitbucket Cloud, and Azure DevOps, follow the setup prompts to authenticate with the provider, select the organization, workspace, or account, and make the approved repositories available to Agent.For GitLab, repositories are displayed without per-repository checkboxes. In organizations that do not use SSO, Agent uses repositories installed for CodeRabbit that the selected token can access. SSO workspaces use the token-visible group catalog. For a self-managed instance, follow Self-managed GitLab setup.
4

Configure the Base Scope

Choose the default repositories, connections, and spend baseline that should apply across the workspace. Installation can remain in pending setup while you configure the Base Scope, but CodeRabbit Agent cannot run until the Base Scope exists. All available connections are selected initially; deselect any that should not be available across the workspace before saving.
5

Start using CodeRabbit Agent

Once setup is complete, open CodeRabbit from Slack’s Apps sidebar or search for “CodeRabbit” in Slack — the Chat tab shows starter prompts to help you begin. You can also mention @coderabbit in any channel to start a conversation there. In the web app, Slack-specific administration now lives under Slack settings. You can refine scopes, connections, and sandbox settings at any time.

What the Base Scope does

The Base Scope sets the default repositories, connections, and spend controls that apply across the workspace. Scopes can override or refine these defaults for specific contexts. Setup can remain pending until the Base Scope is saved, but CodeRabbit Agent cannot run without it. See Slack and Discord scopes for the full model.

Resuming setup

The setup flow is resumable. If provider access is still propagating or a required step is incomplete, the Agent returns the workspace to the next missing requirement instead of forcing admins to start over.

Fixing an incorrect GitHub connection

If the wrong GitHub account or organization was connected, a global admin can reset the workspace GitHub connection from account settings and restart setup with the correct identity.
Resetting the workspace GitHub connection is destructive. It removes existing scopes and workspace usage history for that Slack workspace. Treat it as a recovery path, not a normal reconfiguration step.

What’s next

Working in Slack

Learn how mentions and direct conversations work day to day.

Connections

Add external systems like Jira, Notion, or Sentry for CodeRabbit Agent to use.

Scopes

Add scopes to tailor repositories, connections, and spend limits for specific channels or teams.