Skip to content

Getting Started

Loom is a desktop app (Tauri + SolidJS) that hosts real terminal panes and exposes an inbound control bus so agents can coordinate. This page gets you from download to your first pane-to-pane message.

Loom is Linux-first. Download the latest build from GitHub Releases — artifacts are hosted on Releases, not re-hosted here, so you always get the signed build that matches a tagged commit.

Platform Notes
Linux The primary target — the fully supported build.
macOS / Windows Builds exist, with a few platform parity items still in progress.
  1. Launch Loom. The new-workspace wizard opens (you can reopen it any time with Ctrl+Shift+T).
  2. Pick a working folder, choose a layout (1–16 panes), and set what each pane runs — your shell, claude, a dev server, whatever. Start from a preset like Fleet ×4 if you just want to poke around. Then create it with Ctrl/Cmd+Enter.
  3. Inside a workspace, split with Ctrl+Shift+D (right) / Ctrl+Shift+E (down). Each pane has a routing handle (e.g. Cleo, Faye) — the name you’ll use to talk between panes. See Workspaces & the grid for the whole layout story.

Every pane’s child process gets LOOM_SOCK, LOOM_PANE, and LOOM_BIN injected, and the loom CLI is on PATH. From inside any pane:

Terminal window
loom list # who's around — names, live/dead, focused (*)
loom send Cleo "run the tests" # type a line into another pane and press Enter
loom spawn --name reviewer claude # open a new pane running an agent
loom broadcast "pull main and rebase" # fan a line to every live pane

If $LOOM_PANE is empty you’re not inside a Loom pane and these commands are inert no-ops by design — the same CLI can be installed globally and stays silent outside Loom.

If your agent speaks MCP, the same operations are available as first-class tools via loom mcplist_panes, send_text, spawn_pane, broadcast, card_add, and friends. See the CLI & MCP reference for the full surface, and Agents, MCP & hooks for wiring an agent into Loom’s lifecycle.