Loom publishes JVM artifacts, a command line client and container deployment assets separately.
Maven Artifacts
See Maven Artifacts for the BOM and the primary client and shared model modules.
Command Line Client
metaloom is the command line client for a Loom server. It ships in two forms from the same
io.metaloom.cli:metaloom-cli module:
| Form | Artifact | Notes |
|---|---|---|
Runnable JAR |
|
Self-contained; needs a JVM. Built by |
Native binary |
|
No JVM required, ~30 MB, starts in single-digit milliseconds. Built by
|
See Command Line for usage.
Containers
Loom ships as metaloom/loom-server (production) and metaloom/loom-demo (all-in-one). The AI agent’s
coding sandbox additionally uses the metaloom/loom-session-runner image. See
Containers for the Docker / Compose examples and Container Images
for the full list. The agentic modules (loom/agent/chat, loom/agent/memory, loom/agent/sandbox)
are part of the server image and require no separate artifact.
Helm Chart
See Helm Chart for the Kubernetes deployment entry point.