microagent
Last updated: 2026-07-30
microagent boots Linux microVMs from the OCI images you already use. Use the CLI or Go API to run commands inside them, move files in and out, and manage their lifecycle. microagent handles the kernel, disk, and network plumbing.
Linux and macOS are the supported host targets. On a new machine, start with
microagent doctor so the install can tell you exactly what
the host is missing before you boot a workspace.
Choose your path
Section titled “Choose your path”New here? The glossary defines workspace, rootfs, egress, and the rest of the vocabulary. Deciding whether microagent is the right tool? Choosing microagent compares it with containers, raw Firecracker, Mac VM managers, and hosted sandboxes.
- Try the CLI: Quickstart boots a microVM and runs a command inside it. If you already think in Docker commands, coming from Docker maps the common verbs.
- Embed from Go: Start with the library overview, then run microagent from a Go program.
- Connect an agent or MCP client: Launch the stdio endpoint with
microagent serve mcp. - Have a quick question: the FAQ answers the ones newcomers ask most; limitations covers what microagent deliberately doesn’t do.
Sections
Section titled “Sections”- Getting started: install, quickstart, and the first-agent walkthrough.
- FAQ: short answers to common questions, with links to the full story.
- Guides: step-by-step walkthroughs, from one-shot runs to services and snapshots.
- CLI reference: every subcommand.
- Library: Go package overview, reference, and CLI-to-library mapping.
- Backends & platform support: host requirements per backend, network modes, storage, and state.
- Limitations: the deliberate refusals and where to go instead.
- Security: trust boundary and reporting.
- Troubleshooting: common failure modes, indexed by symptom.