Remote session/task persistence: Detach, preserve, and reattach all active tasks, terminals, and extension processes in VS Code Remote
<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ --> <!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ --> <!-- Please search existing issues to avoid creating duplicates. --> <!-- Describe the feature you'd like. --> ## Feature Request: Universal Remote Session Persistence & Reattachment When using VS Code Remote connections (SSH, WSL, Containers, etc.), I would like the ability to completely detach/disconnect my local VS Code client while preserving the entire remote session—**not only a Copilot agent or a single task, but all running content in the workspace**. This would include: - All running integrated terminal processes - All ongoing tasks (e.g., build, watch, test, custom tasks) - Background/interactive processes started by extensions - Debugger sessions and other live connections After disconnecting (e.g., closing VS Code or losing network for a long period), when I reconnect to the same remote workspace, I would like VS Code to automatically restore all these elements. This means: - ALL previously running terminals and tasks should remain alive in the background and be reattached, preserving their history and state - Output/logs from before the disconnect should remain available and reviewable - Extension-contributed terminal panels/processes/background work (if possible) - Sessions like debugging, ports, tunnels, etc. should resume if possible - UI/interaction state (open editors, layout, etc.) restored as far a
Posted by Diluka on Jun 5, 2026, 3:55 AM
Tags
Related issues
- I've been thinking about this question a lot recently and have asked my friends for their opinions.
- > There's really no reason console games of that era needed, or even could benefit from 6 cores First: One problem of the PS3 was that i...
- Not only Eddie, their account control panels and site in general look like something from the 90s, and it seriously hampers their business.
- Signal don't want you to build 3rd party clients and integrations, they are another fully centralised product meant to capture and lock u...
- The page keeps crashing for me.
- Server-side pagination to make ArgoCD UI a rocket
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
ux (Network)
I've been thinking about this question a lot recently and have asked my friends for their opinions.
> There's really no reason console games of that era needed, or even could benefit from 6 cores First: One problem of the PS3 was that i...
Remote session/task persistence: Detach, preserve, and reattach all active tasks, terminals, and extension processes in VS Code Remote
Not only Eddie, their account control panels and site in general look like something from the 90s, and it seriously hampers their business.
Signal don't want you to build 3rd party clients and integrations, they are another fully centralised product meant to capture and lock u...
The page keeps crashing for me.
Server-side pagination to make ArgoCD UI a rocket
Remote session/task persistence: Detach, preserve, and reattach all active tasks, terminals, and extension processes in VS Code Remote
<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ --> <!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ --> <!-- Please search existing issues to avoid creating duplicates. --> <!-- Describe the feature you'd like. --> ## Feature Request: Universal Remote Session Persistence & Reattachment When using VS Code Remote connections (SSH, WSL, Containers, etc.), I would like the ability to completely detach/disconnect my local VS Code client while preserving the entire remote session—**not only a Copilot agent or a single task, but all running content in the workspace**. This would include: - All running integrated terminal processes - All ongoing tasks (e.g., build, watch, test, custom tasks) - Background/interactive processes started by extensions - Debugger sessions and other live connections After disconnecting (e.g., closing VS Code or losing network for a long period), when I reconnect to the same remote workspace, I would like VS Code to automatically restore all these elements. This means: - ALL previously running terminals and tasks should remain alive in the background and be reattached, preserving their history and state - Output/logs from before the disconnect should remain available and reviewable - Extension-contributed terminal panels/processes/background work (if possible) - Sessions like debugging, ports, tunnels, etc. should resume if possible - UI/interaction state (open editors, layout, etc.) restored as far a
Comments (0)
No comments yet. Start the discussion.