[Feature Request] Self-hosted: full export/list API for extracted memories (currently only search-based recall)

Author: jy04819953Created Sep 9, 2026Updated Sep 10, 2026

Use case

Self-hosted users want to back up / migrate the extracted memory cards (the distilled facts the memory agent produces), not just the raw conversation documents.

Currently on the self-hosted server (v0.0.8):

  • documents.list + documents.get return the original session text — fine, but that's the input material
  • the extracted memories themselves have no list/enumerate/export endpoint — only top-K search recall (searchMode=memories), which can never enumerate everything
  • the on-disk store (data, SMD1 container) is encrypted with no documented export path

→ For a self-hosted user there is no reliable way to take a full, lossless backup of the distilled memory layer, or to migrate it to another system.

Request

Please add an endpoint / CLI that can list and export all extracted memories for a container (ideally with ids, timestamps, metadata), analogous to documents.list — e.g. GET /v4/memories with pagination, plus a plaintext export (JSON/Markdown).

Related

This would also help any user who wants portability/auditability of their memory layer, not just self-hosted deploys.

(Side note, since I'm here: the self-hosted server has been on v0.0.8 since 2026-08-17 — are there any plans for further self-hosted server releases/roadmap? I'd like to know how to plan around it. Thanks!)

Source: supermemoryai/supermemory