"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
PH 用户
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.
这是我第二次发布。第一个版本是一个原生 Git/GitHub 客户端，带一个智能体面板。自己用了一阵后，我意识到真正重要的工作流不只是跟智能体聊天，也不是在桌面端重造 GitHub，而是智能体改完代码之后的审查循环。
所以我把 Reviu 围绕会话重构了。
每个会话都绑定到一个项目和一个 checkout。智能体可以在隔离的 worktrees 里运行，它们的工具调用和文件改动始终可见，每一轮结束都会有一份 diff 回执。你可以评论到具体某一行，并把这些评论连同文件和行号上下文发回给智能体。Checkpoints 让你可以撤销某一轮，或者编辑更早的 prompt，而不用动 HEAD 或 staged changes。
免费版包含智能体会话、本地 diff 审查、worktrees、checkpoints、editor/terminal 和本地 Git 工作流。