One agent can work with several durmem stores in the same session: real project memory, the practice store, and others you create for experiments. Each store is a separate memory boundary, so facts written to one never appear in another. This tutorial shows how to target a store on purpose and how to create and delete a disposable one.
Start with Tutorial 00 and Tutorial 01. Addresses on this page use durmem.ai, your durmem server's address; replace it with your server's host name if you are reading the raw file.
~/.loom/stores.toml, such as [loom_demo]. It tells this computer how to reach one store. Prompts in these tutorials name stores by their section name.stores.toml; you can change it for one session without editing the file.durmem setup registered for real project memory. durmem keeps it connected, so the agent cannot unload it.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.> Illustrative agent output: loom_demo is now the default for this session. Persistent configuration was not changed.
Describing the stores first prevents project facts and tutorial experiments from being written into the wrong place. Store names come from your account, so ask durmem rather than assuming any name.
loom_demo.loom_demo.> Illustrative agent output: Your primary project store is your coding store; it starts nearly empty on a fresh account and grows as you work. loom_demo is the practice store. It starts with a few sample facts and keeps whatever the tutorials have saved so far. Both are reachable.
Describing a store is a live check: it confirms the server answers and reports the store's purpose and domain. If an expected store is missing, stop and sign in again with durmem login (for a private server, durmem login --base https://durmem.ai) rather than sending tutorial writes to a store whose name looks close. Use durmem setup only to repair skills or the MCP integration, not to refresh stores.
One agent may need two stores at the same time. This step shows that connecting to a second store does not silently redirect calls meant for the session default.
loom_demo as this session's default. Load my primary project store by name, describe it, and confirm that loom_demo is still the session default.loom_demo session default in place, loads the primary store by name, and describes it.> Illustrative agent output: Your primary project store is connected and described. loom_demo remains the effective session default.
Reads and writes that name a store go to that store; everything else still goes to the session default. Naming a store never changes the default unless you ask for that change.
durmem refuses to unload three kinds of connection: the reserved default name, your primary store, and the store that is currently this session's default. To disconnect a store that is the session default, first make another store the default.
When a project or experiment needs its own memory boundary, create a store. Ask your agent to create it, or use the Stores page of your durmem web app (https://durmem.ai/stores). Creation sets the store up on the server and adds its section to ~/.loom/stores.toml for you. The full create and manage steps are in Manage stores.
> Note: durmem cannot create your first store. The first stores come from durmem setup; creating more uses an existing store's credentials to sign the request.
This optional walkthrough uses a disposable store named research. Creation and deletion are real account operations, so skip §3 and §4 if you do not want a temporary store. Your account has a store limit. The server reports it when creation is refused, so check that message rather than assuming a number.
If a research section already exists in ~/.loom/stores.toml, creation is refused before the server is contacted. Choose another name or inspect the existing entry; do not replace it blindly.
research for experiments. Then list my stores and confirm research is present. Do not load it yet.stores.toml.> Illustrative agent output: The research store was created and its section is now in stores.toml. Its description comes from the server.
If the server reports that the store was created but its section could not be saved on this computer, do not create it again. Run durmem login with the same server (for a private server, durmem login --base https://durmem.ai) to recover the locally missing section. durmem setup is for integration repair, not a store refresh. See Manage stores.
Now load the new store, then disconnect it. Because loom_demo is the session default and research is not, research can be unloaded directly:
research by name, describe it, unload it, and confirm that loom_demo is still the session default.research. The session default is never touched.> Illustrative agent output: research loaded and described itself as the store just created. I unloaded it; loom_demo remains the session default.
If creation is refused because you reached your store limit, delete a store you no longer need (§4).
Deleting a store destroys its data on the server and cannot be undone. It is a command you run yourself, deliberately named so that it cannot be mistaken for a read:
durmem drop_store research --confirm research--confirm must repeat the store's own name. The command deletes the store on the server and then removes its section from ~/.loom/stores.toml. You can also delete a store from the Stores page of your durmem web app. For the full store-management steps, see Manage stores.
> Warning: An agent must not run durmem drop_store unless you explicitly ask it to delete a named store in that conversation. Never let an agent infer which store to drop.
Then check the result without performing another destructive action:
research store. Confirm that it is no longer available.research is present. It does not attempt another deletion.> Illustrative agent output: research is no longer configured. Your primary project store and loom_demo remain available.
If the command exits with status 3, the outcome is unknown: the store may or may not have been deleted. Do not rerun the command automatically. Open the Stores page of your durmem web app first:
research is gone there, ask the agent to sign out the research section on this computer so the leftover entry is removed.research is still listed, it was not deleted. Decide again, deliberately, whether to delete it.See Troubleshooting if the web app and the command disagree.
default name, and the current session default cannot be unloaded.loom_demo for tutorial examples; it keeps what earlier tutorials saved.~/.loom/stores.toml for you.