Loom Cloud lets you create multiple stores so projects, experiments, and coordination boards can keep separate memory boundaries. Free accounts can create up to five stores, and one agent can connect to several of them in the same session.
Start with Tutorial 00. Verify that Loom is installed and record the exact aliases returned for the default project store, writable tutorial store, and Kanban store. The current bundle normally names the latter two [loom_demo] and [kanban]; use the discovered names below. Add or delete a hosted store only on the Loom Cloud store page. An agent can connect to a store already in your installed bundle, but it cannot create a hosted store from a prompt.
Store names come from the installed bundle. Ask Loom to list its stores rather than assuming any literal name. If the expected default, writable tutorial store, or Kanban store is missing, stop and install the current signed-in bundle instead of redirecting tutorial writes to a similarly named store.
loom_demo the session defaultloom_demo and make it the default for this session only. Confirm the effective session default, and do not edit ~/.loom/stores.toml.loom_demo store and changes only this session's default routing.loom_demo is now the default for this session. Persistent configuration was not changed.Each store is a memory boundary with a distinct purpose. Describing the stores first prevents project facts, tutorial experiments, and coordination events from being written into the wrong place.
[loom_demo], and [kanban].[loom_demo], and [kanban].[loom_demo] is the writable tutorial store, pre-seeded with a small set of starter facts (plus whatever the tutorials have saved so far, if you have run them). [kanban] is the multi-agent coordination store. All three are reachable and ready for their intended use.Store listing is the first orientation step because it shows the names and registry descriptions available in this installed bundle. Asking Loom to describe a store is the first live health check because it confirms the store is reachable and explains what it is for.
One agent may need project memory and a coordination board at the same time. This step shows that connecting to a second store does not silently redirect calls intended for the session default.
loom_demo as this session's default, load and describe [kanban], then unload [kanban] without changing the session default.loom_demo session default in place, loads [kanban], explicitly describes it, then disconnects the named Kanban connection.[kanban] loaded successfully and identifies itself as the multi-agent coordination store. I then unloaded its named connection. loom_demo remains the effective session default.An agent can stay connected to several stores at once. Named-store reads do not change the session default unless you explicitly ask for that change, and the active session-default store cannot be unloaded until another named store becomes the session default.
Use the Loom Cloud store page when a new project or experiment needs its own memory boundary beyond the starter stores. This website is the only place to create a hosted store. The word load means connecting this session to a store that already exists; loading never creates or provisions one. After creating the store on the website, install the updated bundle locally, then ask Loom to list its stores and confirm the new name appears.
This optional walkthrough uses a disposable store named [research]. Creation and deletion are irreversible account operations, so skip the walkthrough if you do not want a temporary store.
research on the Loom Cloud store page.[research] is present.Then reset the connection without trying to unload the active session default:
stores.toml. Then load [research], describe it using its live registry description, unload it, and confirm the primary coding store remains the session default.loom_demo default first, then loads, describes, and unloads [research]. It does not require an exact hard-coded description.[research] loaded successfully and its live description identifies the store that was just created. I unloaded it; the primary coding store remains available, and the session default is unchanged.Use the live capacity status rather than assuming a fixed account-wide limit. If you skipped creation, skip the deletion check in §5 too.
The signup bundle includes [kanban] as a ready-to-use coordination store. Agents use the loom-kanban skill so claims, reviews, and handoffs stay consistent while several sessions work from the same board.
loom-kanban, register this conversation, and scan [kanban].[kanban], and the live scan completed successfully. I found <the claimable/reviewable action taken, or no suitable work>.The result is state-dependent: an empty board is not required for this check to pass. Registration plus a successful complete scan-and-act flow is the invariant.
Use a separate Kanban store only when a project needs an independent coordination boundary.
This step only verifies the board connection. Refer to Tutorial 10: Coordinate multiple agents for atomic claims, cooperative start-window self-checks, dependencies, review, and revision.
Deleting a hosted store is irreversible. It can only be done from the Loom Cloud store page; the agent cannot delete hosted stores for you.
The local bundle is the agent's store registry, so installing the updated bundle is what removes the deleted store from future sessions. This verification checks the registry without performing another destructive action.
[research] store in Loom Cloud and installed the updated bundle. Confirm that it is no longer available.[research] is listed. It does not attempt another destructive operation.[research] is absent from the installed bundle. The primary project store, [loom_demo], and [kanban] remain available.If a removed store still appears, install the current bundle from Loom Cloud or follow the website-provided cleanup instructions.
[loom_demo] for starter tutorial examples.[loom_demo] store is the tutorials' working store: it starts with sample facts and accumulates what you create; reruns are expected to find prior work there.[kanban] for tutorial and real-work multi-agent coordination.