Docker Sandboxes · Docker, product page, accessed 2026-08-10 (surfaced via a Hacker News thread at 206 points and 139 comments around four hours old)
Docker ships sandboxes that make "YOLO mode" the default for coding agents
Docker Sandboxes runs each agent inside its own microVM with only the project workspace mounted in, so an agent can install packages, edit configs, and spin up its own containers without touching the host. The product page states plainly that --dangerously-skip-permissions is now the default, on the reasoning that isolation, not a permission prompt, is what makes permissive execution safe. It ships out of the box for Claude Code, Gemini CLI, Copilot CLI, Codex, OpenCode, and Kiro, installable in one line via Homebrew or winget. The Hacker News thread around the launch is itself substantive: commenters compare the microVM approach against Firecracker, bubblewrap, gVisor, and Incus and LXD, and debate whether a cgroups boundary or a full VM boundary is the right one for agent isolation.
Why it matters: Sandboxing, not model capability, has kept most unattended agent setups from running hands-off. A mainstream vendor making it a one-line install lowers the bar for running agents permissively without hand-rolling a Firecracker or gVisor setup first.