Skip to content

CLI reference

CommandPurpose
runBoot an image and run a command, then tear down
createCreate a named, persistent workspace
applyApply supported workspace spec changes without rebuilding
cloneCopy a stopped workspace into a new workspace
cpCopy files into or out of stopped workspace disks
artifactsList and retrieve declared workspace artifacts
networkInspect workspace network mode and port forwards
startBoot a stopped workspace
superviseStart and restart a workspace according to policy
haltClean disk-preserving shutdown
quarantineSever host-side network and mediation
stopGraceful shutdown
killHard terminate
deleteRemove a workspace and its state
statusShow workspace state
resultShow structured workspace result
psList workspaces
logsShow boot/serial output
connectOpen the workspace console
profilesList exact named resource profiles
imagesList or prune local image records
prunePrune stale records and optional reusable image baselines
perfMeasure workspace boot performance
contractPrint the backend-neutral runtime contract
hostReport host backend capabilities
doctorCheck the host for backend support
rootfsBuild a rootfs from an OCI image
kernelInstall or verify a custom kernel
versionPrint the version

microagent.yaml is the declarative form of microagent create — image, profile, restart policy, networking, mounts, mediation, and outputs in a single file you can keep in source control.

  • --json — print JSON output; place before the subcommand
  • --text — print human-readable output
  • --output <json|text> — select output format
  • --supervisor <path> — override the installed host backend supervisor path (MICROAGENT_APPLEVF_SUPERVISOR and MICROAGENT_FIRECRACKER_SUPERVISOR work too)

All commands can print JSON output. With --json before the subcommand (or MICROAGENT_OUTPUT=json), the response matches the shape documented in the supervisor protocol. Scripts should consume JSON; humans get the text format by default.