durmem's memory lives on the server, not on the computer you saved it from. A second computer connected to the same account can read and write the same stores. This tutorial shows how to check that connection by recalling, on computer B, a fact saved from computer A.
You need:
Both computers use the practice store loom_demo and the project durmem practice notebook, so nothing real is at risk.
First complete Tutorial 01 on computer A. In a fresh session, use its neutral recall prompt and ask for the actual durmem reference of the Decision it reads:
loom_demo for this session. Then help me choose the most important work to do next for the project durmem practice notebook. Include the actual durmem reference for the Decision you used.loom_demo, identifies the relevant Goal, Roadmap item, and Decision, and gives the exact reference returned for that Decision. It does not save a duplicate.Keep that reference for comparison on computer B. Do not make up a reference or treat a sample value as one.
On computer B, follow the Quickstart: install the durmem command, then set up the harness you use there. For hosted durmem, run durmem setup; for a private server, run durmem setup --base https://durmem.ai with the same server address used on computer A. Choose the harness installed on computer B and sign in to the same account as on computer A.
Signing in alone is not enough. durmem setup also connects your harness, which installs the skills, the MCP connection, and the hooks described in Tutorial 00. Without them, the harness on computer B cannot use the stores even though this computer can reach them.
> Warning: Enter the emailed sign-in code only at the prompt that asks for it. Never paste the code, or any part of ~/.loom/stores.toml, into a chat, issue, or screenshot.
Start your harness on computer B and ask it to list the configured stores:
loom_demo.If the store is missing because you are signed out or its credentials need refreshing, sign in to the same account and server: run durmem login for hosted durmem, or durmem login --base https://durmem.ai for a private server. Do not rerun setup just to refresh sign-in; setup is for installing or repairing the harness integration, skills, MCP connection, and hooks. If those components are missing on computer B, run setup as in Step 2, including --base for a private server.
In a new session on computer B, in any repository, name the same store and project:
loom_demo for this session. Then help me choose the most important work to do next for the project durmem practice notebook. Include the actual durmem reference for the Decision you used.loom_demo, reads the project context without a pasted summary, and returns the exact durmem reference for the Decision it used.That round trip is the point: memory belongs to the store, so every computer connected to your account shares it.
When you stop using a computer, remove its local access to a store by name:
loom_demo store. Remove only that section, and confirm it is gone.loom_demo section on this computer only and lists the remaining stores. It never shows the removed credential.loom_demo. The other stores here are unchanged.Signing out is local: other computers keep working, and the store and its memory are untouched. To sign back in on this computer, run durmem login for hosted durmem or durmem login --base https://durmem.ai for a private server, using the same account and server. Run setup only if the harness integration also needs to be installed or repaired. To delete a store and everything in it, see Manage stores; that is a different, irreversible action.
durmem setup on each computer to connect its harness; signing in alone does not install the integration.durmem login with the same account and server. For private servers, include --base https://durmem.ai on every setup and login command.stores.toml as private.