claude-code - 💡(How to fix) Fix [Bug] Ctrl+O verbose/transcript view freezes — new messages and agent responses don't render until toggled off [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#53353Fetched 2026-04-26 05:17:57
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
Timeline (top)
labeled ×4commented ×1

In Claude Code v2.1.119 on macOS, after toggling verbose/transcript view with Ctrl+O, the view appears to freeze:

  • New user prompts and agent responses are not rendered while the transcript view is active.
  • The agent does receive and process new messages — they're just invisible until you toggle Ctrl+O off.
  • Toggling Ctrl+O off immediately reveals all the "missing" output.

This makes the verbose/transcript view effectively unusable for ongoing conversations: it looks frozen, but work is silently happening underneath.

Root Cause

In Claude Code v2.1.119 on macOS, after toggling verbose/transcript view with Ctrl+O, the view appears to freeze:

  • New user prompts and agent responses are not rendered while the transcript view is active.
  • The agent does receive and process new messages — they're just invisible until you toggle Ctrl+O off.
  • Toggling Ctrl+O off immediately reveals all the "missing" output.

This makes the verbose/transcript view effectively unusable for ongoing conversations: it looks frozen, but work is silently happening underneath.

Fix Action

Workaround

Toggle Ctrl+O off whenever you want to see new output, then optionally toggle back on to inspect it with verbose annotations.

RAW_BUFFERClick to expand / collapse

Summary

In Claude Code v2.1.119 on macOS, after toggling verbose/transcript view with Ctrl+O, the view appears to freeze:

  • New user prompts and agent responses are not rendered while the transcript view is active.
  • The agent does receive and process new messages — they're just invisible until you toggle Ctrl+O off.
  • Toggling Ctrl+O off immediately reveals all the "missing" output.

This makes the verbose/transcript view effectively unusable for ongoing conversations: it looks frozen, but work is silently happening underneath.

Environment

  • Claude Code: 2.1.119
  • Model tested: claude-haiku-4-5-20251001 (launched with --model haiku)
  • macOS: 26.3.1 (build 25D771280a)
  • Node: v24.12.0
  • Shell: zsh
  • Terminal: reproduced inside tmux 3.6a (TERM=tmux-256color); originally observed in a regular macOS terminal as well

Reproduction steps

  1. Launch Claude Code: claude --model haiku in any directory.
  2. Send a message, e.g. say hi in one word. Confirm you get a response (Hi).
  3. Press Ctrl+O. The footer changes to: Showing detailed transcript · ctrl+o to toggle · ↑↓ scroll · [ to print output · v to open in vi Existing messages now show a timestamp + model annotation (e.g. 12:36 PM claude-haiku-4-5-20251001).
  4. Send a new message, e.g. count slowly from 1 to 5, one number per line.
  5. Wait for the agent to finish (Haiku responds in a few seconds).
  6. Observe the transcript view: neither the new prompt nor the agent's response appears.
  7. Press Ctrl+O again to exit transcript view.
  8. The previously missing prompt and response are now visible in normal history.

Expected behavior

While transcript / verbose view is active, new user prompts and agent responses (including streaming output) should render in real time, the same way they do in normal view — just with the additional verbose annotations (timestamps, model, etc.).

Actual behavior

The transcript view behaves like a static snapshot taken at the moment Ctrl+O was pressed. Anything that happens afterward is hidden until you toggle Ctrl+O off, at which point the new content suddenly appears.

Additional notes

  • Confirmed the agent is actually running while the view appears frozen — the response is fully present in history once Ctrl+O is toggled off.
  • The current input prompt also seems to swallow keystrokes for viewer navigation (↑↓, [, v) while in transcript view, which compounds the perception that the UI is unresponsive. (This may be intentional, but combined with the missing-render bug it makes verbose mode look completely dead.)
  • Possibly related but distinct issues: #46261 (Ctrl+E transcript toggle state mismatch on macOS), #40984 (Ctrl+O hides Claude questions), #48083 (Write tool diffs missing in verbose mode), #25980 (thinking blocks not shown in verbose).

Workaround

Toggle Ctrl+O off whenever you want to see new output, then optionally toggle back on to inspect it with verbose annotations.

extent analysis

TL;DR

The issue can be temporarily worked around by toggling Ctrl+O off to see new output and then toggling back on to view it with verbose annotations.

Guidance

  • Verify that the agent is indeed processing new messages by checking the history after toggling Ctrl+O off, as the issue might be related to rendering rather than processing.
  • Test if the problem persists across different models or environments to isolate if it's specific to claude-haiku-4-5-20251001 or macOS.
  • Consider checking for any updates to Claude Code, as this issue might have been addressed in a later version.
  • Review related issues (#46261, #40984, #48083, #25980) to see if any fixes or workarounds apply to this scenario.

Example

No specific code snippet can be provided without more context on the internal workings of Claude Code, but checking the rendering logic for the transcript view might yield insights into why new messages are not being displayed.

Notes

The exact cause of the issue is unclear without more information on how Claude Code handles rendering in verbose mode. It's possible that there's a bug in the rendering logic or an issue with how user input is handled while in transcript view.

Recommendation

Apply the workaround of toggling Ctrl+O off and on as needed, as there's no clear indication of a permanent fix available in the provided information. This allows for continued use of the verbose mode for inspection while mitigating the rendering issue.

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…

FAQ

Expected behavior

While transcript / verbose view is active, new user prompts and agent responses (including streaming output) should render in real time, the same way they do in normal view — just with the additional verbose annotations (timestamps, model, etc.).

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [Bug] Ctrl+O verbose/transcript view freezes — new messages and agent responses don't render until toggled off [1 comments, 2 participants]