[FEATURE] detailed description pane
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
Description
Currently, viewing the "thinking" mode and detailed transcript requires pressing Ctrl+O to toggle the view. This interrupts workflow and makes it difficult to monitor Claude's reasoning process in real-time.
Proposed Solution
Proposed Feature
Add an optional persistent pane on the right side of the terminal window that always displays:
- Thinking tokens (extended thinking/reasoning)
- Detailed transcript of the conversation
Alternative Solutions
Ctrl + O but it would be great to not have to interrupt workflow with this mode
Priority
Medium - Would be very helpful
Feature Category
Interactive mode (TUI)
Use Case Example
Description
Currently, viewing the "thinking" mode and detailed transcript requires pressing Ctrl+O to toggle the view. This interrupts workflow and makes it difficult to monitor Claude's reasoning process in real-time.
Proposed Feature
Add an optional persistent pane on the right side of the terminal window that always displays:
- Thinking tokens (extended thinking/reasoning)
- Detailed transcript of the conversation
UI Concept
┌──────────────────────────────────┐
│ │ Thinking & Transcript│
│ Main conversation area │──────────────│
│ │ <thinking> │
│ │ Let me analyze... │
│ │ </thinking> │
│ │ │
│ │ [Tool: Read] │
│ │ file: src/index.ts │
│ │ │
└───────────────────────────────── ┘
Benefits
- Monitor Claude's reasoning without interrupting the main view
- Better visibility into tool calls and decision-making process
- Useful for debugging, learning, and understanding Claude's behavior
- Optional - users who prefer the current behavior can keep it
Suggested Implementation
- New setting to enable/disable the side pane (e.g.,
showThinkingPane: true) - Keyboard shortcut to toggle pane visibility
- Configurable pane width
- Thin border separating panes for minimal visual noise
Additional Context
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗