Loom keeps your agents on track.

Tutorial 14: Use Loom from a second computer

Continue from Tutorial 13. Everything so far ran on one computer. Loom's memory lives on a server, not in that computer, so a second computer can read and write the same stores. This page connects a second computer and proves it by recalling a fact the first computer saved.

What you will accomplish

You need the first computer from Tutorial 00, and a second computer with a coding harness (Claude Code, Codex, or OpenCode) installed and signed in. Use the tutorial store [loom_demo] so nothing real is at risk.

> Private install: Everywhere this page says loom login, use > loom login --base https://<your-host> (or set LOOM_WEB_BASE), because your stores are on your > own server. If your server uses a self-signed certificate, first trust it as described in > Connect clients, and add the server's hostname to /etc/hosts if > it does not resolve.

1. Save a decision on the first computer

On computer A, start your harness inside the palmerpenguins checkout from earlier tutorials.

YouMake [loom_demo] the session default. Save one project decision: "Use the Adelie count of 152 as the reference value in all penguin checks." Confirm it was saved.
AgentThe agent loads [loom_demo] as the session default, saves one decision entity in the project scope, and reads it back.
ResultOne decision is saved and visible on read-back.

2. Install the CLI on the second computer

On computer B, install the shared Loom CLI with the installer for its operating system, then check it (Install the CLI).

loom --version

3. Sign in with loom login

loom login

Enter the same email address as on computer A. Loom shows the Terms and Privacy links and asks you to type I agree (there is no flag to skip it), then asks for the sign-in code that was emailed to you. Type the code at the hidden prompt. It is never shown on screen and must never go on the command line. Sign-in can take up to about a minute with no output while your stores are set up.

> Warning: Do not paste the sign-in code, or any part of ~/.loom/stores.toml, into a chat, > issue, or screenshot.

loom login signs in and writes your stores into ~/.loom/stores.toml (Windows: %USERPROFILE%\.loom\stores.toml). It does not change any harness. If you also want Loom wired into a harness on this computer, run loom setup instead; it signs in (unless ~/.loom/stores.toml already holds your credentials for the server, which on a new computer it will not) and then sets up the harnesses you select.

Existing store entries are never rebound, so signing in again is safe. If your account holds two stores with the same name, loom login keeps the oldest one and prints a Warning: store <handle> was not configured locally: ... line on stderr for the other; the exit status stays 0.

4. Confirm the second computer sees the same stores

loom list_stores

You should see the same store names as on computer A, including loom_demo. If you see a kanban store with a different name than on computer A, compare the store = lines of [kanban] on both computers; they must match. The list shows names and descriptions only, never key material.

5. Recall the decision from computer B

Start your harness on computer B (inside any checkout of palmerpenguins, or any repository).

YouMake [loom_demo] the session default. What project decision did we record about the Adelie count?
AgentThe agent loads [loom_demo] and queries decisions in the project scope.
ResultIt reports the decision from step 1: use 152 as the reference Adelie count. Neither the session nor the computer is the one that saved it; the store is.

That round trip is the point: memory belongs to the store, so any computer that holds that store's credentials shares it.

6. Sign a computer out

loom logout --params '{"section":"loom_demo"}'

This removes the section from this computer only (the result's server_status: "removed" refers to that local section, not to the server). It does not revoke the credential on the server, and the same credential on another computer keeps working. To destroy a store and its contents entirely, see Manage stores; that is a different, irreversible action.

Takeaways