Skip to main content

​
Start work without waiting

The long-running commands site-create, say, build-site, and convert-theme accept --no-wait.
This starts work and returns a handle with ok, status: "streaming", siteId, conversationId, and suggested next actions. It requires a Miles service that supports cancellation. Use --no-wait when the agent needs to poll or keep its own progress interface active. Otherwise, the command streams progress and waits by default.

​
miles wait-job

Waits for the active run and returns one structured settled result. Progress is written to standard error; the JSON result is written to standard output. The default timeout is 600 seconds. Key result fields are: If the timeout expires, the result remains status: "running". Run wait-job again or cancel the work.

​
miles cancel

Stops the active run. The later wait-job result will report outcome: "aborted". Cancel when the user changes their mind; do not silently cancel useful work or start a replacement build before the first run has settled.

​
Protected changes

When approvalRequired is present, the protected work has not happened. Tell the user what Miles wants to do and wait for an explicit answer to that specific change. Only then call approval-respond. Do not use say, --yes, --force, or a generic “continue” to answer an approval. A declined approval ends that branch of work.

​
miles undo

Reverts the most recent eligible site turn and its matching conversation messages. The JSON result includes ok, kind, snapshotVersion, truncatedMessages, and browserRefreshRequired. Undo is one level only and has no redo. Check site-state for undoAvailable first. For a broad experiment, use site-attach --duplicate before the change instead. Next: WordPress and browser connection.