You should be able to setup WSLg then run the Linux Codium in WSL. Regular VS Code will work that way, it just gives a little “hey, you know you could use remote WSL right?” message then keeps chugging.
Yep. I have it running with an Intel integrated graphics chips. There was a driver I had to download direct from Intel instead of HP, though.
https://github.com/microsoft/wslg
https://learn.microsoft.com/en-us/windows/wsl/tutorials/gui-apps
The benefit of the WSL (and SSH and Docker) integration is that you still run the native version of VS Code for your OS, and just the server portion of VS Code runs on the ‘remote’ server. Running the whole of VS Code (or Codium or whatever) in WSL probably works but there’ll be little annoying things with it since it’s not running natively, for example you can’t drag files from Explorer into it, can’t have a PowerShell terminal open alongside a WSL one, etc.
I don’t think the SSH integration is locked down, so I wonder if you could install OpenSSHd in WSL and connect vis SSH.
can’t have a PowerShell terminal open alongside a WSL one, etc.
How are you getting this to work? According to only the default profile can be opened with the local integrated terminal. The default profile seems to be bash, so that fails. But I wouldn’t want set my default profile to PowerShell when I’m in WSL.
