Skip to main content
Presentation memory helps AI-assisted editing retain relevant context across changes to the same presentation. Self-hosted Presenton uses Mem0 OSS with local vector and history storage under /app_data by default.

​
Default configuration

The official container includes the required spaCy model. The embedding model may be downloaded on first use, so restricted or offline deployments should pre-populate the required cache.

​
Memory model

Mem0 also needs an OpenAI-compatible text endpoint for extracting useful memories:
The memory model can differ from the model that creates presentations. Confirm that a container can reach the configured URL; localhost inside Docker does not refer to the host.

​
Persistence and privacy

  • Keep MEM0_DIR inside the persistent /app_data mount.
  • Include memory data in backups and protect it like presentation content.
  • Hosted memory-model endpoints receive the context sent for memory extraction.
  • Set MEM0_ENABLED=false when iterative memory is unnecessary or the workflow must avoid that processing.

​
Troubleshoot

Check application logs for missing spaCy or embedding models, unreachable endpoints, invalid dimensions, and filesystem permission errors. After changing the embedding model or dimensions, use a clean compatible collection rather than mixing incompatible vectors.