Reviu is a native desktop app for reviewing agent-written code before you push. Run Claude Code, Codex, Gemini and other ACP agents in durable sessions, inspect every diff, send comments back to the agent, then stage, rebase, commit, open PRs and review GitHub pull requests without leaving the app.
This is the 2nd launch from Reviu. View more
Reviu
Launching today
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.
Free Options
Launch Team / Built With
"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
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.