devvm Gives Every Project Its Own VM for Coding Agents
The MIT-licensed Go tool builds an isolated Lima VM per project folder, with detected toolchains and coding agents inside.
devvm, an MIT-licensed coding agent sandbox written in Go, had 620 stars and 31 forks on GitHub as of 2026-11-14, collected in the eight days since the repository was created on 2026-11-06. The pitch is narrow and practical: run one command inside a project folder and get an isolated virtual machine carrying that project's toolchain, ready for you or an agent to start coding.
Install and requirements
On macOS, Homebrew installs devvm and Lima together. On Linux, an install script handles it and also works on macOS; it asks before installing Lima, QEMU or access to /dev/kvm. A devvm doctor command checks the machine and explains how to supply anything missing. Releases are signed with a minisign key, and the docs show how to verify the install script against it before running it.
The requirements are macOS 13 or newer, or Linux, on arm64 or x86_64, with Lima 2.2 or newer. The project says it has been tested on Apple silicon Macs and on Linux on both architectures, but not yet on Intel Macs. The VMs run on Lima.
How a VM gets built
Running devvm in a folder shows what the new VM will get, with toolchains detected from the project's files: detection is file based, so a project with a package.json is given node. You confirm, or customize the toolchains, coding agents, layers, network tier and size. The shell then opens inside the VM at the same path as on your machine, with a prompt starting with (devvm), and that shell is where you run an agent such as claude. Running the command in the same folder again reopens that VM.
The first run asks a few questions that set defaults for every future VM, then builds the base image, which takes a few minutes. Later VMs are copies of that image and start in seconds, with toolchains shared read-only between them.
The coding agents supported in the VM are Claude Code, Codex, opencode, pi and Cursor CLI, each with your settings, skills and MCP servers. devvm keeps agent settings and logins in a store of its own, and devvm agent import copies them in from an agent you already use on your machine. Built-in layers cover docker, nix and desktop, and devvm layer new creates your own. The devvm GitHub repository carries the full docs.
Isolation, network and clones
Each VM mounts only its own project folder. New VMs get the allowlist network tier by default, so they reach only the hosts you allow. On every tier, tokens such as your GitHub token and Claude Code token stay on your machine rather than inside the VM. Claude Code needs its login before first start, which devvm agent login claude performs from the VM while keeping the credential on the host.
devvm --clone goes further. The VM gets its own clone of the repository, so nothing inside it can touch your working tree or .git, and its work reaches your repo only when you fetch it, for example with git fetch devvm and then git log -p main..devvm/main to review the diff before merging.
Limits and open questions
The project's own documentation states that no sandbox closes every gap and points readers to a "Staying safe" page before trusting a VM with a project. Intel Macs are untested for now, Windows is not mentioned at all, and the source gives no figures on how much disk or memory each VM consumes or how large the base image is. It also does not say how many toolchains the detection covers.
What it means for building apps with AI
The notable part is the assumption behind the tool: coding agents that run long enough to want a machine of their own, with runtimes already in place and credentials kept off that machine. That is a different shape of product from a hosted builder such as Draftship, the AI app builder, where you describe an app in plain language and get code, a database, sign-in and hosting without managing a sandbox. A team running agents locally gets the same environment every time it opens a folder. A team shipping a web app gets a different workflow. The source makes no claim that devvm does anything beyond the sandbox itself.
Primary sources
- devvmhq/devvm: One VM for every project. An isolated sandbox with your project’s toolchain, ready for you or a coding agent to start coding · GitHub trending AI repositories, Nov 14, 2026
This article was drafted with AI assistance from the primary sources listed below and checked automatically against them. An editor hasn't reviewed it yet.