#Install your first Workflow

The CLI and business Workflow packages have separate installation lifecycles. In the initialized project, stop the Service before adding or removing packages.

intloom stop
intloom loom add @intloom/intent
intloom loom list

A bare package name resolves its current registry version. Installation retains package name, exact version, archive hash, and local source where applicable. It disables package scripts.

If you have a compatible local archive, use it instead of the registry package:

intloom loom add /absolute/path/intloom-intent-0.1.0.tgz

Retain that archive so the installation can be restored. The Workflow artifact protocol must match the host; its protocol version is separate from its npm version.

#Verify loading

intloom start
intloom looms

loom list shows installed packages. looms shows the Workflows loaded by the running Service, their availability and diagnostics. A package may be installed but fail loading; inspect its phase and error.

For CMD/TUI, configure the model before executing a Run. For external MCP, prepare the connected Agent client. Continue with CMD, TUI, or MCP.