Feature: Ctrl+Q — Ask a question mid-generation without interrupting
Resolved 💬 2 comments Opened Mar 3, 2026 by khoraj23 Closed Mar 31, 2026
Problem
When Claude Code is running a long task, there's no way to ask "what's going on?" without interrupting the generation. Pressing Escape or typing anything stops the current work, and resuming has a latency cost as Claude re-processes context.
Users don't plan ahead to be confused — the need to check in arises during the work, not before it.
Proposed Solution
A hotkey (e.g. Ctrl+Q) that lets you ask a quick question about the current task without stopping generation. Similar to how Ctrl+T (task list) and Ctrl+O (verbose mode) already work mid-generation at the UI level.
How it would work
- User presses
Ctrl+Qwhile Claude is generating — caught at the UI level, generation continues - Conversation state is snapshotted from memory (it's already in the process)
- An input field appears (overlay, panel, inline — whatever fits the terminal UX)
- User types their question: "what are you doing?" / "what was that file change?" / "why did you pick that approach?"
- A background API call is made to a small, fast model (e.g. Haiku) with the snapshot + question
- Response is shown in the overlay
- Main generation never stops
Why this works
Ctrl+TandCtrl+Oalready prove that mid-generation UI interactions are possible- The only difference is that
Ctrl+Qneeds a background API call — standard async, runs on a separate thread - The snapshot is read-only, so there's no concurrency risk with the main generation
- Uses a small/fast model so responses are near-instant and cheap
Alternatives Considered
- Background subagents: Requires planning ahead ("run this in the background"). Doesn't solve the reactive "yo, what's happening?" use case.
- Second terminal: Conversation state is in-memory only, so a second session can see file changes but not intent/reasoning. Also clunky UX.
- Agent Teams: Peers working on separate tasks, not an observer watching a worker.
- Verbose mode (Ctrl+O): Shows tool calls but doesn't let you ask questions or get explanations.
The Pitch
Let me ask a question about what's happening without stopping what's happening.
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗