VSCode: /clear should not be top autocomplete suggestion when typing /new

Resolved 💬 1 comment Opened May 27, 2026 by Samuel-Viscoma Closed Jun 28, 2026

Problem

When typing /new in the VSCode extension chat input, the slash command autocomplete menu shows /clear as the first highlighted suggestion. Pressing Enter immediately clears the entire conversation — with no confirmation dialog.

This is a destructive action triggered by a non-destructive intent. The user wants to start a new conversation but accidentally wipes the current one.

Steps to Reproduce

  1. Open Claude Code in VSCode extension
  2. Type /new in the chat input
  3. The autocomplete dropdown appears with /clear highlighted as the first suggestion
  4. Press Enter (expecting "New conversation")
  5. Result: Entire conversation is cleared without confirmation

Expected Behavior

Either:

  • /clear should not rank as the top suggestion when typing /new (the input doesn't even match "clear")
  • /clear (and "Clear conversation") should require a confirmation dialog before executing, since it's a destructive, irreversible action
  • "New conversation" should rank higher than "/clear" when the input is /new

Ideally both: better ranking and a confirmation prompt for destructive commands.

Screenshot

The autocomplete menu when typing /new:

| Position | Suggestion |
|----------|-----------|
| 1 (highlighted) | /clear |
| 2 | /init |
| 3 | /skill-creator |
| ... | ... |
| Context section | New conversation |
| Context section | Clear conversation |

Environment

  • Claude Code VSCode Extension
  • Windows 11 Pro 25H2
  • Claude Code with multiple custom skills registered

Impact

Loss of entire conversation context (potentially hours of work) with a single accidental keypress. No undo, no confirmation.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗