Learn

How memory works

A local SQLite file and an on-device embedding model. Nothing you store leaves your machine.

Store & recall

Code

remember({content: "User prefers pnpm",namespace: "user",tags: ["preference"],priority: 8}) recall({query: "package manager",namespace: "user",preview: true})

remember stores a fact and skips it if a near-identical one is already in that namespace.

recall({ preview: true }) returns short summaries first; load the ones you need in full with recall({ id }).

Namespaces

One file, separate shelves

userYour preferences — follows you into every project“prefers pnpm”
my-projectOne repo’s decisions, errors and code indexsame name as code(ingest)
workContext that spans several repos“staging deploys on Fridays”

A call reads one namespace. To search several at once, pass namespaces: [...] or a declared group.

Skills vs memories

skill

How to do something

Give it metadata.skill_name and load it by name with recall({ item_type: 'skill' }) — a direct lookup, no search.

memory

Something that's true

Facts, preferences and decisions — found by search when they're relevant.

Storing a fact doesn't make it true. To check claims against what's stored before an agent repeats them, see Grounded facts.

Something missing or wrong? Email support@memorylayer.in or open an issue.

DocsLearn