Skip to content

devvm 0.2.0-rc.1

Pre-release
Pre-release

Choose a tag to compare

@w3cj w3cj released this 21 Nov 02:53
· 14 commits to main since this release
v0.2.0-rc.1
7c4659c

This is a release candidate for 0.2.0, and it adds to 0.1.1-rc.3. 0.2.0 takes 0.1.1's place, because its breaking changes need a new minor version. Install it with devvm upgrade --to 0.2.0-rc.1, the install script's --version 0.2.0-rc.1, or brew install devvmhq/tap/devvm-rc. Homebrew's devvm stays on 0.1.0.

Each change below links its section on the 0.2.0 page, which has its full story, and the commit that made it.

Highlights

  • Claude Code's plugins, MCP servers' logins, claude.ai connectors and --setup-token login all work in a VM (details).
  • The bugs you reported are fixed, among them 24-bit color, folder names such as x--y, and a folder's VM after your Mac restarts (details).
  • Your secrets are safer from VMs: the part of each VM's proxy that reads its traffic holds only that VM's secrets, in a sandbox (details).

What to do

  1. Run devvm update in each existing VM's folder, and give the first one several minutes, because it builds base and its shared tools again (details, c9005ae).
  2. Run devvm restart, or devvm stop, in the folder of each VM that was running when you upgraded, so it gets the new ssh port, proxy and SSH agent relay, and start Claude Code there in a new shell (too many VMs at once, the proxy runs without a sandbox, agent forwarding, Claude Code's plugins, details, details, details, details, details, e4ea123, aeea313, 19f9900, 7cc0dd7, e97db05).
  3. Stop one of your running VMs before you start an 18th, because at most 17 VMs run at once, and a start past 17 fails and names the VMs that are running (too many VMs at once, details, e4ea123).
  4. Use a host's full name, such as jenkins.corp.example.com, where a tool in a VM reached it by a short name such as jenkins, because the proxy no longer adds this machine's DNS search domain (a name that doesn't resolve, details, c872cfe).
  5. Disconnect the claude.ai connectors you don't want VMs to use, or deny mcp-proxy.anthropic.com with devvm network deny, because with your subscription's login, code in a VM can now act through your connectors (details, #61, c1db911).
  6. If devvm 0.1.0 imported your Claude Code plugins, sign in again to any plugin that keeps a login of its own, because every VM with Claude Code could read that login (Claude Code's plugins, details, details, 7cc0dd7, e97db05).
  7. If a folder at a VM's path is now on another volume, such as a copy of the disk or, on Linux, a rolled-back Btrfs snapshot, run devvm adopt there to give it that VM (details, 4ccdbf8).
  8. If a folder in devvm's agent store is a link, make it a folder of its own, because devvm agent import and devvm agent save refuse it, and a VM with Claude Code refuses a linked plugins folder (devvm's agent store, Claude Code's plugins, details, details, d939d1d, 7cc0dd7).

Fixed

  • devvm agent login claude --setup-token now shows Claude Code's address and the prompt for its code, and Ctrl-C ends an agent's login (details, details, #57, 6965efc).
  • Programs in a VM, such as coding agents, now get your terminal's 24-bit color in devvm's shell, devvm agent login and ssh to a VM by name (details, #54, 947decb).
  • A login to an MCP server that you make in a VM now finishes and stays in that VM (details, #62, ea3037b).
  • A plugin in a VM now keeps its data, and you can install plugins and update marketplaces there (details, #56, e97db05).
  • A project folder keeps its VM after your Mac restarts, though a folder that moved before its VM started again needs devvm adopt VM (details, #60, 2c0a894).
  • A plugin, marketplace or MCP server with a name such as secret-scanner no longer gets its settings redacted in a VM, so Claude Code stops refusing the VM's settings.json from the VM's next launch. Thanks to @jspiro for the report and @dhruv1220 for the tests' idea in #58 (details, #55, f384829).
  • A folder whose name has separators in a row, such as x--y, foo (copy) or C++ stuff, now gets a VM when you run devvm there again. Thanks to @se6a for the report (details, #52, ba5613e).
  • A warning now prints above the status line, so the status line no longer erases a question's prompt or what you typed (details, 2b176c9).
  • A plain ws:// WebSocket now connects through the proxy, where it used to get 502 (details, f37c70a).
If you use Claude Code and devvm's agent store
  • devvm now warns when devvm agent import or devvm agent save copies a marketplace holding a credential, when a project folder is inside or holds an agent's folder, and when an import leaves out a link (details, details, details, c9d0fdb, c901b92, d939d1d).
  • A failed devvm agent import or devvm agent save now leaves the agent store as it was, and two of these commands at once, or a save and a VM's new Claude Code login, take turns (details, details, details, details, 3101c85, b04a1a9, f80fd2d).
  • On a Mac, devvm agent save and devvm agent import no longer delete a store file whose name differs from yours only in case, such as Foo.md (details, 888078c).
  • devvm agent import fails on an agent's folder past 20,000 entries, 128 MiB or 16 MiB in one file, and devvm agent save saves nothing past folders 128 deep or paths of 4,096 bytes (details, details, c901b92, 888078c).
  • While devvm can't read a VM's state, devvm agent import follows no links and warns, so run devvm doctor and import again (details, b04a1a9).
  • devvm agent save no longer crashes on an agent's settings file that's a single JSON string (details, 1ecd1fa).
If you use Cursor
  • Cursor's CLI in a VM can no longer make some changes to your account, team or cloud agents, such as merging a cloud agent's pull request, so make those from Cursor on your machine (details, 872c2e2).
If you use a company proxy
  • A launch, a devvm network change or a devvm restart that devvm refuses, such as for a missing proxy secret, now leaves a running VM running (details, 4a4aabe).
  • A NO_PROXY entry with an IPv6 zone, or with a port that's 0 or isn't plain decimal, now matches no host (details, details, #59, 8afdec7, a7cc125).
If you use links or forwarded ports
  • A VM that forwards every port leaves out the 17 ports that VMs' ssh uses, so list a server's port on one of them, such as an X server's 6000, with devvm ports (ports, details, e4ea123).
  • devvm link rm now ends a link's open connections within seconds, and a stopped port forwarder or link session no longer leaves its ssh running (details, details, c63f9a3, 90a64a4).
  • A forwarded port's or a link's connection now ends once its client has closed and the VM has sent nothing for 30 seconds, which can cut nc -N in front of a slow query (details, c63f9a3).
  • After this machine briefly runs out of open files, forwarded ports keep answering on both ::1 and 127.0.0.1, and devvm desktop keeps running (details, details, details, 608ab43, f37c70a, df1d76b).
If you use --clone
  • devvm clone fetch and devvm rm's fetch no longer fail with clone_fetch_failed on a VM that forwards no ports (details, c1cf96e).
If you use SSH agent forwarding
  • ssh-add in a VM can still list and use your SSH agent's keys, but it can no longer remove, lock or add them (details, 19f9900).
If you use a Linux host
  • devvm no longer warns that .git/config lost its pin when git replaces the file just as devvm pins it (details, 90a64a4).
  • In a VM confined to its proxy with transparent mode off, a lookup now fails at once from the VM's next launch, instead of waiting, as wrangler dev did for about 40 seconds (details, 63bb1ff).
  • When a VM's proxy can't get its whole sandbox, such as on a kernel whose Landlock is older than ABI 6, the VM keeps its network and devvm doctor warns, naming what's missing (details, 941c63c).
Security hardening: a VM that tries to attack your machine can now do much less
  • Each VM's proxy now runs as two processes, and the one that reads the VM's network holds only that VM's secrets and can't read your files, reach the Keychain or connect to local services (details, details, details, details, aeea313, 941c63c, 1793353, 3da3843).
  • On a Mac, devvm refuses a project in its own folders whatever the case of their names, such as ~/.Config/devvm/layers, so delete a VM already made there with devvm rm (details, c41ca82).
  • devvm history import refuses an export with a name such as .claude/./settings.json, so an export can't put an agent's login or devvm's setup files into a VM (details, e97db05).
  • A VM can't fill a Linux host with processes, because devvm carries at most 256 of its connections to the proxy at once (details, f37c70a).
  • A VM's proxy holds at most 2,048 of its connections, closes one that waits 10 minutes for its next request, and takes at most 64 KiB of headers (details, f37c70a).
  • A devvm network change never leaves a VM running without its proxy (details, 4a4aabe).
  • While a VM runs, Lima's console log and Lima's own logs for it each stay under 10 MiB, plus one older file of up to 10 MiB, so a VM can't fill your disk (details, 9c74dac).
  • While they run, the port forwarder's and link session's logs stay under 1 MiB and the build proxy's under 10 MiB, and the run logs take at most 256 MiB together (details, 9c74dac).
  • Lima's console logs no longer keep a VM's proxy password (details, 4d40958).
  • devvm now reads every host as the proxy does, so devvm secret set, NO_PROXY, MCP servers' URLs and --from no longer take a host with a letter such as the Kelvin sign as plain ASCII (details, 4e92549).
Internal changes
  • devvm doctor now warns once of each VM whose state devvm can't read, naming the VM, the file and why, and it changes nothing (details, 5924a37).
  • mise is 2026.11.10 in base and on this machine, the docker layer has Docker 29.10.0 and compose 5.8.0, and Cursor's CLI is 2026.11.17-f532c45 (details, c9005ae, 01e837a).
  • In a terminal, a status line now says what devvm waits for during its slow steps and while another devvm changes the same thing (details, details, 2b176c9, cb7177b).
  • When devvm can't read a project folder, it names the folder and why, where it used to say the VM was made for an earlier folder (details, cb7177b).
  • A folder that moved while a restart renumbered its disk keeps its VM, once the VM has recorded its folder's volume at a launch (a moved or renamed folder, details, ba510ee).
  • The shared Nix cache downloads each package once, even when two requests for it come close together (details, 90a64a4).
  • devvm now refuses a VM's size that isn't a number, naming it, where the VM used to start with the image's size, so set it again with devvm size (details, 0b85f5f).