[bug / critical / data-loss] Accidental session deletion: Ctrl+Shift+Backspace deletes active session without confirmation

[PVLPM]

Description

Bug Summary

Pressing Ctrl+Shift+Backspace (easily triggered when using Ctrl+Backspace to delete words) immediately and permanently deletes the active session, including any ongoing implementation work. No confirmation dialog appears, and there is no way to recover the deleted session.

Expected Behavior

1. The keybind should either not be assigned by default or should be configurable in settings
2. If assigned, deleting a session should require explicit user confirmation
3. The confirmation dialog should prevent accidental acceptance — the primary action button should be disabled for a minimum of 3 seconds
4. Alternative: Instead of deleting, the session could be paused/stopped, allowing the user to resume

Impact

• Critical: Permanent data loss with no recovery path
• High friction: Common keyboard shortcut collision makes accidental deletion likely
• No safety net: No trash/recovery mechanism exists

Proposed Solution

1. Remove the Ctrl+Shift+Backspace keybind from the default configuration, or make it explicitly optional in settings
2. Add a confirmation modal before session deletion with:
   • Clear warning text explaining the action is irreversible
   • A 3-second delay before the "Delete" button becomes active (configurable in settings)
3. Consider implementing a soft-delete or session history to enable recovery within the current session

Plugins

oh-my-openagent (not related to the bug)

OpenCode version

OpenCode Desktop 1.3.17 (happened on previous versions as well)

Steps to reproduce

1. Open OpenCode Desktop
2. Start an implementation task (any task that involves multiple turns)
3. Begin typing a prompt or code
4. While typing, press Ctrl+Backspace to delete the previous word
5. Accidentally also press Shift (creating Ctrl+Shift+Backspace)
6. Observe: The entire session is immediately deleted with no confirmation dialog
7. Attempt to recover the session — no recovery option exists

Additional Observation

After deletion, the session appears gone from the UI but agents/tasks spawned within it may still be executing. This creates:

• Resource leakage (background processes continue consuming resources)
• Impossible UX state (work in progress with no interface)
• Confusion (user cannot determine if work was completed or lost)

Screenshot and/or share link

No response

Operating System

Windows 11

Terminal

No response

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• [UX] Ctrl+D to delete session too easily exits the app #13950: Same UX concern — a session-deletion keybind triggers too easily without confirmation (Ctrl+D in that case, Ctrl+Shift+Backspace here). Both request a confirmation dialog and safer default keybind behavior.

For keybind-related issues, please also check our pinned keybinds documentation: #4997

[PVLPM]

This issue might be a duplicate of existing issues. Please check:

• [UX] Ctrl+D to delete session too easily exits the app #13950: Same UX concern — a session-deletion keybind triggers too easily without confirmation (Ctrl+D in that case, Ctrl+Shift+Backspace here). Both request a confirmation dialog and safer default keybind behavior.

For keybind-related issues, please also check our pinned keybinds documentation: #4997

No, it is not exactly the same, but UX inconsistency seems close.