Source repository
The full ProPR codebase under Apache 2.0. Read it, self-host it, adapt it, contribute back.
ProPR's Apache 2.0 code and published Docker images run on your infrastructure. Your repositories, credentials, CLI, agents, logs, and task history live in the stack you run. The quickstart gets it going with two commands.
The whole software factory runs inside it: every agent loop, from a review and fix loop to a scheduled automation, runs in isolation on this host and returns its work as pull requests. The prebuilt stack runs on Linux amd64 with Docker and keeps its state locally. Guided propr setup connects GitHub through ProPR Connect; advanced deployments bring their own GitHub App. Agent Tank adds optional capacity tracking. System requirements.
The CLI needs Node.js 22+. propr setup runs host checks, agent sign-in, GitHub, and startup in one pass; the individual commands run each step on its own. Without Node.js, the propr/launcher image does the same job.
npm install -g propr-cli
propr setup
propr init stack
propr check
propr startThe propr CLI checks the agent credentials on your host, scaffolds the stack root, and starts the published images on your Docker daemon. Every generated file sits in the stack directory, ready to inspect, diff, or edit. The documentation covers every path and port.
The full ProPR codebase under Apache 2.0. Read it, self-host it, adapt it, contribute back.
Docker Hub carries the app, web UI, docs, launcher, and one unified agent image with every supported agent: Claude Code, Codex, Antigravity, OpenCode, and Mistral Vibe. The launcher pulls and runs the stack with one command.
Issues and PR events arrive over the hosted WebSocket relay by default, so you need no inbound endpoint; webhooks and polling work too. The documentation covers credentials, directories, updates, and a hardened production install.
ProPR handles plans, prompts, repositories, task logs, provider credentials, and GitHub actions, so where it runs matters. Trust and security lists what stays in your deployment and what GitHub and each model provider receive. The guide to running AI coding agents on your own server adds the host it takes.
Repository clones, task files, indexing state, logs, and worker state live in the ProPR stack you run.
Choose Claude Code, Codex, Antigravity CLI, OpenCode, or Mistral Vibe, on subscriptions or direct APIs, per repository and per task. Cap how many runs each agent may hold at once: a job whose agent is full waits in the queue, oldest first, without occupying a worker.
Branches, PRs, comments, checks, and merges happen in GitHub.
The optional direct MCP route serves https://<instance>/api/mcp with your instance's own OAuth and bypasses Connect. Agents and execution run on your instance; results you request reach your chat host. The hosted route through Connect's Plus managed tunnel reaches the same endpoint. MCP setup guide.