Reviu - The review app for code your agent writes
by•
Since the first launch, Reviu was rebuilt from a Git client with an agent panel into a review workspace for coding agents. Run Claude Code, Codex, Gemini, and other ACP agents in durable sessions, inspect every diff, send inline comments back, checkpoint or undo turns, and finish the branch with real Git. Pro adds GitHub PR review, checks, merge, and notifications.
Replies
@joris_gallot The diff receipt after every turn is my favorite part. Being able to comment on one exact line and send it back to the agent with the file and line attached is so much better than typing "fix that thing in the function" ....
@oliver_graf1 Exactly! The useful unit is the turn: what changed, why, and can I reply on the exact line
@joris_gallot The turn receipt is a strong review primitive. I would add one more state beside reviewed. Verified should bind the exact tree to the command and exit code that passed. If a later turn touches that tree, both the line review and verifier result should expire. That keeps a clean diff from being mistaken for a working branch.
The per-turn diff receipt is the right primitive. Our worst agent-written bug was a spend function that looked fine in the diff, it was writing bad balance events that only surfaced three tables away, and we missed it because we reviewed the whole branch squashed instead of turn by turn. The thing I'd want to know is what happens when a later turn edits a file I already marked reviewed. If it silently stays green, the boundary you're describing leaks.
@asadmalik901 Yes, that's the boundary I care about too, "Reviewed" should mean this version of this change was reviewed. If a later turn edits those lines again, it needs to show up as reviewable again instead of staying silently green
@joris_gallot The thing that'll decide whether people trust it is the granularity. Re-open the whole file and reviewers start clicking through just to clear the noise, which is worse than stale green because now it looks deliberate. Line level, with the review I already gave still sitting next to the new diff, is the version I'd actually read.
"checkpoint or undo turns" is the feature I actually want - I've had claude code sessions where turn 4 did something I wanted to keep but turn 7 went off the rails and I had to manually untangle which file changes belonged to which turn. question on the undo though: if a turn already ran a shell command with a side effect outside the repo (hit an API, wrote to a db, pushed somewhere), does undo just revert the file diff and leave you to clean up the side effect yourself, or does it track that boundary too
@galdayan Great question, checkpoints are repo-state only: Reviu snapshots the working tree before the turn, then undo restores those files. It does not reset HEAD, staged changes, APIs, DB writes, pushes, etc
@joris_gallot that makes sense as a boundary, but it means the diff receipt can show a clean undo while a db write or an api call from that same turn is still sitting out there live. is there any surfacing of that at all, even just a warning like "this turn also did X outside the repo, undo won't touch it" or is it on the human reviewer to remember which turns had side effects before hitting undo