devvm
One VM for every project: an isolated sandbox with your project's toolchain, ready for you or an agent to start coding.
One VM for every project: an isolated sandbox with your project's toolchain, ready for you or an agent to start coding.

An isolated sandbox with your project’s toolchain, ready for you or a coding agent to start coding.
Open a terminal and cd into any project folder.
devvm shows what the new VM gets. Confirm to make it, or customize it.
devvm opens a shell in the VM, whose prompt starts with (devvm), so start your agent there.
Claude Code needs your Claude login before its first start, which devvm agent login claude makes from the VM and keeps on your machine (your first VM). The next time you run devvm in the folder, it opens the same VM, and devvm tools adds an agent to a VM you already have.
devvm chooses the toolchains your project’s files call for, and you can choose more when you customize a new VM or name them with --tools (toolchains).
Claude Code, Codex and opencode run in the VM. Choose one when you customize a new VM, or choose them for every new VM in devvm setup (coding agents).
devvm ships the docker, nix and desktop layers, which you choose when you customize a new VM, and devvm layer new creates your own custom layers you can apply to any of your VMs (layers).
devvm ships with sensible defaults so you can start coding in a sandbox with a single command.z), tree and tldr.:5173 in the VM opens at localhost:5173 on your machine (ports).devvm code opens the VM in VS Code over Remote-SSH (devvm code).devvm locks .git’s hooks and config, so the VM can’t change what git runs on your machine (.git protection).--clone, the VM works on a clone of the repo of its own instead of your folder, so nothing in it can touch your working tree or .git, and its work reaches your repo only when you fetch it.devvm builds each version of a toolchain once and shares it read-only, so all VMs use the same copy (shared tools).devvm builds into an image: devvm layer new mailpit starts one, and devvm --layers mailpit makes a VM with it (your own layers).devvm setup --layers gives every new VM the layers you choose, so your shell setup, aliases or dotfiles can go in a layer of your own that each VM gets unless you leave it out (extras of your own).--from starts the base image from a container image instead of Ubuntu’s, such as node:24 or your team’s own (starting from a container image).devcontainer.json, devvm sets up its VM from the file’s container image, ports, environment and commands (devcontainer.json).devvm runs on macOS and on Linux, on arm64 or x86_64. It needs Lima, which runs the VMs with Apple’s Virtualization framework on macOS and QEMU on Linux (backends). Homebrew installs Lima along with devvm, and on Linux, Lima also needs QEMU and access to /dev/kvm. Installing lists every requirement, and known limits lists what Linux hosts lack, such as .git protection.
No. You start the agent in the VM’s shell, so it runs in the VM, and you never install it on your machine. There it sees only what the VM can reach.
Yes. devvm is open source under the MIT license.
Install devvm, then run devvm in any project folder.
Texto de devvm.dev tal como lo publicó, leído de su página y mostrado aquí con el formato de El Autómata. El original, en devvm.dev · Volver a la noticia de El Autómata