-it flags are needed.
Set an API key to use microsandbox cloud. Each reference page marks local-only commands and cloud limitations.
Install
~/.microsandbox/ and creates command links in ~/.local/bin/. It does not edit shell startup files. If ~/.local/bin is not on your PATH, the installer prints the command to add it. On macOS, Homebrew provides the same CLI through the official tap. On Windows, use PowerShell. Windows support is currently in preview.
Local sandboxes require Linux with glibc 2.28 or newer and KVM, an Apple Silicon Mac, or an x64 or ARM64 machine running Windows 10 or later with Windows Hypervisor Platform enabled. See Linux troubleshooting, macOS troubleshooting, or Windows troubleshooting for setup help.
Command forms
Use short commands for everyday work. These forms are equivalent:ls, rm, cp, and mod also work inside sandbox and sbx.
Saved-state operations are grouped under msb snap. The equivalent long form, msb snapshot, is also supported; this documentation uses msb snap consistently:
--full to save disk state for a fresh boot. The group defaults to the source sandbox’s name, so the first command creates devbox:ready. Full captures, live branches, groups, and archive operations are local-only. Use msb branch devbox --names worker-a worker-b to create children directly from the same live moment. See Snapshots for backend limits and resource bindings. Existing top-level restore and snapshot save/load commands remain supported.
Quick reference
Quick start
msb run without --name creates an ephemeral sandbox, removed when its command finishes. Named sandboxes persist. Names must contain 1–128 UTF-8 bytes.
Global options
Shell completion
msb completion <shell> prints a completion script for bash, zsh, fish, elvish, or powershell. Write it to the location your shell loads completions from:
Command tree
Use--tree as an alternative to --help to see every command, subcommand, and flag at once: