Devvm.dev: One VM for every project

Re:Devvm.dev: One VM for every project by photonios on Friday November 06, 2026 @04:48PM (#50398964)

I keep seeing projects like this pop up and they never nail it.

I need isolation, but I also need to give my agents secure access to internal package registries, logs, internal infra, designs, emulators, docs etc. At a large company, work can span dozens of repositories. My agent needs browsers to drive etc. And on top of that, I need dozens of these.

I built this at work. Engineers use krunkit VMs with proper memory ballooning, GPU acceleration. Retina RDP, credential injecting proxy for secure MCP servers, Cloudflare One and SSH tunnels, secure remote support etc.

This seems like a fun toy, but nothing close to what you need as an engineer in a corporate environment.

[ Parent | on HN ]

Re:Devvm.dev: One VM for every project by toyg on Friday November 06, 2026 @05:44PM (#50399497)

I think this sort of thing can still be useful to smaller shops. I have a hobby project in this vein, and I know it will never make it big, but it's still a fun hamster wheel.

[ Parent | on HN ]

Re:Devvm.dev: One VM for every project by rahimnathwani on Saturday November 07, 2026 @02:12AM (#50402362)

Are you developing Mac or iOS apps? Or is there another reason to have your coding agents run on MacOS?

[ Parent | on HN ]

Re:Devvm.dev: One VM for every project by nilleb on Saturday November 07, 2026 @02:46AM (#50402527)

Hello! I am really interested in your advice on https://GitHub.com/nillebco/varda

Because it's not just VMs, but a lot more around credentials injection, egress, volumes, agents selection policies. I am quite sure also the memory ballooning and GPU acceleration can be fine tuned.

In advance, thank you very much for your feedback!

[ Parent | on HN ]

Re:Devvm.dev: One VM for every project by photonios on Saturday November 07, 2026 @09:30AM (#50404857)

You got the right base, but it seems centered around single project/ticket work.

A lot of work me and my fellow engineers do spans weeks if not months, tens of code bases, tickets etc. Having longer lived sandboxes that cover N repos in which you can just let experiments exist, together with plans etc is a superpower.

[ Parent | on HN ]

Re:Devvm.dev: One VM for every project by nilleb on Sunday November 08, 2026 @03:55AM (#50411529)

Ah, I see! That's where I adopted a repo of repos approach https://raffertyuy.com/raztype/repo-of-repos-pattern/

Eventually I can prepare a sandbox per repository or per "whole project" as we call it.

It's fascinating as a problem - thanks for sharing!!!

[ Parent | on HN ]

Re:Devvm.dev: One VM for every project by wcoenen on Saturday November 07, 2026 @06:18AM (#50403545)

What is "Retina RDP"?

[ Parent | on HN ]

Re:Devvm.dev: One VM for every project by jonathanlydall on Saturday November 07, 2026 @08:09AM (#50404267)

It’s an option on the Windows app (Microsoft’s own RDP client), connects at full retina resolution but while having the host being set to 200% UI scale, so that you get the crisp text and UI.

[ Parent | on HN ]

Re:Devvm.dev: One VM for every project by photonios on Saturday November 07, 2026 @09:09AM (#50404678)

Yeap. That's it.

[ Parent | on HN ]

Re:Devvm.dev: One VM for every project by appstorelottery on Saturday November 07, 2026 @09:33AM (#50404870)

I'm constantly blown away by the power that LLM's are giving us. I've been working on a self-improving agent for around six months - and over the past few weeks I used VM's to isolate the governance layer. Virtualization is - to me - a completely black art, and yet with the deepseek flash 4.1 model the agent itself has built it's own virtual machine launcher/manager on OSX and even managed to port it to windows (windows Home has very limited VM support). For all the negative excitement about LLM's, I'm just amazed how our capabilities are being extended as engineers and what's possible.

[ Parent | on HN ]