Reviu
The review app for code your agent writes
Start new thread

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.

Add a comment

Replies

Best
Maker
📌
Hey Product Hunt - Joris here, maker of Reviu. This is my second launch. The first version was a native Git/GitHub client with an agent panel. After using it myself, I realized the important workflow was not just chatting with an agent, or rebuilding GitHub on desktop. It was the review loop after an agent changes code. So I rebuilt Reviu around sessions. Each session is tied to a project and checkout. Agents can run in isolated worktrees, their tool calls and file changes stay visible, and each turn ends with a diff receipt. You can comment on exact lines and send those comments back to the agent with file and line context. Checkpoints let you undo a turn or edit an earlier prompt without messing with HEAD or staged changes. The free app includes agent sessions, local diff review, worktrees, checkpoints, editor/terminal, and local Git workflows. Pro adds the GitHub layer: PR review, checks, merge, notifications, and browser handoff. I built this because I trust agents more when the boundary is clear: code the agent wrote vs code I actually reviewed.

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.

"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