Skip to content
ReviewRouter
Getting started

Install the control plane. Keep review execution in your repo.

The current setup path is four steps: install the GitHub App, merge the generated setup PR, seed provider access into GitHub Actions secrets, then open a pull request.

Current setup route

Control plane hosted. Review runtime is yours.

ReviewRouter creates and monitors setup, but checkout, PR diff analysis, provider calls, prompts, and model output happen inside GitHub Actions.

ReviewRouter

Control plane, setup, policy

GitHub repo

Setup PR and caller workflows

GitHub Actions

Code checkout and review runtime

Model provider

Called from customer runtime

Setup PR manifest
.github/workflows/reviewrouter.yml
.github/workflows/reviewrouter-interaction.yml
.github/workflows/reviewrouter-codex.yml  # Codex OAuth rotating repos
branch: reviewrouter/setup
runtime: 777genius/review-router reusable workflows
Step 01

Install the GitHub App

Install ReviewRouter on selected repositories or request organization approval. The App syncs installation metadata, selected repos, setup PR state, and health signals.

Step 02

Create the setup PR

From the dashboard, create the setup PR. It uses the reviewrouter/setup branch and adds compact caller workflows, not a hosted code execution path.

Step 03

Merge on GitHub

Merge the PR so the default branch owns the workflow. Dashboard progress advances from setup PR open to provider setup after GitHub metadata catches up.

Step 04

Enable review

Seed provider access from your machine into GitHub Actions secrets. ReviewRouter records only setup confirmation and safe provider status metadata.

What the setup PR installs

The repo receives small caller workflows. The versioned runtime stays in the ReviewRouter repo.

Current workflow shape

FileTriggersJobBoundary
reviewrouter.ymlpull_request, merge_group, workflow_dispatchRuns the AI review gate through ReviewRouter reusable runtime.Top-level permissions are empty, job-level permissions are explicit.
reviewrouter-interaction.ymlreview comments, issue comments, workflow_dispatchHandles /rr style interactions and discussion routing.Uses GitHub OIDC for runtime config and passes only required secrets.

No pull_request_target

Default review avoids the dangerous hosted-secret pattern.

Fork protection

Secret-backed provider execution is skipped for fork PRs.

OIDC config

Runtime config is fetched through GitHub OIDC when available.

Provider access

Pick one auth mode first. You can adjust model, reasoning, fast mode, and provider config later in the dashboard.

OAuth refresh

Codex

Secret
REVIEWROUTER_CODEX_AUTH_JSON
Model
gpt-5.5 default

Copy the dashboard-generated command. It writes encrypted GitHub secret payloads directly to GitHub and refreshes in GitHub-hosted Actions.

OAuth

Claude Code

Secret
CLAUDE_CODE_OAUTH_TOKEN
Model
sonnet default

Run claude setup-token, then store only the printed token.

API key

OpenRouter

Secret
OPENROUTER_API_KEY
Model
Dynamic model catalog

Store the OpenRouter key in GitHub Actions secrets.

Credential commands

Run these from your own machine. Secret values go directly to GitHub Actions.

Recommended

Codex per repository

Use the dashboard-generated command for the selected repository. Generic Codex commands are intentionally disabled.

# Copy the full repo-scoped command from Dashboard -> Enable review -> Codex.
# It uses https://reviewrouter.site/install/codex, a short-lived setup nonce, and REVIEWROUTER_CODEX_AUTH_JSON.
curl -fsSL https://reviewrouter.site/install/codex | REVIEW_ROUTER_CODEX_ROTATING_SETUP_URL="..." REVIEW_ROUTER_CODEX_ROTATING_SETUP_NONCE="..." REVIEW_ROUTER_CODEX_ROTATING_PROVIDER_INSTANCE_ID="..." bash -s -- --confirm-write
Claude Code

Claude Code OAuth token

Store only the printed setup token. Do not paste local Claude config files.

claude setup-token
gh secret set CLAUDE_CODE_OAUTH_TOKEN --repo owner/repo --app actions
API keys

OpenRouter API key mode

Use normal provider billing when you do not want subscription OAuth.

gh secret set OPENROUTER_API_KEY --repo owner/repo --app actions

Operational boundary

Use this as the mental model before enabling review on sensitive repositories.

Source code and PR diffs

GitHub Actions runner. ReviewRouter cloud skips code by default.

Provider credentials

GitHub Actions secrets. Seeded from your machine with gh.

Runtime config

GitHub OIDC plus static fallback. The workflow asks for metadata, not secret values.

Fork pull requests

Secret-backed review skipped. Default workflow avoids exposing provider secrets to forks.

Ready means workflow current plus provider confirmed.

If a setup PR was closed or its branch was deleted, recreate it from the dashboard and merge the new PR before reseeding secrets.