Connect a coding harness to durmem, save one harmless project memory, and recall it in a fresh session. This route uses hosted durmem by default.
The command is now durmem (it was loom).
Before starting: a harness is your coding application (Claude Code, Codex, or OpenCode); the local durmem CLI connects it to a durmem server. Your account grants access to a store, a separate memory database on that server. A fact is one remembered claim. The harness uses MCP, the connection protocol, to reach the server. A hook is a harness callback that can bring relevant durmem memory into a session; a working MCP connection alone does not prove hooks are trusted or ran.
You need a supported computer, a terminal, one of those harnesses installed and signed in, and access to a durmem server. If your harness is not installed, install it and sign in with its own instructions first; harness sign-in and durmem sign-in are separate.
On macOS or Linux, have python3, tar, curl or wget, and sha256sum or shasum available. On Windows, use PowerShell and tar; the installer supplies uv and Python. See Install requirements for details.
The commands below use https://durmem.ai as the server origin. On the published docs site, the server fills in that origin. If you are reading this raw repository page, replace the whole https://durmem.ai origin (not just durmem.ai) with your server's HTTPS origin. For durmem, use https://durmem.ai; for a private server, use its HTTPS host and any nondefault port your administrator gave you.
The installer downloads and verifies the local CLI. It does not install a durmem server. Choose the command for your computer:
curl -fsSL https://durmem.ai/.well-known/cli/install.sh | shirm https://durmem.ai/.well-known/cli/install.ps1 | iexFollow the installer's PATH instructions, then open a terminal that can find durmem:
durmem --versionSuccess: the command exits successfully and prints the installed CLI version.
Run setup for the server you intend to use:
durmem setup --base https://durmem.aiSetup asks which installed coding harnesses to configure, signs in when needed, and installs and verifies the durmem integration. Enter any sign-in code only at the hidden prompt, never in a command or message. Setup does not install the coding application itself.
Check that the stores you expect are listed:
durmem list_storesSuccess: setup reports the selected harness configured, and the list shows the practice store you will use. This list is local connection configuration, not proof of server-side data.
If loom_demo is missing, do not choose a similarly named store. Sign in to the same account on the intended server: use durmem login --base https://durmem.ai for hosted durmem, or durmem login --base https://durmem.ai for a private server. Follow any restart instruction it prints, then start or reselect the harness session and run durmem list_stores again. If that account has no loom_demo store on that server, ask its administrator which safe practice store to use.
Follow any restart instruction printed by durmem setup or durmem login. If it asks for a restart, start a fresh harness session. Follow the relevant trust or connection check in Install and set up durmem. In short: Claude Code's /hooks shows registered durmem hooks; in Codex, trust the hooks only after confirming they come from loom@loom; OpenCode's opencode mcp list checks its durmem connection. A connected MCP server by itself does not prove that hooks are trusted or ran.
Success: after following the printed next step, the selected harness shows its durmem connection and any required hook trust step is complete. If not, stop and follow the troubleshooting guide.
A project scope is a name attached to a memory to show which project it applies to; merely opening a folder does not choose it. For this practice, use the loom_demo store and the project scope durmem practice notebook.
Ask your harness:
For this session, use the durmem practice store
loom_demoand project scopedurmem practice notebook. Remember this harmless practice fact: “This is a disposable durmem quickstart memory.” After saving it, give me the actual fact identifier or reference returned by durmem for this fact. Do not invent one.
Success: the harness confirms this exact fact was saved in the named store and project, and gives the exact fact identifier or reference from durmem's save result. Keep that returned value for the fresh-session check; do not treat a generic “remembered” reply or a made-up identifier as evidence. If it reports a different store or scope, stop and correct that before continuing.
Open a completely new session. Keep the exact reference returned in step 4 for comparison, but do not give it to the harness before it recalls the fact. Tell the harness to use the same loom_demo store and durmem practice notebook project scope, then ask:
What did I ask you to remember for the durmem practice notebook? Include the actual durmem reference for the stored fact you found.
Success: the harness recalls “This is a disposable durmem quickstart memory” without you repeating it, cites the actual stored reference returned by durmem, and uses the same store and project scope. Compare that reference with the value you kept from step 4; do not invent or guess an identifier. If it cannot recall the fact, check the connection and scope before trying to save it again.
Next, read the overview for the concepts, or try Tutorial 01 for a longer practice path. For a connection check, see Tutorial 00.