devvm
One VM for every project: an isolated sandbox with your toolchain, ready in seconds, where your coding agent works without touching your machine.
devvm gives every project folder a VM of its own: an isolated sandbox with the project's toolchain, ready for you or a coding agent to start coding. You open a terminal, go to a project folder and run devvm; it shows what the new VM gets, then opens a shell inside it at the same path, with a (devvm) prompt. Run devvm in the folder again and it opens the same VM. It exists because coding agents are powerful and careless, and running one on your machine means it can reach your SSH keys, your tokens and your other projects. In devvm the VM mounts only the project folder, new VMs get an allowlist network tier by default so they only reach the hosts you allow, and your secrets stay on your machine. With --clone the VM gets a clone of its own, so nothing it does can touch your working tree until you fetch it. It is built to be fast and agent-ready. The base image builds once in a few minutes; later VMs start in seconds, and toolchains are shared read-only between VMs. Claude Code, Codex, opencode, pi and Cursor CLI run in the VM with your settings, skills and MCP servers, and devvm agent login claude sets up the login from inside the VM and keeps it on your machine. It has 718 stars on GitHub with 38 forks, was created on 6 November 2026 and was last pushed on 18 November 2026. It is MIT licensed. It needs macOS 13 or newer, or Linux, on arm64 or x86_64, with Lima 2.2 or newer, and it has not been tested on Intel Macs yet. The docs warn plainly that no sandbox closes every gap, so read the safety page before you trust a VM with a project.