It may support a dotfile repo in your GitHub account like Codespaces does, but I've never setup such a repo so I can't test. I do use VS Code's Settings Sync w

It may support a dotfile repo in your GitHub account like Codespaces does, but I've never setup such a repo so I can't test. I do use VS Code's Settings Sync with my GitHub Account. I was surprised it wasn't on by default, but the menu steps to turn it on on the GitHub Dev site were very quick (didn't have to relogin, it did know which account I was already logged in under on the main GitHub site). It synced quickly with my Settings. It even pulled in some of my extensions, the most noticeable one being a custom color theme. Other than the obvious limitation to extensions that support "Virtual Workspaces", I'm not exactly sure why the subset of supported extensions is what it is. But it's neat that some of them show up. ("Virtual Workspaces" has been an interesting project to follow in VS Code's release notes and lets you do something similar to GitHub.Dev in your locally installed VS Code as well: open a remote GitHub repo you've never cloned/downloaded.) (I have a Vim emulation extension to VSCode in my Settings Sync, but currently disabled for reasons in that I haven't used it in a while. It shows up as supported in the Extensions list on GitHub.Dev, which is interesting. Might try reenabling it and seeing how it works these days.) After turning on Settings Sync once in GitHub.Dev it seems to remember it on subsequent visits (even from different repositories). Pretty neat. It looks like GitHub.Dev only supports VS Code. If you want to provision an environment how you want it setup you could use Codespaces the next step up "big brother" tool to this GitHub.Dev site. (That gives you the ability to specify a full Docker container the Codespace runs in, including things like port forwarding SSH to allow working with vim, which GitHub mentioned doing in their recent Engineering blog about moving to Codespaces.)