One GitLab merge request dashboard for everything that needs you.
Merge requests scattered across projects, groups and a self-managed instance, ranked into a single queue on your desktop — read through the glab CLI session you already have.
Groups and projects are great for organizing code. Less so for organizing you.
GitLab's structure is built around where code lives. Your review workload is organized around something else entirely: which merge requests are currently stuck on a decision from you.
Your work crosses the group tree
A single week can touch merge requests in half a dozen projects across two or three groups. GitLab's per-project MR list is exact and complete for one project at a time, which is precisely the wrong unit — it makes you the thing that aggregates.
Assignee and reviewer are not the same role
GitLab distinguishes the two, but a flat merge request list does not make the consequence obvious: an MR assigned to you as author needs a push or a rebase, while one where you are the reviewer needs a decision. Different work, mixed together.
To-Do items are a queue you have to garden
GitLab To-Dos are closer to a work list than a raw feed, but they only accumulate what was explicitly triggered, and they stay until you tick them off by hand. An MR that quietly went stale after you cleared its To-Do leaves nothing behind.
Unresolved discussions decide who holds the ball
An MR with two open discussion threads is waiting on somebody, and which somebody it is determines whether you should look at it today. That count is one click into the changes tab rather than something you can scan across everything at once.
Merge requests, ranked by who is blocked.
One list, whatever group the project lives in.
There is no per-project setup and no allowlist to keep current. Turn GitLab on and the merge requests you are involved in appear — from any project your glab session can see — classified into what needs you, what you authored, and what is correctly waiting on someone else.
- Smart views: Needs you · Your MRs · Waiting on others · Recently done
- A GitLab dot on every row, so provider is never ambiguous
- Unresolved discussion counts before you open anything
- Track an individual MR by URL, even outside your usual projects
Read the diff, resolve the discussion, submit.
Open a merge request for its diff stats, discussions, an AI estimate of complexity and risk, and any linked Jira, Linear or Trello ticket. Then review it properly in the app: a full unified diff with per-file “viewed” tracking, line comments, thread replies, and a verdict.
- Approve, request changes or comment — submitted to GitLab as one review
- Nothing posts until you press submit; PR Flow never merges
- Every write is recorded in a local audit log on your machine
- “Submit & next” walks you down the queue
Built for instances that never leave your network.
Plenty of GitLab installs are self-managed precisely because the code should not sit on someone else's infrastructure. A hosted review dashboard reintroduces the exact problem that decision was meant to avoid.
Your instance, your session
PR Flow follows your glab session wherever it is authenticated. No inbound access, no webhook to configure, no allowlisted IP range.
Nothing routed through us
Requests go straight from your machine to your GitLab. There is no PR Flow backend proxying them, and your code and diffs never touch our servers.
Alongside other providers
Teams that self-manage GitLab often still have code on GitHub or in Gerrit. Those sit in the same queue, without a second tool.
Full details in the security overview and privacy policy. AI review follows the same rule — see local AI code review.
If glab works, you are done.
Install PR Flow
macOS, Windows or Linux. Free for 14 days — no account, email or card.
Confirm your session
PR Flow uses the same authentication your terminal already has.
Enable GitLab
One switch in Settings. Merge requests appear on the first poll and refresh quietly from then on.
GitLab specifics.
Does it work with self-managed GitLab?
Do I need to give PR Flow a GitLab access token?
Can I approve a merge request from the app?
Does it say "pull request" everywhere?
We use GitLab and something else. Does that work?
Keep reading
See which merge requests are waiting on you.
Point PR Flow at your GitLab instance and let it tell you which MR is actually blocking someone. Free for 14 days.