[FEATURE] Peek mode — ask a question without consuming context

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 working in a long session, I often want to ask Claude a quick side question — "what does this function do?", "what's the syntax for X?", "remind me what approach we ruled out for Y" — without that exchange permanently occupying my context window.

Currently, the only way to do this is to manually /rewind after every throwaway question (double-tap Esc → select the message → choose "Restore conversation only"). This works but is tedious, easy to forget, and creates fork clutter when done repeatedly.

The result is that I either:

1. Waste context on throwaway Q&A that accumulates over a session
2. Go through a multi-step rewind flow every time, breaking my focus
3. Open a separate terminal with a fresh claude session just to ask a quick question

Proposed Solution

A /peek command that sends a query, displays the response, and then automatically rewinds the conversation state to before the question was asked. The response is visible to the user but does not persist in context.

/peek where does this codebase handle image resampling again?

Claude answers the question as normal, the user reads it, and then the conversation state rolls back — as if the exchange never happened. No manual rewind needed.

Behavior should match the existing "Restore conversation only" rewind option, just triggered automatically after the response completes.

Alternative Solutions

• Manual /rewind after each question: Works, but requires multiple steps every time and is easy to forget. Also creates conversation forks that clutter the session history (see #9279).
• Opening a second claude session: Loses all project context, so Claude can't answer questions about the current codebase or conversation state.
• Using a subagent via Task tool: Overkill for a quick question, and subagents don't inherit full conversation context by default.

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

Scenario: Quick syntax check mid-task

I'm 30 messages into a refactoring session. I can't remember the exact signature for a library function. I want to ask without bloating my context:

/peek what are the arguments to asyncio.create_task?

Claude answers inline. Context stays clean. I keep working.

Scenario: "What did we decide?" without double-counting

Deep in a session, I forget a decision we made earlier. I want to ask Claude to remind me, but I don't want the reminder Q&A eating context when the original decision is already in history:

/peek which caching strategy did we settle on earlier?

Scenario: Exploring a tangent without committing

I'm curious whether a different approach might work but don't want to derail the session if it's a dead end:

/peek would it be simpler to use a decorator pattern here instead?

I read the answer, decide it's not worth pursuing, and my context is untouched.

Additional Context

_No response_