[FEATURE] Code Review Mode: Dedicated UI for reviewing Claude's changes with inline comments

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

When Claude generates code changes, users must currently accept or reject entire modifications without granular review capabilities. There's no way to:

Examine exact line-by-line changes in context
Add inline questions or concerns to specific code sections
Request targeted revisions without losing the conversation context
Systematically review larger refactors or multi-file changes

This friction slows down workflows, especially for critical code sections where careful review is necessary before acceptance.

Proposed Solution

Add a dedicated code review interface that appears when Claude proposes changes. The ideal workflow:

Claude generates code changes

1. User clicks "Review Changes" instead of immediate Accept/Reject
2. Side-by-side diff view opens with syntax highlighting
3. User can click any line to add inline comments: "Why this approach?" or "Consider using X instead"
4. User can select "Request Changes" with their feedback attached
5. Claude sees comments and revises accordingly before re-presenting the changes
6. User can Approve, Request Changes, or Reject with optional reasoning

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Interactive mode (TUI)

Use Case Example

Scenario: Refactoring a critical authentication module

1. User asks Claude to refactor legacy auth code
2. Claude presents 150-line changes across 3 files
3. User clicks "Review Changes" → side-by-side diff opens
4. User sees a new password hashing approach on line 42, hovers and adds comment: "Why bcrypt instead of argon2? Security implications?"
5. User flags another section: "This breaks backward compatibility—need migration plan"
6. User clicks "Request Changes" with annotations
7. Claude receives feedback, revises implementation to address concerns
8. New diff presented; user approves

Additional Context

_No response_