Installation guide
AI Code Reviews in CLI lets you run fast, high-quality AI-powered code reviews directly from your terminal. It works on macOS, Linux, and Windows, and installation typically takes a few minutes.
This guide walks you through installation steps.
Prerequisites
Bito API Key (aka Bito Access Key)
You'll need a Bito account and a Bito Access Key to authenticate AI Code Reviews in CLI. You can sign up for a Bito account at https://alpha.bito.ai, and create an access key from Settings -> Advanced Settings
Installation guide
Download and install the CLI
macOS and Linux:
Open a terminal and run the following command:
curl -fsSL https://bitoreview.bito.ai/install.sh | bashWindows:
Open PowerShell 7 and run the following command:
irm https://bitoreview.bito.ai/install.ps1 | iexWhat gets installed:
The installer will:
Download the CLI binary for your platform
Install it in a user-local directory:
macOS/Linux:
~/.bitoreview/bin/Windows:
%USERPROFILE%\.bitoreview\bin\
Add the binary to your PATH so the
bitoreviewcommand is available globallyInstall bito-wingman (the AI engine) if it is not already present
Create a
bralias for quick accessAutomatically configures the usage guidelines globally for Claude Code and Windsurf (if detected). For other supported IDEs (such as Cursor, VS Code, etc.), you need to add the guidelines manually at the project level. See the commands given below in Add guidelines section.
Add guidelines
The guidelines file is a set of instructions that tells your AI coding agent (Claude Code, Cursor, etc.) how to correctly run bitoreview command when you ask it to do a code review. It defines the expected workflow, such as always using --prompt-only for structured JSON output, waiting for the review to complete before responding, grouping issues by severity, and validating problems in the actual code before suggesting fixes. Without these guidelines, the AI coding agent may not know how to use Bito's AI Code Reviews in CLI.
Global configuration (auto-applied during install)
During setup, the installer automatically adds the usage guidelines globally for the following AI coding agents if they are detected on your system:
Claude Code
~/.claude/CLAUDE.md
Windsurf
~/.codeium/windsurf/memories/global_rules.md
Project-level configuration (manual, per-project)
For all other supported IDEs such as Cursor, VS Code (GitHub Copilot), Junie, and JetBrains AI Assistant, you need to add the guidelines manually inside each project directory where you want them to apply.
Navigate to your project root, then run the relevant command:
Cursor:
macOS / Linux:
cd /path/to/your/project curl -fsSL https://bitoreview.bito.ai/bito_cli_review_guidelines.md -o .cursorrulesWindows:
cd C:\path\to\your\project irm 'https://bitoreview.bito.ai/bito_cli_review_guidelines.md' | Out-File -FilePath .cursorrules
Windsurf:
macOS / Linux:
cd /path/to/your/project mkdir -p .windsurf/rules curl -fsSL https://bitoreview.bito.ai/bito_cli_review_guidelines.md -o .windsurf/rules/bitoai-review.mdWindows:
cd C:\path\to\your\project New-Item -ItemType Directory -Path .windsurf\rules -Force irm 'https://bitoreview.bito.ai/bito_cli_review_guidelines.md' | Out-File -FilePath .windsurf\rules\bitoai-review.md
VS Code (GitHub Copilot):
macOS / Linux:
cd /path/to/your/project mkdir -p .github curl -fsSL https://bitoreview.bito.ai/bito_cli_review_guidelines.md -o .github/copilot-instructions.mdWindows:
cd C:\path\to\your\project New-Item -ItemType Directory -Path .github -Force irm 'https://bitoreview.bito.ai/bito_cli_review_guidelines.md' | Out-File -FilePath .github\copilot-instructions.md
Junie:
macOS / Linux:
cd /path/to/your/project mkdir -p .junie curl -fsSL https://bitoreview.bito.ai/bito_cli_review_guidelines.md -o .junie/guidelines.mdWindows:
cd C:\path\to\your\project New-Item -ItemType Directory -Path .junie -Force irm 'https://bitoreview.bito.ai/bito_cli_review_guidelines.md' | Out-File -FilePath .junie\guidelines.md
JetBrains AI Assistant:
macOS / Linux:
cd /path/to/your/project mkdir -p .aiassistant/rules curl -fsSL https://bitoreview.bito.ai/bito_cli_review_guidelines.md -o .aiassistant/rules/bitoai-review.mdWindows:
cd C:\path\to\your\project New-Item -ItemType Directory -Path .aiassistant\rules -Force irm 'https://bitoreview.bito.ai/bito_cli_review_guidelines.md' | Out-File -FilePath .aiassistant\rules\bitoai-review.md
Reload your terminal environment
To make the CLI available immediately, restart your terminal or reload your shell configuration.
macOS / Linux:
Restart your terminal or run:
# Bash
source ~/.bashrc
# Zsh (macOS default)
source ~/.zshrcWindows:
Restart PowerShell 7 or
Run
refreshenvif Chocolatey is installed
Authentication setup
To run code reviews, the CLI requires a valid Bito API key (aka Bito Access Key).
Get Bito API key:
You can sign up for a Bito account at https://alpha.bito.ai, and create an access key from Settings -> Advanced Settings
Configure the Bito API key:
You can configure authentication in multiple ways.
Method 1: Interactive setup (recommended) - You'll be prompted to paste your Bito API key securely.
bitoreview config set-api-keyMethod 2: Direct CLI setup - Useful for automation or scripted setups.
bitoreview config set-api-key YOUR_API_KEY_HEREMethod 3: Environment variable - Useful for CI/CD pipelines, shared machines, temporary or project-specific credentials
export BITO_API_KEY=YOUR_API_KEY_HEREVerify your Bito API key:
To confirm your Bito API key is configured correctly, run:
bitoreview config show-api-keyBito API key resolution priority
If multiple API keys are configured, the CLI resolves them in the following order:
Command-line flag:
--api-key YOUR_KEYEnvironment variable:
BITO_API_KEYStored configuration file:
~/.bitowingman/env
This makes it easy to override credentials per command, project, or environment.
Next steps
You’re now ready to run AI-powered code reviews from your terminal.
How to use? – Run your first code review
Available commands – Complete reference of CLI commands
Troubleshooting – Common issues and how to resolve them
Last updated

