ROADMAP · BUILT IN THE OPEN · UPDATED AS COMMITS LAND
Roadmap
Revset is built in the open, so the plan is too. This page is the actual roadmap — what just shipped, what we're building right now, and what's queued behind it. No quarters, no vaporware.
HOW TO READ THIS
In progressUp nextExploringShippedThe whole plan, top of stack first.
New work sits on top, like revisions in a stack. Finished work sinks to the bottom — and stays shipped.
01
IN PROGRESS
Merge from Revset
Land a green stack without leaving the review — Revset merges each revision in order, no tab back to GitHub.
02
IN PROGRESS
Multi-line comments
Drag across a range of lines and the thread anchors to all of them — not just the one you happened to click.
03
IN PROGRESS
Merge queues
See where the bottom of your stack sits in the merge queue before you hit the button.
04
UP NEXT
Native GitHub stack support
Stacks show up on GitHub as real, ordered pull requests — reviewable there by teammates who never open Revset.
05
UP NEXT
Self-hosted Revset
Run the whole thing inside your own network. Same binary we run, your hardware, your keys.
06
UP NEXT
Public API & webhooks
Review state as an API — dashboards, or a webhook the moment a stack goes green.
07
EXPLORING
Editor integrations
Reviewed markers and threads inside VS Code and JetBrains, sitting next to the code they're about.
08
EXPLORING
Review analytics
Where stacks stall, how long re-reviews really take, which files eat the most rounds.
09
EXPLORING
GitLab support
The same re-review model, pointed at merge requests. Sooner if enough of you ask.
10
EXPLORING
Admin panel
Members, repos, and permissions in one place — who can review what, changed without filing a ticket.
11
EXPLORING
SSO Login
Sign in through the identity provider your org already runs, with membership kept in sync from there.
12
EXPLORING
Keyboard shortcut bindings
Remap the review flow to the keys your hands already know — the defaults are just a starting point.
13
EXPLORING
Links in comments
Paste a URL and it becomes a link — issues, docs, other threads, clickable right where the discussion is.
14
EXPLORING
Photos in comments
Drop a screenshot straight into a thread — before-and-after UI, a failing graph, whatever words won't carry.
15
EXPLORING
@user/file in comments
Type @ to pull a teammate or a file into the thread — people get pinged, files link to their diff.
ALREADY LANDED
Shipped means merged.
THE PLAN IS A CONVERSATION
Don't see it here?Ask us for it.
THE ROADMAP CHANGES WHEN THE CODE DOES · LAST SYNCED AUG 2026