Skip to content
ReviewOS
Features
Review
Durable review threads
Comments that follow the line through a rebase instead of vanishing.
Stacked pull requests
Dependent changes that merge in order and retarget themselves.
Agentic review
Coding agents as first-class authors and reviewers, with the audit trail to match.
Diffs that stay fast
Rendered on the server, against the merge base, readable at a hundred files.
Merge strategies and rules
Merge, squash, or rebase, gated by approvals, threads, and checks.
Repositories
Plain git hosting
Ordinary bare repositories on your disk, driven by the git binary.
Issues that link up
One number sequence, closing keywords, and references that resolve.
Search that reads like a query
Qualifiers, quoting, and negation, parsed properly rather than by regex.
Automation
Checks from your own CI
A status API your existing pipeline reports into, enforced at merge.
Webhooks you can trust
Signed, retried with backoff, and blocked from reaching your own network.
Notifications worth reading
Every message says why it reached you, and a burst arrives as one.
Operations
Self-hosting without a cluster
One database and one process. Scale the parts that need it, later.
Pages for every repository
A docs folder is a documentation site. Push, and the site is the branch.
Every feature, in one place.
All features
Repositories
Activity
Docs
Sign in
Sign up
Reload
also looking at this
stacks
/
rfcs
RFC 0006: classify every SHOULD and MAY in Protocol 1.0 Part I
#7
Open
chris wants to merge
rfc-0006-should-and-may
into
main
1 file
+174
-0
Conversation
Commits
Checks
Files changed
Review screen
9a9dccc98c
docs(rfc): 0006 classifies every SHOULD and MAY in Part I
Chris
review this step