[BUG] VS Code extension: after approving one of several queued edit approvals, chat scrolls to bottom instead of the next pending edit
Preflight Checklist
- [x] I have searched existing issues 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
What's Wrong?
With permission mode set to manual, when the model proposes edits to N files (e.g. 8), the chat stacks N approval tiles. After every single approval, the chat scrolls to the very bottom of the conversation — not to the next pending edit tile.
So for each remaining edit you must: scroll up, locate the correct (collapsed) tile, expand it, read the diff, approve — then the view jumps to the bottom again and the whole process repeats. For 8 queued edits that is 7 manual scroll-up-and-hunt cycles per turn.
What Should Happen?
After approving (or rejecting) an edit in a multi-edit approval queue, the view should scroll to the next pending approval tile and expand it, so the diff can be read and acted on immediately. At minimum, the view should not jump to the bottom while approvals are still pending.
Error Messages/Logs
Steps to Reproduce
- Set permission mode to manual (plan/manual approval for edits).
- Ask for a change that requires edits to many files (e.g. 8 files) so multiple edit approvals stack up in the chat.
- Scroll up, expand the first pending edit tile, review, and approve it.
- Observe: the chat scrolls to the bottom instead of moving to the next pending edit tile.
- Repeat for each remaining edit — each approval requires manually scrolling back up and finding the next tile.
Claude Model
Opus
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.233
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
VS Code integrated terminal
Additional Information
Related (both closed, neither covers the post-approval scroll target in a multi-edit queue): #72117 (input/permission prompts force-scroll chat to bottom, closed as duplicate), #58767 (auto-scroll during streaming, closed as not planned).
A companion issue filed alongside this one covers rejection behavior in the same multi-edit approval flow: rejecting edit k of N with a reason still forces review of edits k+1..N before control returns to the model.