Installation

What you need

Loom is built with Bun and uses Bun's JavaScript runtime. For the prebuilt release you do not need to install Bun separately: the executable bundles the Bun runtime with the Loom CLI and browser UI. Install Git and OpenCode, then configure a model provider in OpenCode for Loom's primary workspace and task workflow. Additional supported CLI providers can be connected for chat after installation. This is a local-first application: the executable and workspace data stay on your device; the website does not host your workspace or act as a remote Loom server.

Release targets are macOS on Apple silicon and Intel, and Linux on x64 and arm64 with glibc; Alpine/musl is not published. Windows x64 is still being prepared, and its installer says so until a binary is published. The release CI starts the packaged daemon natively on every Linux and Intel macOS build; the Apple silicon build is cross-compiled on an Intel runner and starts on your Mac at install time, which the installer verifies before it writes anything.

Install Loom

Run the command above in Terminal on macOS/Linux, or PowerShell on Windows. The installer prints eight numbered phases, shows binary download progress, verifies SHA-256 (and size on Windows), checks that the executable starts, installs to your user folder, and updates your user PATH. It does not require administrator access.

The installer needs a published GitHub release. If it reports that no release is available, check GitHub Releases. This installs the Loom CLI and local browser workspace, not a native desktop app; run loom after installing to start Loom on your device. The installer does not build from source and never clones the repository onto your machine.

What the install log shows

Every run is a step-by-step log, so you can see what was detected, downloaded, verified and changed. The numbered phases are the same on macOS, Linux and Windows.

Phases 1 to 3 report your platform, the tools the installer itself needs, and the tools Loom needs afterwards (Git and OpenCode). Missing tools are reported with an install hint and never installed for you, so nothing outside ~/.loom changes without your decision.

Phases 4 to 6 resolve the published release, download the single binary for your platform with a progress bar, and compare its SHA-256 against the published manifest. A mismatch stops the run and nothing is installed.

Phases 7 and 8 run the new binary once to prove it starts on your machine, move it into place, and add its folder to your PATH. The final line prints the elapsed time and the next commands to run.

[1/8] Checking your system
[2/8] Checking the tools this installer needs
[3/8] Checking what Loom needs after the binary is installed
[4/8] Resolving the latest release on the stable channel
[5/8] Downloading the Loom binary
[6/8] Verifying the download
[7/8] Installing Loom
[8/8] Adding Loom to your user PATH

Open your workspace

Restart your terminal so it picks up the PATH change, then run Loom. It opens the local UI on 127.0.0.1:4317. The daemon continues running after the terminal command returns.

loom
loom doctor

Where it lives

Loom installs to ~/.loom/bin/loom on macOS/Linux and $HOME\.loom\bin\loom.exe on Windows. Its configuration, SQLite database, logs, cache, and managed worktrees stay under the same .loom directory.

For a custom location, set LOOM_HOME to an absolute path before installing and keep that environment variable set whenever you run Loom. Updating an existing installation uses loom update, rather than rerunning the installer.