microagent resume
Last updated: 2026-08-15
microagent resume <name> [--reason <text>] [--state-dir <dir>]resume thaws a paused workspace and records its state as
running again. The VM’s vCPUs continue executing from exactly where they were
frozen, with guest memory, disk state, and the host-side network, port
forwarding, and vsock paths intact. After resume, exec,
connect, and stats work again.
For human output, thawing follows the lifecycle progress behavior documented for
halt. It reports only a noticeable wait, while JSON and MCP
responses carry structured results alone.
resume requires the workspace to be paused. To boot a halted or stopped
workspace from disk, use start.
Examples
Section titled “Examples”Freeze a workspace, then thaw it:
microagent pause researchmicroagent resume research--state-dir matters only when the workspace lives outside the default
~/.microagent/.
| Flag | Description |
|---|---|
--name <name> |
Workspace name; positional name is also accepted |
--id <id> |
Workspace ID alias for --name |
--reason <text> |
Opaque reason recorded as the lifecycle event’s purpose |
--state-dir <dir> |
State directory holding the workspace record (default ~/.microagent/) |
--backend <name> |
Backend identity override |
--supervisor <path> |
Override the installed host backend supervisor path |
See global flags for --output/--json/--supervisor.
Exit status
Section titled “Exit status”resume exits 0 when the VM is running again; nonzero when the workspace
cannot be found, is not paused, or when the backend cannot thaw the VM.