CodeRabbit Installation and Authentication

Overview

Route setup through the provider-specific flow and separate web-app installation from CLI auth. Never solicit or print credentials.

Prerequisites

• Identify the CodeRabbit organization, Git provider, repository, plan, and accountable owner.
• Read references/official-docs.md and re-check any time-sensitive contract before execution.
• Use synthetic or read-only evidence until the approval boundary is satisfied.
• Preserve the repository's independent CI, security, and human-review requirements.

Current Contract

• GitHub, GitLab, Azure DevOps, and Bitbucket use different authorization contracts.
• Organization access may require admin approval and explicit repo scope.
• Interactive and headless Agentic-key CLI auth are separate.
• Headless keys belong in a secret store, not repository config.