[FEATURE] Session/Conversation Block Navigation within Claude Code

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

When using Claude Code in a terminal, after multiple rounds of conversation with extensive output, it becomes difficult to navigate back to find where specific conversations started.

Modern terminals like Warp have a "blocks" feature that allows users to select and navigate between command blocks using arrow keys. However, since Claude Code is essentially a "terminal within a
terminal," the outer terminal (Warp, iTerm2, etc.) can only see Claude Code as a single running process and cannot detect the individual conversation turns happening inside.

Proposed Solution

Add a built-in navigation feature within Claude Code that allows users to:

1. Jump between conversation turns — Navigate to the previous/next user prompt or assistant response using keyboard shortcuts (e.g., Ctrl+↑ / Ctrl+↓ or similar)
2. Visual session markers — Display clear visual separators between conversation turns
3. Optional: Conversation index — A command like /sessions or /turns that lists all conversation turns in the current session with the ability to jump to a specific one

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

• Long debugging sessions with multiple iterations
• Code reviews with extensive output
• Any session where Claude outputs a lot of content and the user needs to scroll back to reference earlier parts of the conversation

Additional Context

Current Workarounds

• /clear or /compact to reset context (loses history)
• Terminal search (Cmd+F) to find specific text
• /history to view past sessions (but not navigate within current session)

These don't solve the core navigation problem within an active session.

Environment

• Claude Code running in various terminals (Warp, iTerm2, etc.)
• Issue is terminal-agnostic since it's a limitation of Claude Code's internal UI

---
Feel free to edit as needed!