Resources
Get unstuck fast.
Every guide on this site, the troubleshooting page, and the issue tracker, one click from here. Most problems are answered in under a minute.
Start here
Pick the page that matches your problem.
Setting up, stuck mid-mission, or hitting a usage limit: there is a guide for each. If nothing fits, the issue tracker is at the end of the list.
Escalation
Three tiers, in order.
Loom has no support tickets and no account managers, because it has no accounts. Help works the way open source works.
1. The guides
Install, first goal, permissions, rate limits. The walkthroughs above cover the path from a fresh download to a six-session fleet running a real mission.
2. The documentation
For reference detail beyond what a guide covers, docs.mingllm.com and the documentation page go deeper on every part of the app.
3. The issue tracker
Loom Conductor is open source under Apache-2.0, and the issue tracker is the support channel. Bugs, confusing behavior, and feature requests all belong there.
Before you file an issue
A good report gets fixed faster. Search existing issues first, then include enough context to reproduce what you saw:
- Your operating system and the Loom version you are running.
- Which Conductor provider you had configured, if the problem involves planning, dispatch, or verification. Never paste the key itself; it belongs in your OS keychain and nowhere else.
- What the mission was doing when things went wrong: what the mission DAG showed, what the activity strips said, and what was in the terminal of the affected session.
- Whether auto-accept was on, and whether you had changed any terminal's permission mode.
If the problem is a stall or a usage limit rather than a bug, read rate limits first. The Conductor recovers rate limits and stalls on its own, and rotates pooled Claude accounts when one hits its usage limit, so the behavior you are seeing may be the recovery working as designed.
Hand it the work.
Walk away.
macOS, Linux, and Windows. Around 13 MB. Free and open source.