Start with the quickstart: install the local command, connect a coding harness, and save and recall one harmless project memory. This page explains the ideas behind that route and points to the next guide or practice exercise.
| Term | Meaning |
|---|---|
| Harness | The coding application you work in, such as Claude Code, Codex, or OpenCode. |
| CLI | The local durmem command used to install and connect durmem. It is separate from the server. |
| Server | The durmem service that stores and retrieves memories for accounts that can reach it. |
| Account | The sign-in that grants access to a server and its stores. |
| Store | A separate memory database on a durmem server. |
| Fact | One claim the agent remembers, such as a project decision. |
| Project scope | A name attached to project memories so a later session can find context for the same work. Opening a folder alone does not select a scope. |
The harness connects to the server through MCP, a connection protocol. durmem skills guide the agent in using memory; lifecycle hooks can bring relevant context into a session. A working connection alone does not prove that hooks are trusted or ran.
| Hosted durmem | Private server |
|---|---|
| durmem operates the service; you do not install a server. Begin with the quickstart. | Your organization operates the service. Ask its administrator for the HTTPS address and any certificate or sign-in instructions. Users joining an existing server can follow the same quickstart; server operators have a separate installation guide. |
Guides explain concepts and repeatable tasks. Tutorials let you practice them with an observable result. A tutorial may briefly remind you of a prerequisite and link back to the guide; it should not make you guess why a command is needed.