SplashReview
Review the work, not the scrollback.
When an agent says it's done, you don't want 300 lines of transcript. You want the diff, anything that failed, and the final answer, next to each other, with a box to tell the agent what to fix.
What the Review panel shows
The latest response
The agent’s final message from the last turn, rendered as Markdown, without the tool calls in between.
Failures, up front
Failed tool calls and agent errors from the turn are listed, so a red test run can’t hide in the scroll.
Every changed file
The folder’s git changes against HEAD. Review all changes opens each one as a diff tab, unified or split.
The pull request
When the branch has a pull request on GitHub, it’s linked right there.
Feedback in the same thread
Send feedback continues the same conversation; Ask agent to review has the agent check its own work first.
Mark reviewed
Clears the item from Needs attention once you’ve looked.
Second opinions
Fork it for review.
When the agent supports it, Fork for review creates a separate conversation from the agent's current context and prepares a review message for you to send. The original conversation stays as it was.
- Try another approach forks without the review draft.
- Forks share the workspace folders with their parent, so file changes are shared too.