Feature request: vertical scroll on long messages instead of "Show more" button

Resolved 💬 2 comments Opened Jun 14, 2026 by tolstoistudio Closed Jun 18, 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

When a message in the conversation is long, Claude Code truncates it and shows a "Show more" button at the bottom of the block.

I would prefer the block to have a fixed maximum height with vertical scroll instead of truncating and requiring a click to expand.

Current behavior

Long messages are truncated. A "Show more" button appears at the bottom-right of the block. Clicking it expands the full content.

Expected behavior

Long message blocks have a maximum height and are scrollable vertically. No truncation, no "Show more" — the content is accessible by scrolling within the block.

Why this is better

Keeps the conversation flow visible without losing context above
Reduces clicks — scroll is more natural for reading
The "Show more" pattern breaks reading flow when reviewing long structured content (tables, lists, step-by-step responses)
Environment

Claude Code VSCode extension
Windows 11

Proposed Solution

Replace the current truncation + "Show more" pattern with a scrollable container using CSS:

/ Instead of truncating with a "Show more" trigger /
.message-block {
max-height: 400px; / or a configurable value /
overflow-y: auto;
overflow-x: hidden;
}
Optionally, expose a user setting in settings.json to control the max height or toggle the behavior:

{
"claudeCode.messageTruncation": "scroll", // "scroll" | "expand" | "none"
"claudeCode.messageMaxHeight": 400
}
This would allow users to choose their preferred reading experience without removing the existing "Show more" option for those who prefer it.

Alternative Solutions

_No response_

Priority

Low - Nice to have

Feature Category

Interactive mode (TUI)

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

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