Repository navigation
[Bug] Ctrl+O triggers transcript view, not real-time verbose toggle - missing keyboard shortcut for live verbose output #14511
Description
Bug Description
There are two distinct verbose-related features that appear conflated in documentation and help text:
-
Real-time verbose output - enabled via
/config→ "Verbose output",--verboseflag, or settings.json. Shows detailed tool usage inline as Claude works. -
Transcript mode (Ctrl+O) - a separate historical view that takes over the screen and shows past session details, not real-time output.
Problems:
-
Missing feature: There's no keyboard shortcut to toggle real-time verbose output on/off while Claude is actively working. Users who want to quickly enable/disable verbose streaming during a session cannot do so without restarting with
--verboseor changing/config. -
Misleading help text: The
?help menu shows Ctrl+O as "Toggle verbose output" but it actually triggers transcript mode - a completely different full-screen historical view. -
Documentation gap: Issue Docs: Comprehensive documentation out of sync with changelog features #5068 noted that transcript mode lacks documentation. The distinction between these two features is not explained anywhere.
Expected behavior:
- A keyboard shortcut (perhaps Ctrl+O or another key) should toggle real-time verbose output on/off during active Claude execution
- Transcript mode should have a different shortcut or be accessible via slash command
- Help text should accurately describe what each shortcut does
Related issues: #5068 (documentation sync), #7554 (Ctrl+O conflicts), #2724 (transcript mode UX)
Environment Info
- Platform: linux
- Terminal: vscode
- Version: 2.0.72
- Feedback ID: 34abe5e6-c16f-4e38-b2db-2efc857747fb
Errors
[]
Activity
github-actions commentedon Jan 19, 2026
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
felix314159 commentedon Feb 16, 2026
Yes, real-time verbosity adjustment during an ongoing thinking process would be a nice feature
scapeshift-ojones commentedon Feb 16, 2026
This issue is tracked in the consolidated report at #26125, which covers the broken transcript mode (hidePastThinking hardcoded to true), mislabeled Ctrl+O help text, and post-compaction history inaccessibility — with source-level root cause analysis and a community patch. Please add your thumbs-up there to help it reach the oncall triage threshold.
scapeshift-ojones commentedon Feb 20, 2026
Still mislabeled as of v2.1.47. The
?help menu shows Ctrl+O as "toggle verbose output" but it activates transcript mode. The keybinding collision was noted in the original report and remains unfixed.This is now consolidated into #27242 alongside the deeper problem: even when transcript mode activates, it doesn't show pre-compaction history or thinking blocks. If this keybinding confusion has affected you, please 👍 and comment on #27242 to help reach the triage threshold.