A GitHub pull request dashboard that shows what needs you next.
See what Needs you, what is Waiting on others, and what can wait. PR Flow reads GitHub through your gh CLI session and keeps the queue in the menu bar or system tray.
An action queue beside GitHub, not a replacement for it.
Keep GitHub for repository work. PR Flow gives you a desktop view of the review actions spread across repositories and, when needed, other providers.
It stops at the boundary of GitHub
GitHub pull requests can sit beside GitLab merge requests, Azure DevOps pull requests, and Gerrit changes while keeping their provider identity.
The notifications inbox is still event-shaped
A push, comment, or failed check is activity. PR Flow instead names the action it sees: review, reply, fix CI, merge, or wait.
Who holds the ball?
Current review state determines the smart view and position. Older work remains visible when newer events arrive.
Unresolved threads as a signal
Unresolved review conversations appear on the row. When a teammate replies to your comment, the PR returns to Needs you with a Reply action.
Your GitHub review state, resolved into one ranked list.
Two very different jobs, kept apart.
Requested reviews and replies sit under Needs you. Submitted PRs can wait quietly under Waiting on others. The full ordering rules are on the pull request review queue page.
- Needs you — review requested, or changes requested on your PR
- Your PRs — what you opened, and what is holding each one up
- Waiting on others — submitted, correctly out of your hands
Threads are state, not history.
PR Flow counts unresolved conversations on the row. If Agent Pipelines is configured and thread summaries are enabled, your chosen AI provider can condense a long thread.
- Unresolved thread counts on the row, before you open anything
- Thread summaries for discussions that grew past reading
- Reply to a thread from the app, previewed before it posts
A real GitHub review, from the menu bar.
Read the unified diff, stage line comments and replies, choose a GitHub review outcome, then submit. Enabled AI findings can be accepted into staged comments or dismissed; they do not post on their own.
- Re-review delta tracks what changed since your last review pass
- Review comments are staged and previewed before submission
- Merging remains your deliberate action on GitHub
- Press O to open any diff line in your editor
Three things, then it is running.
Install PR Flow
macOS, Windows or Linux. It starts in the menu bar or system tray. The 14-day trial needs no account, email or card.
Check your CLI
PR Flow reads GitHub through the session you already have. If this prints an account, there is nothing else to do.
Turn GitHub on
Enable GitHub in Settings. The first poll fills the queue; later refreshes run in the background.
Beyond what the native dashboard covers.
Stale reviews get louder
A 4px border on each row encodes age — fresh, warm, stale. The request from last Thursday stops being invisible just because newer rows arrived above it.
Digests instead of a live feed
A scheduled OS notification for what needs you and what has gone stale. With the AI estimate enabled, it can also include queued review effort.
Nudges you preview first
PR Flow can draft a nudge when your PR is waiting. You choose the recipient, preview the text, and send it yourself.
Zero org install required
No GitHub App or organization-wide permissions. PR Flow authenticates locally through your existing gh CLI session. If you also work across GitLab (glab) or Azure DevOps, they share the same queue without cloud connectors.
Working across more than GitHub? The same queue holds GitLab merge requests, Gerrit changes and Azure DevOps pull requests — see the full pull request dashboard.
GitHub specifics.
Do I have to give PR Flow a GitHub token?
Does it replace GitHub notifications?
Can I actually approve a pull request from the app?
Does it work with GitHub Enterprise?
What about repositories I only occasionally touch?
Keep reading
Pull request dashboard
One ranked queue for pull requests spread across repos and providers.
Pull request review queue
How PR Flow decides which review needs you next, and why that beats a feed.
Stacked pull requests
Stacks as one ordered journey — position markers, a map, and layer-by-layer review.
Local AI code review
AI review on your own provider — a CLI, a local model, or your gateway.
From the blog
Who Owns the Next Move on a Pull Request?
Open, review requested and approved don't answer who has to act next. A plain event-driven model for pull request ownership, and where it stops helping.
How to Re-review a Pull Request Without Starting Over
Re-reviewing a pull request is a race against context decay. How to inspect what changed since your last review without re-reading the entire diff from scratch.
Keep your GitHub next actions together.
You still review and merge. PR Flow keeps the queue and review workspace ready. Try it free for 14 days; a one-time licence keeps it after the trial.