GitHub orchestration for coding agents.

ProPR is the PR-centered process around coding agents. You start with a plan, run the task in an isolated workspace, get a pull request, and keep refinements inside GitHub. Claude Code, Codex, and other coding agents remain the implementation layer. ProPR gives them a shared engineering process.

Because that is where teams already review code. The diff, comments, checks, approvals, and merge decision stay in the place engineers trust. Agent output stops living in terminal scrollback or chat history and starts living in the same pull request loop as human-written code.

A terminal session asks you to approve commands and edits as it goes. ProPR delegates that control to the isolated workspace and moves your approval to the pull request. Scope the task well and it works like delegating to another engineer — label the issue, walk away, review the PR. Follow-up is lighter too: screenshots paste straight into GitHub comments, ready for the next follow-up.

ProPR supports GitHub. The loop uses GitHub's pull requests, review comments, status checks, and comment controls to drive follow-up work. GitLab and Bitbucket fall outside the current product boundary.

Each task runs away from the main checkout in its own Git worktree, branch, and Docker workspace. ProPR performs branch, commit, and push operations deterministically. An optional allowlist firewall restricts outbound access to required endpoints; it is off by default and needs elevated container privileges. Every result returns through commits and a pull request that people can review, retry, discard, merge, or revert. Revert the commit or close the PR — the record of the attempt feeds the next one.

ProPR watches whether checks pass — an Ultrafix loop waits for green before it continues — but it works from the pull request conversation and never reads your CI logs. When a build or test fails, paste the failing output into a PR comment and ask for a fix. ProPR routes that into another isolated run and lands the correction as a follow-up commit on the same branch.

No. ProPR runs on provider subscriptions you may already pay for, including Claude Pro and ChatGPT Plus. Direct API keys work too, with metered billing. Use one provider or several, and route each phase to the agent that earns it. Either way, ProPR never marks up tokens.

Yes. Add a trigger label (such as AI or propr) to an issue and ProPR picks it up, implements the change in an isolated run, and opens a pull request linked back to the issue. Model labels like llm-claude-sonnet46 choose the agent, a base-<branch> label targets a non-default branch, and state labels track progress automatically. Several model labels on one issue produce separate branches and PRs to compare.

Planning splits a broad prompt into review-sized tasks, and Epic mode runs them as an ordered chain: each task becomes its own PR, and the next one starts only after the previous PR merges — optionally auto-merging on green CI. A large change ships as a sequence of reviewable diffs. Each branch stays focused.

Yes. The branch, commits, task page, and pull request give every agent the same visible starting point. A PR can start with one agent, get reviewed by another, and receive a follow-up from a third while the complete sequence remains in GitHub.

The planning flow builds a context preview before implementation starts. ProPR combines the files you name, files it believes are relevant, repository summaries, screenshots, attachments, and optional reference repositories. ProPR shows the model the code it needs without dumping the whole repository.

Plans, prompts, task history, commits, file changes, logs, model choices, cost, and follow-up activity stay attached to the task. Branches, commits, and PR conversations also remain in GitHub, where your existing tools can clone, grep, and diff them.

Yes. Agents run on your server, so a device only steers. The web UI is mobile-optimized for plans, tasks, logs, and dashboards, and because iteration happens in GitHub comments, the GitHub mobile app works as a remote control: label an issue, review the diff, leave a plain comment like Please handle 429 retries for temporary provider rate limits., and the follow-up commit lands on the same PR. See mobile and remote control.

Yes. The web UI is the primary interface. The CLI covers plans, tasks, repositories, agents, settings, todos, logs, active tasks, and system status, so scripts and CI jobs still use the normal review path.

You need a Docker-capable Linux host, GitHub access for the repositories you want to work on, and provider access for the agents you want to use. Plans, tasks, and task logs stay in your ProPR stack. The LLM calls go to the providers you configure. The quickstart takes you from install to the first agent PR.