Add unified "Accept All / Reject All" review panel for agent changes (like Windsurf Cascade)

Status Open
Maintainer reply None cached
Activity 1 comment · opened Aug 29, 2026

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

Currently, after Claude Code (VSCode extension) makes a series of file edits during a task, there's no single place to review and batch-accept or batch-reject all the changes it made. The two existing options are:

  1. Per-tool-call approval prompts during execution (Default permission mode) — this interrupts the agent mid-task rather than letting it finish and then reviewing holistically.
  2. Relying on VSCode's native git Source Control diff view after the fact — which works, but is a generic git staging UI, not something purpose-built for reviewing an agent's session of changes as a set.

Feature request:

Proposed Solution

A dedicated review panel, similar to Windsurf's Cascade, that appears once the agent finishes a task and shows:

  1. Every file changed during that task/turn, listed together.
  2. An Accept All and Reject All button for the whole batch.
  3. Per-file and per-hunk accept/reject controls within that same panel, so a user can selectively keep some changes and discard others without leaving the panel or manually using git commands.
  4. Ideally, changes rejected this way are cleanly reverted (not just unstaged) so the working tree matches what the user actually approved.

This would let users let the agent work autonomously through a multi-file change, then do one focused review pass at the end — rather than either interrupting every tool call or falling back to raw git diffing.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗