I have been looking at https://github.com/Kruemelkatze/vscode-dashboard which seems to have stalled and https://github.com/DanielNoveo/vscode-dashboard who has not turned on 'issues' and does not respond to attempts to contact.
I just found this project and it seems in more active development? So considering swapping...
The following feature are also missing from the other projects but they do have a nice friendly UI that you may want to take a look at. The fact that there seems to be little progress on them makes me think being involved with this project will be more useful.
Suggestion 1:
Though this is about WSL, it would probably apply to any remote, So I would suggest perhaps abstract it in the UI. Remove (or hide) explicit SSH and PROMODE. That way it would be the same UI for or Github Codespaces or Azure or any oither future remote that somebody invents. After all, all remotes following the same syntax vscode-remote://<handler>+<authority>/<path>.
ref: WSL in VSCODE https://code.visualstudio.com/docs/remote/wsl for url format.
Suggestion 2:
A UI (as suggestion 1) with a means to add remote <username> as the Windows %USERNAME% may not be the same as the WSL ${USER}, though I guess the former would be the default entry.
Suggestion 3:
Desired: means to select remote (or local) existing project *
Desired: Means to add current project or proect from remote explorer or perhaps the recent history - See #6
Additional?: Entering a remote non-existent or empty folder will create a new project: (Dialog Y/N?) or would it just say does not exist and bork.
* And, if the APIs allow this, offer an existing project from the list. Similar to Remote Explorer (ms-vscode.remote-explorer)
NOTE I tried URL vscode-remote://wsl+default/home/\<username\>/work/project/
and that seemed to work for opening an existing project.
Notes:
- I think the page linked by MS from https://github.com/Microsoft/vscode-remote-release is wrong and swaps opening a file or a project folder instructions. Which may mean the trailing slash is important. Not sure....
- It seems the $HOST and $HOSTNAME env vars in WSL are incorrect and wsl.localhost is a made up name only known to Windows. so something to be careful of...