@m455 well, if you port forward as part of your SSH connection, you can always use chrome on a different machine even when the main program is on the vbox.
vscode on the other hand, probably not so much, so you'd need to stick to editing with vim.
@technomancy @m455 if you suuuper needed to use those tools, both are luckily some of the most forwardable over ssh between vscode's remote ssh windows (kinda like emacs tramp with lsp/dap) and the classic ssh -D socks proxy for browsers (though chrome annoyingly needs an extension to use those easily, unlike firefox)
it makes both only really a matter of having a good ~/.ssh/config
those aren't quiiite the same aesthetic as using a terminal-only setup to do the things you need though
