open-remote-ssh

I recommend moving to VSCodium and using this extension: https://github.com/jeanp413/open-remote-ssh and run vscode-server inside a VM or container

I am quite keen on this as well, I have been trying to move all my active development to happen inside a container, including the harnesses. This, of course, makes it very hard to run GUI harnesses. I prefer CLI, but it would be neat to be able to better isolate gui-based harnesses as well. I have been using VSCodium with https://github.com/jeanp413/open-remote-ssh so (most of) the IDE also runs inside the container. I have been trying to get everything inside the container, including the projects I work on, the IDE, the harness, the dependencies, etc. Both for security and for portability so I can have the same setup in both my work and home computers. One thing I haven't been able to do is limit the blast radius of is git, github ssh keys give blanket access to all repos tied to my profile and ATM I set up the github SSH key inside the

I have been using VSCodium (chromium-like version of VSCode) with this extension: https://github.com/jeanp413/open-remote-ssh I run the editor (and its extensions), my projects and any agent harnesses from inside a container and use that extension to get an editor. This is mostly to protect my credentials and data from malicious extensions/dependencies/rogue-agents, bu it also lets me quickly port my dev environment to any machine (I use linux at home and macos at work). Just install podman, install VSCodium, add the SSH extension, build image, add my utility shellscripts (to quickly get in and out of the container in a shell) and done. Apparently Microsoft keep some VSCode APIs proprietary so only its own extensions can use it (allegedly for security reasons), which is why this specific extension only works in VSCodium. I wonder if it is

I don't find it that opaque. Even without trying to deobfuscate the obfuscated source code which Microsoft ships (I haven't tried but it wouldn't be hard) a lot of details about how it works become obvious just by reading its logs. Of course, it is a pity Microsoft doesn't open source it. But there are some well-maintained open source alternatives, e.g. https://github.com/jeanp413/open-remote-ssh and https://github.com/F1yingWhite/fast-remote-ssh (I haven't got around to giving either of them a go–but I really should.)