Resources
All systems local.
Loom Conductor runs entirely on your machine. There is no Loom cloud, no Loom server, and no Loom database, which makes this the easiest status page on the internet to maintain.
Current status: whatever your laptop says
Most status pages exist because a company sits between you and your work. Loom does not. The app is a 13 MB desktop install, the fleet is six real Claude Code CLI sessions running locally under your own Claude login, and the Conductor calls whichever model provider you brought your own key for. There is no telemetry, no account beyond your Claude login, and no middle tier that can have a bad day on your behalf.
So if Loom feels down, the honest answer is that something on your machine or at one of your providers is down. The good news: that list is short, and you can check all of it in about a minute.
First checks
Start with the CLI.
The fleet drives the official Claude Code CLI, so if the CLI is missing, outdated, or signed out, all six terminals feel it at once. Two commands settle it.
# is the Claude Code CLI installed?
$ curl -fsSL https://claude.ai/install.sh | bash
# is your login still valid?
$ claude loginThe checklist
Three places to look when something feels down.
The claude CLI
Loom orchestrates real CLI sessions, it does not replace them. Confirm the CLI runs on its own in any terminal. The Claude login guide covers setup from scratch.
Your login and limits
Usage limits look a lot like outages. Loom recovers rate limits and can rotate pooled accounts when one is parked, so check rate limits and account rotation before assuming the worst.
Your provider status pages
The Conductor is bring-your-own-key across providers like OpenAI, Anthropic, Google, and OpenRouter. If planning stalls, check that provider's own status page. Local Conductors on LM Studio, MLX, or Ollama have no status page at all, which is rather the point.
Still stuck?
Work through the troubleshooting guide, and if the problem survives that, file an issue on GitHub with your platform and what the terminal showed. Since the whole app is open source, the incident report and the fix live in the same repo.
Hand it the work.
Walk away.
macOS, Linux, and Windows. Around 13 MB. Free and open source.