Get Loom

YOUR MACHINE. YOUR WORKSPACE.

A clear desk for
parallel agents.

Give your ideas a plan. Let OpenCode agents work side by side. Bring it all together with a review you can trust.

Install Loom Take a look at the docs

macOS · Linux · Windows in preparation / Built with Bun

From a plan to a reviewed change.

Less window switching.
More of the work that matters.

Git worktrees Provider-backed chats Human approval

A PLACE FOR THE WHOLE PROCESS

Follow the work.
Keep the context.

Your plan, conversations, and changes belong together. Loom gives them a shared home.

loom / workspace Local workspace
Loom workspace showing the project and session sidebar, a chat session with its composer, and the Agents and tasks rail with running and idle counts
Your work, in one place

Move from an idea to a working branch without losing track of the conversation.

Captured in Loom

BUILT FOR WORK THAT HAS MOVING PARTS

Give the agents space.
Keep yourself in control.

How parallel work works

Isolated workspaces

A workspace for every task.

Each task works in its own Git worktree. Independent agents can make progress at the same time.

Dependency-aware planning

The right order, built in.

Plans make dependencies explicit. Dependent tasks wait for the work they need and receive its context.

Integration & review

Your branch. Your call.

Loom brings task branches together, runs your checks, and presents a diff for approval before merging.

Multi-chat workspace

Keep workstreams in reach.

Open separate chat tabs, split the view, and keep conversations for different parts of a project easy to switch between.

Provider choice

Choose the right runtime.

Use OpenCode for the primary workspace flow, or route chat through a connected Claude Code, Codex CLI, or Antigravity CLI provider.

Workspace tools

See the work around the chat.

Keep project files, terminal sessions, agent activity, and available context close to the conversation.

ONE IDEA. THREE DELIBERATE STEPS.

A little structure.
A lot less juggling.

Start with a repository and a goal. Stay as involved as the work requires.

Your first project
  1. 01

    Make the plan yours.

    Create a plan. Review the proposed tasks, adjust dependencies, and approve the commands that will validate the result.

  2. 02

    Let independent work move.

    Agents work in isolated branches. Follow the Kanban board, read the chat, and respond when an agent needs permission.

  3. 03

    Bring it home, thoughtfully.

    Inspect the task changes and check results. Merge each task when you are happy with what you see.

LOCAL BY DEFAULT

Your repositories stay on your machine.

Loom keeps project and task data locally. Messages, selected files, and tool context may be sent to the provider selected for that chat or task.

Read the privacy details

A SMALL START FOR YOUR NEXT BIG THING

One command.
Your own workspace.

Install Loom, then open it with loom. Git and OpenCode are the prerequisites. Loom itself runs on Bun, bundled with the release.

Want the website as an app shortcut? Use your browser menu to install Loom Workspace. The shortcut opens this public site; the CLI install below sets up Loom locally.

Full installation guide
Terminal
curl -fsSL https://loomworkspace.bond/install.sh | sh

Run this in Terminal or PowerShell. The installer prints each step and download progress.

Direct downloads
Install log preview
  1. [1/8] Checking your system
  2. Platform linux-x64 (x86_64, kernel 6.18.26)
  3. install target ~/.loom/bin/loom
  4. data directory ~/.loom
  5. release channel stable
  6. [2/8] Checking the tools this installer needs
  7. curl 8.14.0
  8. sha256sum found
  9. [3/8] Checking what Loom needs after the binary is installed
  10. git 2.54.0 — worktrees and task branches are ready
  11. opencode not found — Loom runs chat and Kanban tasks through OpenCode
  12. Bun, Node.js and npm are not needed: the release bundles the Bun runtime with the UI.
  13. [4/8] Resolving the latest release on the stable channel
  14. GET .../releases/download/channel-stable/manifest.json
  15. Loom 0.1.0 for linux-x64 (48.2 MB)
  16. [5/8] Downloading the Loom binary
  17. [###########.............] 42% 20.3 MB / 48.2 MB
  18. [######################..] 100% 48.2 MB / 48.2 MB
  19. Downloaded 48.2 MB in 12s (4.0 MB/s)
  20. [6/8] Verifying the download
  21. expected sha256 4f2a9c1e8b7d0a53…
  22. actual sha256 4f2a9c1e8b7d0a53…
  23. SHA-256 verified for 48.2 MB
  24. [7/8] Installing Loom
  25. Executable answers: loom 0.1.0
  26. Installed to ~/.loom/bin/loom (mode 700, no administrator access used)
  27. [8/8] Adding Loom to your user PATH
  28. Wrote PATH entry to ~/.profile
  29. Loom 0.1.0 installed successfully in 21s.
  30. next restart your terminal, then run: loom

Nothing is built or cloned on your machine: the installer downloads one published binary, verifies its SHA-256, then writes it into ~/.loom. Missing tools are reported, never installed for you.

What gets installed?
  1. Detects your OS, CPU architecture and libc.
  2. Checks the tools Loom still needs after install: Git and OpenCode.
  3. Downloads the published release binary over HTTPS with a progress bar.
  4. Verifies SHA-256 before installing the bundled Bun-powered executable.
  5. Installs Loom to your user folder and adds it to PATH.

Loom uses Bun as its JavaScript runtime; the release bundles Bun, so users do not need to install it separately. Install Git and OpenCode, then configure an OpenCode model provider to use the workspace. The command-line installer does not install a native desktop app; Loom opens its local browser workspace after you run loom.

Published targets: macOS on Apple silicon and Intel, and Linux on x64 and arm64 with glibc. Windows x64 is being prepared, so the PowerShell installer reports that clearly instead of failing on a missing download.

You can also install this website from your browser menu as a shortcut. That installs the public product site, not the local Loom workspace or daemon.

See platform requirements and troubleshooting.

Bun runtime included Verified downloads

Installers use published GitHub Releases. Availability and platform requirements are listed in the docs.

BEFORE YOU GET STARTED

A few useful details.

Do I need to install Bun?+

Loom is built with Bun, and the release bundles Bun's runtime with the executable and browser UI. You do not need to install Bun, Node.js or npm separately. You will need Git and OpenCode available on your PATH for Loom's primary task workflow. For chat, you can also connect supported Claude Code, Codex CLI, or Antigravity CLI runtimes.

Can I install the site?+

Yes, your browser can install or pin the public Loom product site as an app shortcut. That is only the website; the Loom workspace is installed separately on each user's device with the command-line installer and runs locally.

Can I use my existing repository?+

Yes. Add the path to a local Git repository with at least one commit. Loom creates separate worktrees for tasks. Keep your main checkout clean before approving a merge.

Does Loom choose my model?+

You choose a connected provider and model in chat. Custom agents can have their own provider and optional model. Loom's task workflow uses OpenCode; provider usage and charges follow the provider selected for each request.

Does the selected agent stay the same for every message?+

The model, custom agent, and thinking mode are selected for each message. You can switch them during a conversation, so check the composer before sending if you want to keep using the same setup.

What happens when changes conflict?+

Integration happens in a separate workspace. A resolver can propose a fix, and checks run again. The combined diff still needs your approval before it reaches your project branch.