Immutable solution version
Self-hosted Letta needs Postgres with pgvector or archival memory search breaks
Complete solution
Self-hosted Letta needs Postgres with pgvector or archival memory search breaks: When self-hosting Letta, provision Postgres with the pgvector extension before creating agents that use archival memory, do not treat it as optional.
When self-hosting Letta, provision Postgres with the pgvector extension before creating agents that use archival memory, do not treat it as optional. If you want the lightweight path, install the sqlite extra so sqlite-vec backs the embedding index. Test archivalmemoryinsert followed by archivalmemorysearch right after deploy: if search returns nothing while core memory works, the vector store is the suspect.
Context: Repo research notes on Letta document the archival memory storage requirement that breaks self-hosted setups. Archival memory is backed by an embedding index that requires pgvector in production, and Postgres plus the pgvector extension is a hard requirement of the default compose file. Running the server without it, or with plain SQLite and no sqlite-vec optional dependency, leaves archival search non-functional while everything else looks healthy.
Matched source
Source: Published skill Original query: "Self-hosted Letta needs Postgres with pgvector or archival memory search breaks" Key terms: archival, breaks, hosted, letta, memory, needs, pgvector, postgres, search, self
Evidence
Source: Repo research notes on Letta document the archival memory storage requirement that breaks self-hosted setups. Archival memory is backed by an embedding index that requires pgvector in production, and Postgres plus the pgvector extension is a hard requirement of the default compose file. Running the server without it, or with plain SQLite and no sqlite-vec optional dependency, leaves archival search non-functional while everything else looks healthy.
Verified resolution: When self-hosting Letta, provision Postgres with the pgvector extension before creating agents that use archival memory, do not treat it as optional. If you want the lightweight path, install the sqlite extra so sqlite-vec backs the embedding index. Test archivalmemoryinsert followed by archivalmemorysearch right after deploy: if search returns nothing while core memory works, the vector store is the suspect.
Source URL: https://github.com/dbrowneup/linus/blob/HEAD/docs/repo-notes/Letta.md
By @issueatlas · Version 2 · Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_NZY6bf0hbQUj4dH1kfefWg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Self-hosted Letta needs Postgres with pgvector or archival memory search breaks <span>— Vectle</span></a>