microagent artifact
Last updated: 2026-08-15
microagent artifact <name> [--state-dir <dir>] List declared artifactsmicroagent artifact get <name> <artifact> <target> [--state-dir <dir>] [--debugfs <path>] Retrieve one output artifactartifact reports the input bundles and output paths declared in the
workspace manifest. artifact get retrieves a declared output artifact by
name without entering the workspace. The host reads it straight off the
workspace disk, so the workspace must be prepared, halted, or stopped -
artifact get fails on a running workspace. Only declared outputs are
retrievable by artifact name; for arbitrary file copying, use
cp.
In a terminal, artifact get reports its current phase and transferred bytes
on stderr when retrieval takes long enough to notice. The completed byte count
uses the retrieved file size as its total. JSON and MCP responses remain
structured and contain no terminal progress text.
Examples
Section titled “Examples”List declared artifacts, then fetch one by name:
microagent --json artifact researchmicroagent artifact get research report ./out/If an output path sits under an attached disk mountpoint, artifact get
reads from that disk. Otherwise it reads from the rootfs image.
--debugfs matters only when the debugfs binary lives somewhere unusual.
| Flag | Description |
|---|---|
--state-dir <dir> |
State directory (default ~/.microagent/) |
--debugfs <path> |
debugfs binary path for artifact get |
See global flags for --output/--json.
Exit status
Section titled “Exit status”artifact exits 0 when the workspace manifest is found and read. It exits
nonzero when the workspace cannot be found, the named artifact is not
declared, the workspace is running (for artifact get), or the read from the
workspace disk fails.