
See the plan first
Orchestra shows the planner's tasks and waits for your go before a single worker starts.
loom orchestra "…" --plan-only
Loom 2.1 makes the crew safer and easier to steer: plans you approve first, guardrails for each project, a brain you can curate, and the tools you already use able to start the work.

Orchestra shows the planner's tasks and waits for your go before a single worker starts.
loom orchestra "…" --plan-only

Save a goal, its fleet and its options once, then run it again from the phone or a script.
loom recipes run nightly-sweep

A worker stalled or failed? Hand just that task to another agent or model, keeping its worktree.

Call models fast, smart or cheap everywhere. Set a daily dollar or token cap: a warning at 80%, a hard stop at 100%.
loom models --health

Pin what matters, merge near-duplicates, archive what's gone stale, and import or export it as Markdown.
loom brain:export --md docs/BRAIN.md

Every turn records which memories it was given, with their scores and the reason each was picked.

Each chat can get its own git branch, with commit messages drafted from the prompt and the diff.
loom pr:describe

Protected paths, a shell command denylist, secret checks before every commit and push, and Strict, Normal or Trusting presets.
loom audit --risky

Face ID lock, messages that send when you're back online, share text into a chat, and ask about any line of a diff.

A link to one Orchestra run with its goal, tasks and results, with a countdown until it expires. Team fleets and per-project approvers too.

A /loom comment on a GitHub issue, /loom in Slack, Jira intake, GitLab MR feedback and Discord run threads.

Subscribe to every trigger's upcoming runs as an iCal feed, and get the daily digest by email.

Prometheus metrics at /metrics, scheduled backups, crash bundles with secrets redacted, and disk usage per project.
loom backup --every 1d --keep 7

Stream a turn as NDJSON, follow a run live, define your own aliases, and tab-complete every option.
loom send --stream "…"

Your own keyboard shortcuts, recent commands first in ⌘K, notification history, and your layout back when you reopen.
Loom 2 turns one brain into a whole crew: fleets of agents on different models, working in parallel, steered from your desk or your phone, and able to drive Loom themselves.

Two Claude Code on Opus 5.5 next to two Codex on GPT‑5.6, in one Orchestra run. Any agent, any model, as many times as you like.
-w claude-code@claude-opus-5-5x2,codex@gpt-5.6x2

One prompt to several agents or models at once, each in its own worktree. Read the answers and diffs side by side and keep the best.
loom compare

A demo project and a scripted demo agent that need no keys and no CLIs, with a guided walkthrough of the whole loop.
loom try

Eight skills teach Claude Code, Codex, Grok and OpenCode every Loom command. The MCP server lets one agent start others.
loom skills install loom

Send a note to an agent mid-turn instead of queueing it. It takes the hint and keeps going.
⌥ Enter

Which model wins your races, how often a turn finishes, and what each one costs — per project or across all of them.
loom scoreboard

New project, cloned repo or new chat from the phone, with the agents and models you pick.

A checklist that follows what you've really done, and installs agent CLIs for you in one click.
loom setup

Ask the agent something on the side with /btw. The answer never touches the thread.
/btw

Edit a prompt or retry a reply and flip between the versions with ‹ 1/3 ›. Nothing is lost.

In a shared chat, see who's watching and who's typing.

When a PR an agent opened fails CI or gets a review, the fix request goes back to the chat that opened it.

Hand a chat to another of your machines with its history and its agent's own session.
loom chat:move

Your assigned GitHub and Linear issues become chats or Orchestra goals in a click.
loom intake

Two Claude Code accounts? When one hits its cap, Loom moves to the next before it switches CLIs.
loom accounts add

A real shell in the project and a file browser with syntax colours.

Every schedule and webhook with its next run and last results. Run now, pause, resume.

Right-click a file, or ⌘K: open it in VS Code, Cursor, Zed or JetBrains. The one you used last comes first.
loom open --in zed

After the first reply, “Chat 7” becomes “Fix the login redirect”. Locally, for free; never over a name you gave it.

Something off? A redacted report of versions, doctor checks and logs, handed to your own agent to diagnose — or a ready-to-paste issue.
loom triage --agent codex
The full list, with every fix, is in the changelog and the release notes.