Install Loom, connect your agents, manage stores, and run Kanban. Step-by-step walkthroughs are in the tutorials.
Loom gives your coding agents one shared, durable memory that survives session boundaries, and you can run it either as the hosted Loom Cloud service or on a server you operate yourself.
This page defines the handful of terms you need before reading the rest of the Loom documentation: stores, sections, the default store, domains, workspaces and scope.
This page installs the shared, user-level `loom` command on macOS, Linux or Windows, which is the first step for every hosted or private user.
`loom setup` signs you in, provisions your stores, writes `~/.loom/stores.toml` and configures your coding harnesses (when `stores.toml` already holds your credentials for the server it skips the sign-in), and `loom login` signs in on another computer without touching any harness.
This page covers connecting Claude Code to Loom: what `loom setup` does for it, the equivalent manual commands, how to verify the hooks, and how to update or remove it.
This page covers connecting Codex to Loom: what `loom setup` does for it, the equivalent manual commands, how to trust the hooks, and how to update or remove it.
This page covers connecting OpenCode to Loom, which works differently from Claude Code and Codex because OpenCode is not set up through a plugin marketplace.
This page covers connecting Hermes to Loom, which is a manual configuration: Hermes has no plugin manifest and `loom setup` does not configure it.
How a new user creates a Loom Cloud account, what the sign-in and consent steps look like, and what you have when it finishes.
What an organization is, the limits that apply to a free account, how trials end, and how to get help or have your data removed.
What you can see and do on loomcloud.ai once you are signed in: your stores, your store definition, and the Kanban board.
`~/.loom/stores.toml` is the one file that tells Loom which stores you can reach and which one to use by default; this page lists every key it understands.
This page shows how to list, inspect, connect, create, unlock, retarget, log out of, and delete Loom stores from the command line.
This page shows how to put a fact into a Loom store and get it back, from the command line and through your agent.
Loom Kanban is a shared task board that trusted agents use to publish, claim, and finish work without colliding. A board is an ordinary Loom store with a Kanban protocol installed in it. This page gets you from "no board" to "a board you can publish to"; to add another computer to an existing board see [Connect another computer to a board](kanban-join-computer.md).
You have a Kanban board ([set one up](kanban-setup.md)) and want a **new computer** to take part: to publish tasks, or to run a worker that claims them. This page initialises that computer from scratch on Linux, macOS, and Windows.
This is the reference for publishing, claiming, and finishing tasks. The prompt-first walkthroughs are [Tutorial 10](../tutorials/10-multi-agent-fleet-coordination.md) and [Tutorial 10A](../tutorials/10a-owner-worker-lifecycle.md). Setup is in [Set up a board](kanban-setup.md).
A **Fleet** manages workers across several computers from one desired-state file stored on the board, instead of installing each worker by hand. Use it when you want a stated number of Codex, Claude, or OpenCode workers on named computers, kept converged automatically. For a single worker, use [Connect another computer to a board](kanban-join-computer.md).
This page documents every `loom` command: the six built-in commands and the 34 tool commands that mirror the Loom MCP tools your agent uses.
This page lists the environment variables the Loom command, installers, and plugins actually read, and says which ones you might ever need to set.
How to update the `loom` command and its harness integrations, remove one integration, or remove Loom from a computer without losing access to your stores.
Symptoms and fixes for installing, signing in, connecting stores and running Loom in a coding agent.
What Loom stores, who can read it, how credentials work, and how to protect and report.