VS Code: Latest response buried in long conversations with large plans

Resolved 💬 3 comments Opened Feb 6, 2026 by kevint4 Closed Feb 10, 2026

Description

In long conversation threads (especially ones involving plan mode with multiple rounds of implementation), the most recent response often appears visually buried in the middle of the conversation rather than being clearly visible at the bottom. This makes it very hard to find the latest answer.

Steps to Reproduce

  1. Have a long conversation in the VS Code extension that includes plan mode with a large, multi-section plan
  2. Implement the plan across multiple rounds of changes (the plan content stays rendered in the thread)
  3. Ask a follow-up question unrelated to the plan (e.g., "Will this work with TestFlight?")
  4. The response to the follow-up question appears somewhere above/within the previously-rendered plan content, rather than at the very bottom of the conversation

Expected Behavior

The most recent response should always be clearly visible at the bottom of the conversation thread, or the view should auto-scroll to show it. Previously-completed plan content should not obscure the latest response.

Actual Behavior

The latest response (a short answer to a simple question) is rendered far above a large block of previously-completed plan content. The user has to scroll up through hundreds of lines of already-implemented plan details to find the actual latest response.

Additional Context

The conversation in question had a large plan with ~5 rounds of auditing, each with detailed tables, code snippets, and file summaries. The plan content remained expanded in the thread. When a new question was asked, the short response appeared above all this plan content and was extremely difficult to locate.

It appears that context compression may be involved — when prior messages are compressed, the plan content that was part of an earlier response may get re-rendered below the latest response, pushing it out of view.

Environment

  • Claude Code VS Code extension
  • macOS

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗