Per repo. Not per person.

Adding teammates is always free — pay only for the private repos Read PR watches. Public repos are on us.

Charged via Stripe. Pro-rated to the day. Disable a repo and the meter stops on the next reconcile.

Questions, answered.

The ten things engineers and security leads actually ask before installing.

What does Read PR actually do?+

Read PR is a GitHub App and browser extension. The app posts a required status check on every pull request. The extension tracks reading time per file as a reviewer scrolls through GitHub's diff view. The check turns green when each reviewer has met the per-file reading threshold for the repo. It does nothing else — it doesn't read the diff, summarise the change, or post comments.

Doesn't this feel like surveillance?+

We track reading, not readers. Read PR records dwell time per file, focus events, and which file is on screen. It does not record keystrokes, mouse paths, screen contents, scroll positions inside files, the contents of the code, or anything outside github.com pull-request pages. The extension is open source. Per-PR records expire 90 days after the PR closes unless your retention policy is longer.

Can a reviewer leave the tab open and walk away?+

No. Reading time only accumulates while the file is on screen, the tab is focused, and there are signs of life — scroll movement or focus events. Open the tab and walk away and the timer pauses immediately.

What if a reviewer doesn't have the extension installed?+

The CI check stays pending. The PR page shows a one-line nudge to install the extension. Optional manual attestation can be enabled per repo for one-off reviewers — audited the same way as a normal reading record, with the attestation flagged.

Does this slow down review?+

No. The reading thresholds are configurable per repo and scale with file size. The defaults — 15 seconds minimum, 5 seconds per 100 lines, 3 minutes max per file — match how senior engineers actually read code. Lockfiles and generated files are excluded by default.

Does it work with required reviewers and CODEOWNERS?+

Yes. Read PR sits as a separate required status check alongside your normal review requirements. Branch protection treats it the same as a passing test suite. CODEOWNERS still controls who is asked to review; Read PR controls whether their approval counts.

Will it post a comment on every PR?+

It posts a single status check. No comments by default. The extension shows the progress ring inline next to each file in the GitHub UI — no PR comment thread spam.

What's the pricing?+

Public repositories are free, forever. Private repositories are $8 per repo per month, with the first private repo included. Adding teammates is free — there are no per-seat charges. Billed via Stripe, prorated to the day.

Which browsers and Git hosts are supported?+

Chrome, Edge, and Firefox today. Safari is on the roadmap. GitHub.com and GitHub Enterprise Cloud are supported. GitHub Enterprise Server is available on the Enterprise plan.

What happens to old reading records?+

Per-file reading state clears when the PR closes or merges. Aggregate reviewer history is kept for 90 days, then deleted. Workspaces with audit retention requirements can extend retention indefinitely.