Secondary window loses connection when the parent window is closed

[AugustoAmaral]

🏷️ Discussion Type

Bug

Body

Hi everyone,
I'm experiencing an issue with the GitHub Codespaces extension on VS Code Desktop regarding session persistence across multiple windows.

The Issue:
When I have a Codespace open and open a subfolder in a new window using the terminal (e.g., cd ./some_dir && code .), the new window connects successfully. However, if I close the original VS Code window, the second one immediately loses its connection. I then have to manually trigger a reconnection or reopen the window.

Why this is a problem:
It seems the second window's connection is tethered to the first one. Closing the "parent" window kills the tunnel/process for the "child" window.

Steps to Reproduce:

1. Connect to a Codespace in VS Code Desktop.
2. Open a subfolder in a new window via the integrated terminal: code . (or code ./path).
3. Close the first (original) VS Code window.
4. The second window enters a "Disconnected" state.

Suggested Improvement (UX):
If a "handover" of the connection between windows isn't technically feasible right now, it would be great if VS Code could at least:

• Warn the user that closing the current window will terminate sessions in other linked windows.
• Automatically promote the second window to "primary" to maintain the connection active.

Environment:

• Version: 1.119.0 (Universal)
• Commit: 8b640eef5a6c6089c029249d48efa5c99adf7d51
• Date: 2026-05-05T11:23:50-07:00
• Electron: 39.8.8
• ElectronBuildId: 13870025
• Chromium: 142.0.7444.265
• Node.js: 22.22.1
• V8: 14.2.231.22-electron.0
• OS: Darwin arm64 25.5.0
• github.codespaces version: 1.18.13

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐