[FEATURE] VSCode: Preserve user input when a question/plan-approval prompt appears

Resolved 💬 5 comments Opened Mar 13, 2026 by shaharsha Closed Apr 10, 2026

Preflight Checklist

  • [x] I've searched existing issues for duplicates
  • [x] I've thought about whether this is broadly useful or specific to my use case

Problem Statement

In the VSCode extension, when Claude Code presents a question (like plan approval or AskUserQuestion) while the user is typing in the main input, the text the user was composing disappears.

The user is then forced to:

  1. Close/dismiss the question
  2. Wait for Claude to continue
  3. Re-type their message from scratch

This is frustrating because the user had something to say (e.g., a correction, additional context, or a redirect) and lost it.

Proposed Solution

  1. Never discard text in the main input — When a question/plan-approval prompt appears in the VSCode extension, the main input field should preserve whatever the user was typing.
  1. Allow sending a message while a question is open — If the user has text in the main input and hits send while a question prompt is visible, it should:
  • Dismiss/close the question
  • Send the user's message as a normal message
  • Claude reads and responds to that message instead of waiting for the question answer

This way the main input is always the primary interaction channel, and questions/prompts are an overlay that doesn't interrupt the user's flow.

Alternative Solutions

  • At minimum, just preserve the input text when a question appears (don't clear it). The user can then close the question and send their message normally.
  • Show the question inline in the chat rather than as a separate prompt that takes over input focus.

Priority

Medium — this is a workflow interruption that happens frequently when users want to redirect Claude mid-task.

Feature Category

IDE Integration (VSCode extension)

Use Case Example

Before:

  1. Claude is planning in the VSCode extension. User starts typing "actually, don't change the auth module, just fix the..."
  2. Claude finishes and shows plan approval prompt
  3. User's half-written message vanishes
  4. User dismisses the prompt, Claude continues, user has to re-type their message

After:

  1. Claude is planning in the VSCode extension. User starts typing "actually, don't change the auth module, just fix the..."
  2. Claude finishes and shows plan approval prompt
  3. User's text is still in the input. User finishes typing and hits send
  4. The plan prompt is auto-dismissed, and Claude reads the user's message as a redirect

Additional Context

This applies to any scenario in the VSCode extension where Claude presents a question (AskUserQuestion, ExitPlanMode approval, etc.) while the user is mid-composition. The core principle: never discard user input.

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗