Docs/Tools & Features/Memory

Memory

Dynamo remembers things across sessions. The model saves important facts automatically, or you can ask it to remember something specific.

Memory is the model's own running notebook — distinct from the curated, team-shared brief in `DYNAMO.md`.

Project memory is inside your repo and is not ignored for you. It lives at .dynamo/memory/, and Dynamo's managed .dynamo/.gitignore covers cache/, script-runs/ and *.tmp — not memory/. A plain git add -A will stage model-written memories. If you'd rather keep them out of the repo, add .dynamo/memory/ to your .gitignore; global memory (in your config dir) is outside the repo either way. Memory is never auto-promoted into DYNAMO.md; see DYNAMO.md vs Memory for how the two systems divide up.

Memory Tools

Tool	Description
`memory_save`	Save a fact, preference, or project note
`memory_list`	List all saved memories
`memory_read`	Fetch the full content of one memory
`memory_delete`	Remove a memory

Scopes

Memories are stored in two locations:

Scope	Location	Use for
Global	your Dynamo config dir (`~/.config/dynamo/memory/` on macOS/Linux)	Your preferences, feedback, references
Project	`.dynamo/memory/`	Project-specific context

Browsing Memories

bash

/memory                # list all saved memories (global + project)
/memory consolidate    # merge duplicates and clean up stale entries

How It Works

The model proactively saves memories when it learns lasting facts — your role, preferences, project decisions, and important context. Each memory is a markdown file with frontmatter (name, description, type).

Memory types:

●user — your role, preferences, knowledge
●feedback — guidance on how to approach work
●project — ongoing work, goals, decisions
●reference — pointers to external resources

Consolidation

Over time, memories can accumulate duplicates or become stale. Run /memory consolidate to trigger AutoDream-style consolidation — the model merges duplicates, resolves contradictions, and prunes outdated entries.

Manual /memory consolidate works on any plan. The automatic dream-on-startup loop is gated on both ai.auto_consolidate: true in dynamo.yaml (off by default) and a paid plan — and it isn't wired into session start yet, so setting the flag has no effect today. Run it manually when you want it.

To disable memory entirely: ai.memory: false in dynamo.yaml.

Skills Hooks