This is great news! I've been doing a similar setup to this for years with Jupyter Notebooks. However, if I get to make a teeny tiny feature request (Nat, if y

This is great news! I've been doing a similar setup to this for years with Jupyter Notebooks. However, if I get to make a teeny tiny feature request (Nat, if you're out there...) it would be about this: > What if I don’t want to develop in a browser? > If you prefer, you can open a codespace in GitHub and then connect to it in VS Code. I really kinda wish I could do the oposite, kinda like how Google Drive's Colaboratory (essentially Jupyter Notebooks on Drive[0]) do: I would launch a CodeSpace on GitHub, and it would handle all of the UI and automation bits, but I would keep the "environment" hosted somewhere else (i.e. a Docker container exposing a CodeSpace agent/headless VSCode through localhost:8080 that my browser talks to) All of the gears seem to be already in-place for this to be possible given: > How is Codespaces different from VS Code? > Codespaces sets up a cloud-hosted, containerized, and customizable VS Code environment. After set up, you can connect to a codespace through the browser or through VS Code. The reasons for this are several: - I bought a beefy computer for a reason, and want to use it. I don't want to pay boatloads of money to Azure to have equal firepower to what I currently have idling; - From an SRE perspective, your code, several times needs to be "inside" your infrastructure to run properly (because of roles, latency, you might be running Data Loss Prevention solutions, what have you), and this allows me to point the CodeSpace to a dedicated instance I have running inside a VPN on my own infrastructure; - There are more, but I don't want to make this too long and I'm failing to recall some of them. So to sum it up: I think this is a potentially great feature, as long as it doesn't come coupled with the need to buy Azure instance time. This would (and I'm asserting this purely from my own gut, without a shred of evidence) probably lead to increased adoption for this feature, and as a corollary lead to selling more Azure instance time for those who do not want the hassle, without crippling those who actually need to keep some things "in-house". [0] https://colab.research.google.com https://colab.research.google.com