VSCode: Input text lost when switching between chats

Resolved 💬 4 comments Opened Mar 15, 2026 by istulenkov Closed Apr 22, 2026

Problem

When using Claude Code in the VSCode extension, if you type text in the input field but don't send it, then switch to a new chat and come back — the typed text is gone. There is no draft saving or persistence of unsent input across chat switches.

Expected behavior

The unsent input text should be preserved when switching between chats (tabs/conversations) and restored when returning to the original chat. This is standard behavior in most chat applications (Slack, Telegram, Discord, etc.).

Steps to reproduce

  1. Open Claude Code panel in VSCode
  2. Start typing a message in the input field (do not send)
  3. Switch to a new chat / conversation
  4. Switch back to the original chat
  5. Result: The input field is empty — typed text is lost

Impact

This is frustrating when composing longer prompts or when accidentally switching chats. Users lose their work-in-progress input with no way to recover it.

Suggested solution

Save draft input per chat/conversation (e.g., in extension state or memory) and restore it when the user returns to that chat.

View original on GitHub ↗

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