[BUG] VS Code plan review: comments panel has no internal scroll, approve/submit action unreachable (still broken in 2.1.270)

### Preflight Checklist

- [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code

> Note on the first checkbox: this bug **has** been reported — five times. Every one of those reports is now closed, and there is no open issue tracking it. See "Why this is a new issue and not a duplicate" below. I am filing a fresh report because the bot instructions on the closed issues explicitly say to do so ("Please open a new issue if this is still relevant").

### What's Wrong?

In the Claude Code VS Code extension, the plan-review flow renders accumulated inline comments in a "Comments (N)" block above the plan-approval actions. That block has **no internal scroll**. Once enough comments are added (roughly 10+, depending on window height), the block grows taller than the viewport and pushes the "Yes, approve plan" / submit action — and the prompt input below it — off the bottom of the panel, with no way to scroll to them.

The result is that a plan review can be composed but not submitted. All the review work is stuck in the UI.

Details:

- The comment list does not scroll internally, and the surrounding panel does not scroll far enough to reach the action row.
- The action row is not pinned or otherwise kept visible.
- Keyboard submit (Cmd/Ctrl+Enter) does not work as an escape hatch.
- There is no collapse control on the comment thread and no Command Palette command to submit the review.
- Cancelling the plan panel discards the comments — they are not persisted anywhere and are not delivered to the model, so the work is simply lost.

The only known workaround is repeatedly zooming the VS Code UI out (Ctrl/Cmd+`-`) until the action row fits back on screen.

Reproduced on Claude Code VS Code extension **2.1.270** (linux-x64, WSL2), and reported by others continuously since 2.1.83 in April 2026.

### What Should Happen?

The comment list should scroll internally, and/or the plan-approval action row and prompt input should be pinned so they remain reachable regardless of how many comments have been added. A review should always be submittable.

As a secondary safeguard, in-progress plan comments should survive a panel close or window reload rather than being discarded.

### Error Messages/Logs

```shell

```

### Steps to Reproduce

1. Open a workspace in VS Code with the Claude Code extension.
2. Enter plan mode and have Claude produce a plan of reasonable length.
3. Select text in the plan and add inline comments — around 10 or more, depending on window height.
4. Return to the chat panel to submit the review.
5. The "Comments (N)" block fills the panel; the "Yes, approve plan" / submit action and the prompt input are below the fold and cannot be scrolled to. Ctrl/Cmd+Enter does nothing.

### Why this is a new issue and not a duplicate

This bug has been reported at least four times, and a closely related scroll bug in the same extension a fifth. Every report is closed, and the closure chain is circular: new reports get auto-closed as duplicates of older reports that were themselves auto-closed for inactivity. No issue about this bug is currently open, so there is nothing left to "duplicate" and nothing tracking the fix.

| Issue | Filed | Version | Outcome |
| --- | --- | --- | --- |
| #42697 | 2026-04-02 | 2.1.84 | Auto-closed 2026-05-11 as inactive (`stale`) |
| #43501 | 2026-04-04 | 2.1.83 | Auto-closed 2026-04-08 as duplicate of #42697 — which then went stale |
| #66133 | 2026-06-07 | 2.1.167 | Labeled `bug`, `has repro`, `area:ide`, `area:ui`, `platform:vscode`. Auto-closed 2026-09-10 as inactive |
| #68328 | 2026-06-14 | 2.1.81 | Auto-closed 2026-06-17 as duplicate of #66133 — which then went stale |
| #68732 * | 2026-06-16 | 2.1.178 | Auto-closed 2026-06-19 as duplicate of #68544 — which was itself auto-closed as inactive on 2026-09-09 |

\* #68732 is the adjacent bug — scroll not working in the extension's conversation area, with the wheel captured by prompt-history navigation — included here because it followed the identical closure pattern. Its duplicate target #68544 is closed-stale, and the other suggested targets were #66601 (closed as duplicate) and #65833 (open, but filed against the TUI, not the extension).

So the reports that were dismissed as duplicates were not duplicates in any useful sense; they were fresh confirmations that the bug is still present, and each one was pointed at an issue that no longer had a heartbeat. #66133 in particular carried full reproduction steps and a `has repro` label and was still closed as inactive. Every one of these issues is now locked, so the reporters cannot even comment on them.

Related: #87647 tracks the broader problem of `has repro` issues being auto-closed by the bot. #48945 (also closed as inactive) covers plan comments not reaching the model, which is why cancelling out of the panel is not a workaround.

Request: please exempt this issue from the auto-duplicate and auto-stale bots, or point it at a genuinely open tracking issue. Auto-closing it will only produce a sixth report in a few weeks.

### Claude Model

Opus

### Is this a regression?

No, this never worked

### Last Working Version

_No response_

### Claude Code Version

VS Code extension 2.1.270 (linux-x64); CLI 2.1.260

### Platform

Anthropic API

### Operating System

Ubuntu/Debian Linux

### Terminal/Shell

Other

### Additional Information

Environment: Windows 11 + WSL2 (Ubuntu), VS Code 1.109.2, Claude Code native VS Code extension (`anthropic.claude-code-2.1.270-linux-x64`) — not the integrated terminal.

Prior reports cover macOS (arm64) and WSL/Linux, so this does not look platform-specific.

Start in the Claude Code VS Code extension's plan-review flow and reproduce the issue with about 10 inline comments in a short viewport. Trace the Comments (N) block, approval action, and prompt input to identify why the action remains unreachable; done means a review stays submittable regardless of comment count, with any persistence behavior verified separately.

Written by the indexing model from the issue text.