Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [DOCS] Fullscreen rendering docs still describe Ctrl+O as transcript mode [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#45464•Fetched 2026-04-09 08:04:49
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
coygeekcoygeek
Participants
coygeekcoygeek
Timeline (top)
labeled ×2
RAW_BUFFERClick to expand / collapse

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/fullscreen

Section/Topic

The "Search and review the conversation" section, plus the Ctrl+O shortcut descriptions in the interactive mode and keybindings references.

Current Documentation

The fullscreen page currently says:

Press Ctrl+o to enter transcript mode. With fullscreen rendering active, transcript mode gains less-style navigation and search:

Esc, q, or Ctrl+o | Exit transcript mode

The interactive mode reference currently says:

Ctrl+O | Toggle verbose output | Shows detailed tool usage and execution. Also expands MCP read and search calls, which collapse to a single line like "Queried slack" by default

The keybindings reference currently says:

app:toggleTranscript | Ctrl+O | Toggle verbose transcript

What's Wrong or Missing?

Changelog v2.1.97 added a focus view toggle for CLAUDE_CODE_NO_FLICKER / fullscreen mode: Ctrl+O now shows the prompt, a one-line tool summary (including edit diffstats), and the final response.

The current docs still describe Ctrl+O only as transcript / verbose mode and do not explain the focus-view behavior in NO_FLICKER mode, what content it shows, or how it differs from the fuller transcript-style view described today.

That leaves the fullscreen documentation out of date for a user-visible shortcut and UI mode.

Suggested Improvement

Update the fullscreen rendering docs to describe the Ctrl+O focus view in CLAUDE_CODE_NO_FLICKER=1 sessions, including:

  • that the shortcut is available in fullscreen / NO_FLICKER mode
  • that the view shows the prompt, one-line tool summaries, edit diffstats, and the final response
  • how this differs from the existing transcript/verbose terminology already used elsewhere

Then update the shortcut references on the interactive mode and keybindings pages so they no longer describe Ctrl+O only as "verbose transcript" without the fullscreen-specific behavior.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageContext
https://code.claude.com/docs/en/fullscreenPrimary CLAUDE_CODE_NO_FLICKER / fullscreen behavior documentation
https://code.claude.com/docs/en/interactive-modeKeyboard shortcut reference for Ctrl+O
https://code.claude.com/docs/en/keybindingsDefault app:toggleTranscript binding description

Total scope: 3 pages affected

Source: Changelog v2.1.97

Exact changelog entry:

Added focus view toggle (Ctrl+O) in NO_FLICKER mode showing prompt, one-line tool summary with edit diffstats, and final response

extent analysis

TL;DR

Update the documentation for fullscreen rendering and keyboard shortcuts to reflect the new behavior of Ctrl+O in CLAUDE_CODE_NO_FLICKER mode.

Guidance

  • Review the changelog entry for v2.1.97 to understand the changes made to the Ctrl+O shortcut in NO_FLICKER mode.
  • Update the documentation on the affected pages (fullscreen, interactive mode, and keybindings) to describe the new focus view behavior, including the content it shows and how it differs from the existing transcript/verbose view.
  • Ensure that the updated documentation clearly explains the availability of the Ctrl+O shortcut in fullscreen/NO_FLICKER mode.
  • Verify that the changes are consistent across all affected pages to avoid confusion.

Example

No code snippet is necessary for this issue, as it is a documentation update.

Notes

The updates should be made to the following pages: https://code.claude.com/docs/en/fullscreen, https://code.claude.com/docs/en/interactive-mode, and https://code.claude.com/docs/en/keybindings.

Recommendation

Apply workaround: Update the documentation to reflect the new behavior of Ctrl+O in CLAUDE_CODE_NO_FLICKER mode, as this will improve the understanding of the feature and reduce user confusion.

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…
#tool integration#LLM response#prompt template#agent execution#callback error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING