Unsaved work lost after accidental VS Code window close – no recovery prompt

Resolved πŸ’¬ 2 comments Opened Jan 18, 2026 by Rashidzada Closed Jan 18, 2026

Hello Maintainers πŸ‘‹,

I would like to report a usability issue that can lead to loss of work, especially during long development sessions.

❗ Problem Description

Sometimes I spend a long time thinking or planning, without actively typing code for a while. During this time, the editor remains open and everything seems fine.

However, if the VS Code window is accidentally closed (by mistake or system interruption), all unsaved work is lost, and there is no way to restore or continue from where I left off.

This can be frustrating, particularly when:

  • You are mentally planning or reviewing code
  • You step away briefly
  • The window is closed unintentionally
  • No auto-save or recovery prompt appears

πŸ” Expected Behavior

One or more of the following would be very helpful:

  • A warning or confirmation dialog before closing when unsaved context exists
  • Better automatic session recovery
  • Optional background auto-save / draft snapshot
  • Ability to resume work context even after accidental closure

🎯 Why This Matters

Accidental window closures are common, and losing work β€” even thinking-stage or partially written content β€” can negatively impact productivity and learning, especially for students and developers.

πŸ™ Request

Please consider improving recovery or warning mechanisms to help users continue their work safely after unexpected closures.

Thank you for your time and for the amazing work you do on this project.

Best regards,
Rashid Zada

---

🏷️ Optional Labels (if available)

  • bug
  • usability
  • data-loss
  • enhancement

View original on GitHub β†—

This issue has 2 comments on GitHub. Read the full discussion on GitHub β†—