#CMD operation guide

CMD is useful for explicit operations, file input, and scripts. It accepts complete execution arguments and returns promptly; use separate observation and answer commands.

#Input and output

intloom run intent --prompt-file ./request.txt --json
intloom run intent --prompt-file - --json
intloom status --json --no-color
intloom logs RUN-example --follow --json

The stdin example expects intent text piped into the command. --prompt preserves the complete string; --prompt-file cannot be combined with it.

Without --json, CMD prints readable summaries and tables even when redirected. --json emits one CoreResult object for ordinary operations; streams emit JSON Lines. Logs and diagnostic stderr remain separate from machine stdout.

#Automate deliberately

Check ok for the command and status for the Run. A successful admission or answer may leave the Run running or waiting. A query of a failed Run can exit nonzero, while successful cancellation exits zero.

Retain request identities for uncertain writes. The client does not automatically retry execution. A watcher reconnects by reading state rather than replaying run.

--project chooses an exact project root. Artifact export paths still use your shell's working directory. --no-interactive disables lightweight setup selection; it does not answer Workflow questions.

Use Run operations, results, and the complete command reference.