Start with the durmem quickstart, then choose a practice track. A tutorial number is a stable page name, not a requirement to finish every earlier page.
Examples use harmless practice data. Prompts and outputs illustrate a method; verify the actual saved records and results. Tutorial 12 uses the public palmerpenguins repository for a bounded coding audit.
Check the configured connection and distinguish MCP access from effective hooks.
Save a harmless project fact and recall its actual reference in a fresh session.
Connect one agent to multiple stores while keeping each memory boundary clear.
Give durmem enough project context to return the right memory at the right time.
Learn how entities, relations, and built-in types turn notes into connected knowledge.
Save standing rules and evidence-bearing observations, then preview a reminder without executing its action.
Distinguish actual hook context, manual retrieval, handoffs and optional compaction capture.
Reuse or declare a fact type and distinguish once-valid prices from false claims using synthetic history.
Check current decisions and intended work before drafting a compatible plan.
Verify a parameterized method against an identified data snapshot and call it from a fresh session.
Coordinate owner decisions, dependencies, leases, messages, and truthful task boundaries.
Split independent work and use one owned two-run review with live different-harness checks.
Inspect host convergence and worker health separately, then choose the authorized cleanup layer.
Audit one synthetic work item, decide on a bounded repair, and verify the result without inventing delivery.
Practice with fictional personal context in a separate PersonalDomain store.
Connect a second computer and recall the same practice project from the same store.
Use a dedicated board and one scheduled worker to complete and close a read-only task.