claude-code - 💡(How to fix) Fix [Bug] Message renderer truncates long outputs without full scrollable content [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#45395Fetched 2026-04-09 08:06:25
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
Timeline (top)
labeled ×3closed ×1commented ×1

Code Example

[]
RAW_BUFFERClick to expand / collapse

Bug Description I am using the new renderer for this chat and the output for this message was long and the renderer didn't show the whole output from claude. It mentioned that there were ~8 points but it didn't show me the first few points. I had to /export the chat to a txt file to read the full output.

Environment Info

  • Platform: darwin
  • Terminal: iTerm.app
  • Version: 2.1.96
  • Feedback ID: 261ad96f-b6f6-4434-b9a8-008ae7f112fa

Errors

[]

Attaching how it looks on my screen right now:

<img width="1420" height="925" alt="Image" src="https://github.com/user-attachments/assets/5f7d41bc-c2ca-4ab7-b1bc-e20cf7ba2558" />

extent analysis

TL;DR

The issue can be mitigated by using the /export command to view the full output in a text file, as the new renderer has limitations in displaying long outputs.

Guidance

  • The new renderer may have a character limit or rendering issue, causing it to truncate long outputs.
  • To verify the issue, try rendering a shorter output and see if it displays correctly.
  • As a workaround, use the /export command to export the chat to a text file, allowing you to view the full output.
  • Consider providing feedback with the Feedback ID to help the developers address the rendering issue.

Notes

The exact cause of the rendering issue is unclear, but it appears to be related to the length of the output. The provided Errors JSON array is empty, indicating that there may not be a specific error message to investigate.

Recommendation

Apply workaround: Using the /export command to view the full output in a text file is a reliable workaround until the rendering issue is addressed.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING