For
Every engagement gets a fleet.
Brief one mission per client, let six parallel Claude Code sessions execute it, verify the result, and hand off clean. Loom Conductor is built for time-boxed work.
Engagements
Time-boxed by design.
One mission per client
Hand the Conductor the engagement goal. It plans the goal into tasks, dispatches them across a fleet of six real Claude Code CLI sessions, and shows progress on a mission DAG with live activity strips you can read at a glance.
Verified before it counts
The Conductor watches every terminal, answers permission prompts, recovers rate limits and stalls, and verifies work before a task counts as done. What you present at the end of the week is what actually ran.
Clean handoff
The built-in source control panel gives you a full git graph, and the editor shows hunk-by-hunk AI diffs. Walk the client through exactly what changed, commit by commit, before you close the engagement.
Setup
Productive on a fresh machine in minutes.
The installer is about 13 MB and runs on macOS, Linux, and Windows. The fleet uses your existing Claude login, so there is no API key to provision for it. Sign in once and brief your first mission.
# install Claude Code and sign in once
$ curl -fsSL https://claude.ai/install.sh | bash
$ claude login
# then launch Loom and brief the missionQuestions
What consultants ask.
Whose keys, whose bill?
The app is free and Apache-2.0 open source. The fleet runs on your existing Claude login with no API key. The Conductor is bring-your-own-key, with OpenAI, Anthropic, Google, xAI, Groq, Cerebras, DeepSeek, Mistral, OpenRouter, any OpenAI-compatible endpoint, or a local model via LM Studio, MLX, or Ollama. You pay your providers directly, which keeps expensing simple.
Is client code safe on my machine?
Keys live in the OS keychain only. A secret-path deny-list blocks reads and writes to sensitive files, every file, git, and shell operation goes through a workspace authorization registry, outbound requests pass an SSRF-guarded Rust HTTP proxy, and there is no telemetry.
What happens to permission prompts during a long run?
The Conductor answers them for you. Auto-accept presses only the safe affirmative, it is toggleable, and shift+tab cycles one terminal's permission mode when you want tighter control on a sensitive client repo.
Hand it the work.
Walk away.
macOS, Linux, and Windows. Around 13 MB. Free and open source.