claude-code - 💡(How to fix) Fix [Bug] Ctrl+E toggle state mismatch in transcript viewer: messages not showing [1 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#46261Fetched 2026-04-11 06:24:59
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
0
Author
Participants
Timeline (top)
labeled ×4renamed ×1
RAW_BUFFERClick to expand / collapse

Bug Description Bug: Ctrl+E in transcript viewer toggles state but does not hide/show messages

Version: Claude Code v2.1.89 OS: macOS 25.2.0

Description: In the transcript viewer, pressing Ctrl+E toggles the label between "ctrl+e to hide N previous messages" and "ctrl+e to show N previous messages" correctly, but the actual messages are not hidden or shown — the visible content remains identical in both states.

Steps to reproduce:

  1. Open transcript viewer with Ctrl+O
  2. Observe label: "ctrl+e to show N previous messages"
  3. Press Ctrl+E
  4. Label changes to "ctrl+e to hide N previous messages"
  5. But the messages above are still fully visible — nothing is hidden

Expected: Previous messages collapse/hide when Ctrl+E is pressed (state = "show") Actual: Messages remain visible regardless of toggle state

<img height="122" alt="Image" src="https://github.com/user-attachments/assets/d8837a37-0122-4ac7-b9f5-722b26313a69" /> <img height="122" alt="Image" src="https://github.com/user-attachments/assets/98ef50c1-e741-4adb-9407-77feea02def8" />

Environment Info

  • Platform: darwin
  • Terminal: iTerm.app
  • Version: 2.1.89
  • Feedback ID: e2324a59-0435-409c-aca4-133b508be9c6

extent analysis

TL;DR

The issue can be addressed by investigating and fixing the logic behind the Ctrl+E toggle functionality in the transcript viewer.

Guidance

  • Review the code handling the Ctrl+E key press event to ensure it correctly updates the visibility of previous messages based on the toggle state.
  • Verify that the CSS or styling responsible for hiding/showing messages is correctly applied when the state changes.
  • Check for any JavaScript errors or console logs that might indicate why the messages are not being hidden or shown as expected.
  • Inspect the HTML structure of the transcript viewer to ensure that the messages are properly wrapped in elements that can be targeted by the hide/show functionality.

Example

No specific code example can be provided without access to the actual codebase, but the fix would involve ensuring that the element containing the messages has a class or ID that can be targeted by the JavaScript code handling the Ctrl+E event, and that this code applies the correct CSS to hide or show these messages based on the toggle state.

Notes

The provided information does not include specific code snippets or detailed technical implementation details, making it challenging to provide a precise fix. The issue seems to be related to the front-end logic and CSS styling rather than a back-end or server-side problem.

Recommendation

Apply a workaround by manually adjusting the CSS in the browser's developer tools to hide or show the messages when the Ctrl+E state changes, to verify if the issue is indeed related to the CSS application. This can help in isolating the problem and guiding further debugging efforts.

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