Allow opening of local workspaces when connected to a remote

[jonah-iden]

Feature Description:

Currently when connected to a dev-container or remote system the only entry in Open Recent Workspaces... is the current folder inside of the remote. It would be great if one could still see and open other recent workspaces from the recentworkspaces.json from the local system.

This would also require some conceptual work on how to handle different workspaces inside of the remote vs workspaces located on the local system.
But in general it would probably be best if the WorkspaceServer was a local proxy. This would then require some contribution or changes to the workspaceService to actually open workspaces that its FileSystemProvider is not able to reach.

Above that it would be great if when closing a connection to a dev container, to then return to the original workspace.

[sgraband]

The same is may be relevant for Open File and Open Folder, there you can also only see the files on the remote. VSCode offers a Show Local Files button in the dialog, which brings you to your local files.

[jonah-iden]

thanks for the info!

[jonah-iden]

Above that it would be great if when closing a connection to a dev container, to then return to the original workspace.

Regarding that, i just saw vscode does it the same way we are doing it right now. Meaning going back to an empty workspace.
Do we really want different behaviour here?

[msujew]

Related issue: #14080