miles site-pages
slug and files; each file has path, mimeType, sizeBytes, and usually a previewUrl.
With a path, prints the file content. Add --output <file> for binary files or when the agent needs a local copy. Use this to inspect generated HTML or CSS, verify page coverage, or compare a generated file in a normal repository workflow.
miles export
html is the default and is available once the site build completes. It returns previewUrl and slug. It is fully headless.
theme is available after convert-theme. It returns themeSlug, downloadUrl, editorUrl, and dashboardUrl. Reading that metadata is headless; --download <file> needs the connected browser workspace for design sandboxes and writes the theme ZIP to the chosen file.
Miles does not currently provide a WordPress blueprint, WXR/content export, or other export types.
Related commands
Usemiles screenshot <preview-url> to render a stored design or HTML preview. Use miles screenshot --live to capture the actual WordPress frontend after conversion; that form needs a browser connection.
Next: Lifecycle and compatibility.