Skip to main content

Loom documentation

Loom runs workflows locally and records structured diagnostics. Start with the task you need to do:

Start here​

GoalLink
Run your first workflowHello Loom
Understand the author → validate → run → diagnose loopHow Loom works
Diagnose a failing runDiagnostics ladder
Browse the CLICLI overview
Understand artifact layoutRuntime logs contract

Adopting Loom in a repo​

  1. Follow Hello Loom for your first successful run
  2. Learn the workflow format in Syntax v1 and Workflows
  3. When something fails, use What to share to share the minimal evidence set

Alpha 1 support boundary​

The bullets below are a short orientation. The Alpha support boundary defines Loom's claim states, evidence rules, and compatibility limits.

  • Execution: local-only with loom run --local
  • Target: native host jobs use target: linux on Linux or target: darwin on macOS; native Docker jobs require target: linux. GitLab execution remains Linux-only.
  • Providers: host and Docker-backed execution today
  • Agent integration: see Agent integration for MCP, Cursor skill, and agent-driven workflow setup

Site structure​

SectionWhat's there
ProductWhat Loom is, why it exists, how it works, roadmap
DocsGetting started, concepts, guides, workflows, troubleshooting
ReferenceCLI commands, workflow schema, artifact contracts
Knowledge BaseFAQs, patterns, and operational playbooks