I used this on a few test machines at one point. It has an optional web interface that is fairly minimal, so you can install it on a remote box, configure HTTPS

I used this on a few test machines at one point. It has an optional web interface that is fairly minimal, so you can install it on a remote box, configure HTTPS access, and point your browser to the IP of the box and get a minimal X session (displayed in your browser) with VSCode and a terminal running on the physical resources of the box rather than your client PC. Useful for things like developing remotely using an underpowered Chromebook or sharing environments (with saved state) with other developers. For example, if you were developing a web app, you could create a dev machine in DigitalOcean or Linode and run both the dev environment (web server, database) and the dev tooling (IDE) in a self-contained instance that gets automatic backups and is available for your colleagues to connect to. I've also heard of it being used as a method to access graphical environments in containers on a localhost. If I remember correctly, it was thought to offer enhanced security by isolating the container from the host's X11 while still allowing the container to display on the host.