Install ProPR, or skip the server
Run npm install -g propr-cli and propr setup on a Linux Docker host (quickstart). ProPR Hosted runs a dedicated instance for you when you would rather not run one.
ProPR: the self-hosted alternative to Claude Code cloud sessions
Claude Code cloud sessions run on Anthropic-managed infrastructure, started from claude.ai/code or claude --cloud. ProPR runs Claude Code on your own server as one of five agents, with planning, review, and follow-up.
vs
Claude Code
Works well together
Claude Code implements. ProPR plans the task, opens the pull request, and turns GitHub comments into follow-ups, on your server.
Cloud session pathclaude.ai/code → Anthropic-managed VM → pull request → Auto-fixNeeds a Claude subscription account; no API key, Bedrock, Google Cloud, or Foundry.
ProPR pathPlan → isolated workspace → GitHub PR → follow-up commitThe same Claude, on your plan or API key, on your own server.
Switch from Cloud sessions to ProPR.
What you keep: your GitHub repositories and review process, and the Claude Pro, Max, Ultra, Team, or Enterprise plan, which ProPR runs through the same Claude Code CLI.
The same ideas, ProPR's names
| Cloud sessions | ProPR |
|---|---|
| Cloud session | Task |
| Plan permission mode | Plan, approved before code runs |
| Anthropic-managed VM | Isolated workspace on your server |
| Auto-fix on the PR | Any plain PR comment; /fix for review findings |
| Claude GitHub App | GitHub through ProPR Connect, or your own GitHub App |
| Claude subscription accounts only | Claude plan, API key, Bedrock, Google Cloud, or Foundry |
From zero to the first pull request
Add the same repository and sign in your agent
Open the web UI, sign in with GitHub, and add the repository. Sign in Claude Code with the same Claude plan.
Start the first task and approve the plan
Add the AI label to the issue, or describe the change in Planner Studio, then approve the plan.
Review the pull request in GitHub
Review the diff the way you review any pull request. A plain comment on it becomes the next commit on the same branch; /review posts scored findings and /fix applies them. The phone review playbook runs the loop from the GitHub mobile app.
What stays with Cloud sessions: Cloud sessions start from the Claude mobile app and run with no server; ProPR runs on a Linux Docker host or a Hosted plan, and you steer it from the mobile web UI or GitHub mobile.
Cloud sessions, also called Claude Code on the web, remove local setup from the first task. Each session starts from the browser at claude.ai/code, the Claude mobile app, the desktop app, or claude --cloud in the terminal, runs in an isolated Anthropic-managed VM, clones the repository through the Claude GitHub App, pushes a branch, and creates the pull request with a generated title and description. Auto-fix then watches that PR: when a check fails or a reviewer comments, Claude investigates and pushes a fix if one is clear, replying under your GitHub account with a Claude Code label. Cloud sessions need a Claude Pro, Max, Ultra, Team, or Enterprise account; they are unavailable on an API key or through Bedrock, Google Cloud, or Foundry.
ProPR runs Claude Code on your own server, on the same Claude plan or on an API key, with Anthropic billing you directly. You approve a plan, review the pull request in GitHub, and pick the agent per task.
After the PR opens, each plain GitHub comment becomes the next commit on the same branch, from Claude Code or any of the other four agents.
Claude Code cloud sessions fit best when...
- Anthropic-hosted sessions you can steer from a phone or browser are the main workspace.
- Auto-fix on a PR Claude opened covers your follow-up needs.
- Everyone works on a Claude subscription and nobody needs another agent in the loop.
ProPR fits best when...
- Claude Code is one option alongside Codex, Antigravity CLI, Mistral Vibe, OpenCode, or direct API-backed agents.
- Planning, PR creation, review follow-up, usage, and logs live in one self-hosted system.
- Plain GitHub comments drive fixes, reviews, and branch updates on any PR, from any of the five agents.
Anthropic-hosted sessions versus a PR layer that still runs Claude.
| Question | Claude Code cloud sessions | ProPR |
|---|---|---|
| Anthropic hosts the coding session | Yes, isolated Anthropic-managed VM | No, your server |
| Claude implements the change and opens the PR | Yes | Yes |
| Plan before implementation | Plan permission mode in the session | Reviewed plan on every task |
| GitHub comments become follow-up commits | Auto-fix on PRs Claude watches | Any plain comment, any PR |
| Runs on an API key, Bedrock, Google Cloud, or Foundry | No, Claude subscription accounts only | Yes |
| Switch to Codex, Antigravity CLI, Mistral Vibe, OpenCode, or API-backed agents | No | Yes |
| Task history lives in your deployment | No | Yes |
Verified November 2026: Use Claude Code in the cloud, cloud sessions quickstart, GitHub Actions docs, claude.com/pricing.