claude-code - 💡(How to fix) Fix Delete session button has no confirmation and sits 1px from edit button in VS Code session list

Summary

In the VS Code extension's active sessions list, each session row has a pencil (edit) icon and a trash can (delete) icon placed directly adjacent to each other. Clicking approximately one pixel to the right of the edit icon hits the delete icon instead, and the session is deleted immediately with no confirmation prompt and no undo.

Steps to reproduce

1. Open the Claude Code extension in VS Code.
2. View the list of active/recent sessions.
3. Hover over a session row to reveal the edit (pencil) and delete (trash can) icons.
4. Click on or very near the edit icon — slightly off-target to the right.
5. The session is permanently deleted with no warning.

Expected behavior

Either:

• A confirmation prompt before deletion, or
• An undo toast with a several-second grace period after deletion, or
• Visibly greater spacing between the edit and delete icons (and ideally destructive-styled treatment on the delete button — e.g., red on hover).

Actual behavior

The session is deleted immediately and irreversibly, with no confirmation, no undo, and no visual distinction warning that the trash icon is destructive.

Why this matters

Placing a destructive, irreversible action one pixel from a safe, frequently-used action is a well-known UX anti-pattern. The 2018 Hawaii false-missile-alert incident is the canonical example — the "test alert" and "real alert" buttons were adjacent in a dropdown with no confirmation, and an operator picked the wrong one. The consequences here are far smaller, but the design failure is the same shape: safe and destructive actions are visually and spatially indistinguishable, and the destructive one has no guardrail.

Environment

• Claude Code VS Code extension: 2.1.165
• OS: Windows 10 (10.0.19045) x64
• VS Code version: 1.123.0 (system setup), commit 6a44c352bd24569c417e530095901b649960f9f8
• Confirmed reproducing on these versions as of 2026-06-05.

Suggested fix priority

This feels like low-effort, high-impact: a confirmation modal or an undo toast would eliminate the failure mode entirely.