local-first memory for AI agents

A shared memory store for Claude Code, Cursor, and every agent you use

All agents read and write to the same store that lives on your machine, in a folder you can copy, inspect, and take anywhere.

npx memloom initGitHubdocs

setup in 60 seconds

In your terminal before your coffee cools

One command, and everything you tell one tool, every tool knows. CLI, MCP, a browser viewer, plain HTTP: all reading and writing the same store on your machine.

Save it once, find it from any wording. And exact identifiers still work: pg_hba.conf finds the memory that mentions it.

terminal
$

one store, every client

Every agent, one brain

What Claude Code learns on Monday, Cursor knows on Tuesday. One daemon owns the store; everything connects to it.

MCP

Claude Desktop, Claude Code, Cursor. Agents save and recall as they work.

CLI

save, recall, context add, history. You, in a terminal.

viewer

The graph, your documents, every memory and conflict, and a chat that answers from all of it. Served by the daemon itself.

HTTP + Postgres

A local API for your own tools, and a real Postgres wire for psql or Drizzle Studio.

context

Your context joins the memory

Ingest your existing context: markdown, text, or PDFs as single files or folder and then just ask about it.

the belief pipeline

Agents that remember without a mess

A memory store agents write to constantly becomes a mess unless something curates it and resolves contradictions.

duplicates merge

The same fact saved twice stores once. Agents can save freely; the store stays clean.

beliefs have history

A reworded or edited fact becomes a new version. The old one stays in history, never overwritten.

contradictions ask you

Two memories that can't both be true are kept, flagged, and resolved by a human. Every resolution is reversible.

typed, not a pile

Facts, preferences, episodes, procedures. The same taxonomy across every client, filterable in the viewer.

ask your memory

Built-in assistant

Ask questions in plain language about your memories and context. Every claim links to the memory or file passage it came from, one click from its place in the graph.

ownership

Leave whenever. Everything comes with you.

Your memory is a folder: ~/.memloom/data. Copy it and that's a backup. Point psql at it and that's an audit. Delete it and it's gone.

No account. No telemetry. The only network calls go to the embedding provider you configure, and it runs fully offline if you'd rather it call nothing at all.

It's not a total black box, either. When indexing runs you can watch it stream, line by line, in the console.

coming soon

memloom cloud

Hosted memory with zero setup: no API key hunt, synced across your machines and agents. One command pulls everything home to a local folder. The exit is a feature.