What to share when asking for help
Share the command, relevant state and a short event excerpt. Follow the Diagnostics ladder to locate them.
Copy/paste template
Command: loom run --workflow .loom/workflow.yml [flags]
Loom version: <loom version>
OS: <operating system>
Run ID: <run_id>
Job / step / command ID: <IDs from the records>
Status / exit code: <recorded result>
Expected behavior: <what should happen>
Actual behavior: <what happened>
Event excerpt: <short reviewed excerpt containing the failure>
How to find each item
Native run directory
Use the directory printed by loom run. Its state.jsonl and events.jsonl
contain the recorded lifecycle and output. If recording could not start, share
the terminal error and command.
Failing job and step
Run loom logs <run_id> --state and find the failed operation. Use
loom logs <run_id> --json for full context. MCP clients can use loom_read_run
and loom_read_events with job_id to narrow the excerpt.
Short excerpt (10–20 lines)
Include the failing command or operation, error message, exit code and nearby context. If several jobs failed independently, identify each job and include the relevant excerpts. The same two files also contain provider failures.
Redaction checklist
Before sharing, review the excerpt for secret values, credentials in URLs, authorization headers, private keys and sensitive hostnames or paths. Declared secrets are protected before recording, but tools can emit undeclared values. If redaction removes relevant context, describe what was removed.