[FEATURE] Visual Navigation Minimap, Prompt Anchors, and Interactive Keybindings for Session History

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

As Claude Code sessions grow during complex, long-running engineering tasks, navigating back through the terminal scrollback history becomes a major bottleneck.Currently, long code blocks, multi-file tool outputs, and expansive assistant responses create a "scroll-fest" environment. Prompts blend into surrounding text data, making it difficult to visually locate where a specific prompt was injected or quickly flip back and forth between previous question-answer iterations.While the Ctrl+O transcript view offers vim-like { and } paragraph motions, exiting the live terminal prompt area to step into a separate view disrupts active developer muscle memory.

Proposed Solution

We propose introducing a native, interactive navigation layer directly inside the core TUI (Terminal User Interface) consisting of three cohesive components:

1. Visual Separators & Structural Anchor Bars

• Prominent Prompt Demarcations: Introduce a high-contrast, visually distinct horizontal separator line or border before every new user prompt block.
• Block Anchors: Render explicit structural indicators (e.g., text indicators, distinct color blocks, or unique symbols) marking the boundary where a user query transitions into Claude's workspace context.

2. Sidebar/Edge Conversation Minimap

• Compact History Map: Implement a narrow vertical minimap panel pinned to the right or left edge of the terminal view.
• Input Marker Bar: Display a dynamic timeline or scale featuring subtle "ticks" or colored marker nodes representing the precise spatial positions of prior user inputs versus system outputs. This behaves similarly to how IDE scrollbars register compilation warnings or search results.

3. Native Hotkeys for Block Jumping

• Interactive View Navigation: Introduce a pair of native interactive keybindings—ideally Ctrl+Up / Ctrl+Down (or configurable alternatives)—to instantly snap the terminal view pane up or down directly to the nearest message boundary.
• Context Preservation: Ensure this scrolls the interface view seamlessly without breaking, clearing, or losing focus on the active input cursor sitting at the bottom of the prompt.

Alternative Solutions

• Using external log parsers: Community utilities like claude-run or local script web viewers parse JSONL history into static, timeline-based web GUIs. However, switching contexts out of the developer terminal entirely breaks terminal velocity.
• Terminal Emulator Specific Hacks: Relying on native shell integration markers (OSC 133 sequences) via specialized terminal configurations (like iTerm2 or VS Code tasks). This lacks portability and drops out completely for developers working over basic SSH shells or standard terminal wrappers.

Priority

High - Significant impact on productivity

Feature Category

Performance and speed

Use Case Example

_No response_

Additional Context

This enhancement unifies existing navigation concepts present across modern IDE tools into Claude Code's text terminal environment. Providing quick visual and physical anchors significantly drops the cognitive overhead required to review previous debugging logs, command patterns, and system responses during extensive development cycles.