Skip to main content
Let authorized collaborators start PRFlow from a GitHub comment, with no local Claude Code session open. A cloud command passes through an authorization gate before the agent job starts. The gate holds narrow GitHub permissions. The agent job then receives the model credentials and the repository permissions you configured. Maintainer-controlled workflow files and .prflow/config.json define both jobs. The run writes its work to a branch, a workpad, a pull request or a review. A cloud command moves from a GitHub comment through an authorization gate with narrow GitHub permissions, then into an agent job with model credentials and configured repository permissions. The agent job produces a branch, workpad, pull request or review for a person to review and merge.

​
What a Fresh Installation Ships

A fresh installation adds two workflow files, and they answer four comment commands:
No cloud run merges a pull request. Every command ends with work a person still has to read, approve and merge.
Automatic pull-request-triggered review is not included in a fresh installation. If you want a review to be requested without anyone typing a comment, add the workflow on Request a Review Automatically on Green CI.

​
Set Up Cloud Runs

1

Install the Cloud Tier

Run the installer from the repository root. See Cloud Installation.
2

Add Authentication and Project Setup

Add the model credential, review .prflow/config.json and declare how the runner is provisioned. See Cloud Setup.
3

Choose a Runner

Keep the default GitHub-hosted Linux runner, or point the workflows at your own. See Cloud Runners.
4

Learn the Comment Triggers

Learn the exact comment format and who is allowed to use it. See Cloud Triggers.
5

Try a Low-Stakes Run

Use a throwaway pull request or a small issue before you rely on the automation.

​
Keep It Running

Updates

Move an existing installation to a newer release without losing your configuration.

Recovery

Read a workpad status and resume a run that stopped before it finished.