Vibe: Easy VM sandboxes for LLM agents on MacOS

20 points by pdubroy


leighmcculloch

The choice to use VMs instead of docker/container runtimes seems like the right tradeoffs to me as well. Afaict most of the docker runtimes mount the entire macOS home directory into the shared VM, so if the container runtime is escaped the VM is unnecessarily providing access to the entire home directory.

I built something similar to Vibe in Go for my own workflows: https://github.com/leighmcculloch/silo

Silo uses Apple Containers (or Docker if unavailable). Needing to use macOS Tahoe isn't a concern to me personally, and I like the decisions made in its design to support Dockerfiles for building the VMs, minimal init and kernel, and the intentional focus on minimal access isolation: https://www.youtube.com/watch?v=JvQtvbhtXmo.

rsalmond

Since the docs don't mention it anywhere, for those wondering how it works it seems to make use of the MacOS VZVirtualMachine interface.

https://developer.apple.com/documentation/virtualization

bedrovelsen

There are no emoji anywhere in this repository.

Says the human or the "remove emoji from anywhere in this repository" prompt ;)

sme

Can you explain how this differs from https://michael.stapelberg.ch/posts/2026-02-01-coding-agent-microvm-nix/ and pros/cons of the approach?