Workflows
Review and request changes
Review sessions help you inspect modified files and turn review comments into a structured implementation handoff prompt.
How review sessions work
- Start a review session from the modified files panel when you want focused review context.
- Review sessions cannot be created from subagent sessions.
- A review session cannot be used to spawn another review session.
- For git-worktree parents, review sessions track parent linkage differently than local-session reviews.
Request changes flow
- Add comments in review, then use Request changes.
- The app creates a new implementation session in the same project.
- Comments are grouped by file and line range into a prefilled structured prompt.
- Modified file paths are appended for extra implementation context.
- The prompt is prefilled, not auto-sent, so you can edit before execution.
When this workflow is best
- Use for larger review rounds where comment structure matters.
- Use when multiple file-level comments need a single implementation pass.
- Use when you want a clean transition from review intent to build execution.
Failure cases to expect
- If no comments exist, Request changes will not create a handoff prompt.
- If the source review session is missing/invalid, the flow aborts safely.
- If session creation fails, no prompt handoff is generated.