Configuration
Engram works out of the box with sensible defaults, but you can customize its behavior through environment variables and configuration files.
Storage Location
Section titled “Storage Location”By default, Engram stores its SQLite database at:
~/Library/Application Support/engram/memory.dbOverride with the ENGRAM_DB_PATH environment variable:
export ENGRAM_DB_PATH="/path/to/custom/memory.db"Embedding Model
Section titled “Embedding Model”Engram uses paraphrase-MiniLM-L6-v2 for semantic embeddings (384 dimensions). The model runs locally — no API calls needed for embedding generation.
Project Scoping
Section titled “Project Scoping”Memories are scoped by project. When your AI stores a memory, it tags it with the current project name. Recall automatically filters by project scope, but also includes global memories.
- Project-scoped: Architecture decisions, file paths, patterns specific to a codebase
- Global: User preferences, cross-project conventions, workflow settings
Importance and Expiry
Section titled “Importance and Expiry”Memories support an importance field (1-5) that boosts recall ranking. You can also set expires_in_days for temporal context that auto-expires from recall results.
Next Steps
Section titled “Next Steps”- Claude Code Setup — Configure Claude Code for the best experience
- Tools Reference — Browse all 22 MCP tools