claude-code - 💡(How to fix) Fix [Feature Request] Quick Entry should support follow-up messages in the popup without opening the main window [1 participants]

Preflight Checklist

• I have searched existing requests and this specific behavior hasn't been requested yet (related: #10535, but that issue focuses on the main window auto-opening, not on continuing the conversation inside Quick Entry)
• This is a single feature request (not multiple features)

Problem Statement

On macOS, Claude Desktop's Quick Entry (Opt+Space) currently works as a one-shot input box: you type a message, hit send, and the conversation immediately moves to the main Claude Desktop window. There is no way to ask a follow-up question, read the reply, and keep the back-and-forth inside the Quick Entry popup itself.

This is a significant UX gap compared to ChatGPT's equivalent feature (Opt+Space on macOS), where the popup acts as a persistent mini chat window: you can send a message, receive the response inline, send a follow-up, and continue the entire conversation without ever switching to the full app.

Current Behavior

1. User presses Opt+Space anywhere in macOS
2. Quick Entry popup appears
3. User types a message and sends it
4. The conversation immediately moves to the main Claude Desktop window — user is forced to context-switch to read the response and continue

Expected Behavior

1. User presses Opt+Space anywhere in macOS
2. Quick Entry popup appears
3. User types a message and sends it
4. The response is rendered inside the popup, which expands into a compact chat view
5. User can send follow-up messages, receive responses, and continue the conversation entirely within the popup
6. Optional: a button/shortcut to "expand to main window" if the user wants to move the conversation over (e.g. when switching to file uploads, artifacts, or long-form work)

Use Case

As a developer working across VS Code, terminal, and browser (42 Ecole curriculum, C/Python projects, research reading), I frequently need Claude for:

• Quick clarifications on error messages
• Short back-and-forth debugging ("why does this happen?" → "what if I try X?" → "will that break Y?")
• Definition lookups with one or two follow-ups

For these, the main Claude Desktop window is overkill and disrupts flow. The whole point of Quick Entry is ambient access — but ambient access breaks the moment a single reply forces a full window switch.

ChatGPT's popup handles this exact use case well, and it's a concrete reason users cite for staying on ChatGPT for quick-question workflows.

Proposed Design Notes

• Keep the popup lightweight: chat thread view, input box, minimal chrome
• Conversation persists as long as the popup is open; closing the popup either ends the chat or saves it to history (configurable)
• Optional "pop out to main window" button for when the conversation grows
• Existing features (attach application window, voice dictation) should continue to work
• Setting to toggle this behavior on/off so users who prefer the current one-shot flow keep it

Related Issues

• #10535 — Quick entry auto-opening main window (related but distinct; fixing that alone doesn't give you a continuous conversation, just hides the main window)
• #22420 — Windows taskbar quick entry behavior (related platform parity issue)

Environment

• Platform: macOS (Darwin 25.3.0)
• Claude Desktop version: 1.3109.0
• Quick Entry shortcut: Opt+Space (default)

Impact

This is the single biggest friction point I hit when using Claude Desktop as a daily driver vs. ChatGPT. Fixing it would make Quick Entry genuinely replace the need to switch apps for short interactions, which is the feature's stated purpose.