Memento

A local-first, LLM-agnostic memory layer for AI assistants

Every AI session starts the same way: re-explaining your preferences, your project's conventions, the decisions you made last week, the dead-ends to avoid. Each tool solves this in its own siloed way (CLAUDE.md, .cursorrules, copilot-instructions.md, ChatGPT Memory) — but you, the human, are the one constant. Your memory shouldn't fragment across vendors.

Memento is one place where that memory lives. It runs an MCP server over a local SQLite file, so any MCP-capable AI assistant — Claude Desktop, Claude Code, Cursor, GitHub Copilot, Cline, OpenCode, Aider, a research bot, a custom agent — can read and write durable, structured memory about you, your work, and your decisions. Local-first, no outbound network calls by default, no vendor lock-in.

Quickstart

Three steps from zero to a working memory layer:

1. Initialize Memento

npx @psraghuveer/memento init

Creates the database under the XDG default ($XDG_DATA_HOME/memento/memento.db, typically ~/.local/share/memento/memento.db on POSIX), runs migrations, and prints copy-paste MCP snippets for every supported client. Idempotent — re-run any time to reprint the snippets.

2. Connect your AI client

init prints, for each client, either a one-line subcommand (e.g. claude mcp add memento … for Claude Code) or a JSON snippet to merge into the client's MCP config (Claude Desktop, Cursor, Cline, VS Code Agent mode, OpenCode). Pick the one for your client, paste it, then restart the client so it loads the new MCP server.

The full per-client walkthrough lives in docs/guides/mcp-client-setup.md.

3. Teach your assistant when to use Memento

Memento exposes the MCP tools, but the assistant still needs to know when to call them. Two paths, depending on your client:

• If your client loads Anthropic-format skills: install the bundled Memento skill. One cp -R command, printed by init, copies it into ~/.claude/skills/ — the path most skill-capable clients read from. (A few use a client-specific directory; check your client's docs and re-target the cp if the skill doesn't pick up after a restart.) Restart the client; the skill auto-loads on intent match.
• If your client doesn't support skills: paste the persona snippet from docs/guides/teach-your-assistant.md into your client's persona file (.cursorrules, custom system prompt, etc.).

That's it. Verify with npx @psraghuveer/memento doctor --mcp (scans known client configs and flags shape mismatches) and try a fresh session: "Remember that I prefer pnpm over npm for Node projects." In the next session, ask "What's my preferred package manager?" and the assistant should recall it without you re-explaining.

Getting started

Prerequisites. Node.js ≥ 22.11, and a C/C++ toolchain so better-sqlite3 can compile on platforms without a prebuild (Xcode command-line tools on macOS, build-essential on Debian/Ubuntu).

Run init once to set things up:

npx @psraghuveer/memento init

init defaults the database to the XDG data dir; pass --db /custom/path/memento.db (or set MEMENTO_DB=/custom/path/memento.db) if you want a non-default location.

To run the server directly (e.g. for debugging):

npx @psraghuveer/memento serve

The server listens on stdio for MCP requests. To pass extra flags (e.g. a custom database location):

npx @psraghuveer/memento serve --db ~/.local/share/memento/memento.db

You can also point at an existing database with the MEMENTO_DB environment variable.

Verify the install by running npx @psraghuveer/memento doctor (add --quick to skip the DB and embedder probes; add --mcp to also scan known MCP client config files). For a one-screen summary of what's in your store, npx @psraghuveer/memento status. To inspect what your install can do — registered commands, current config, database location — without speaking MCP, run npx @psraghuveer/memento context. To smoke-test the MCP transport end-to-end, npx @psraghuveer/memento ping.

Wiring Memento into an MCP client (Claude Desktop, Claude Code, Cursor, Cline, OpenCode, VS Code Agent mode, …) is covered step by step in docs/guides/mcp-client-setup.md. The TL;DR is the three-step quickstart above: init, paste the snippet, install the skill or paste the persona.

Vector retrieval (paraphrase matching on top of FTS) is on by default. The first search triggers a one-time model download (~110 MB) into $XDG_CACHE_HOME/memento/models (or ~/.cache/memento/models / %LOCALAPPDATA%\memento\Cache\models); after that, both FTS and vector arms run automatically. If the model has not yet downloaded, search degrades gracefully to FTS-only. For configuration options and library-wiring details, see docs/guides/embeddings.md.

Operating the store day-to-day — compact, backup, status, scheduling — is covered in docs/guides/operations.md. The conflict workflow is in docs/guides/conflicts.md. To prime an AI assistant on how to use Memento well, see docs/guides/teach-your-assistant.md — or, if your client supports Anthropic skills (Claude Code, Cowork), install the bundled skill for a no-config alternative.

See and curate your store in a browser. npx @psraghuveer/memento dashboard launches a local-first web UI that reads against your MEMENTO_DB: memory counts by kind and scope, audit trail, conflict triage, config inspection. Localhost-only, gated by a per-launch random token in the URL the launcher hands the browser, no telemetry. The dashboard is a sibling package (@psraghuveer/memento-dashboard) shipped under ADR-0018; see docs/guides/dashboard.md for the full walkthrough.

Stuck? Common failure modes (better-sqlite3 build errors, command not found: memento, STORAGE_ERRORs, missing embedder dependency) are covered in docs/guides/troubleshooting.md.

For the contributor workflow (branching, commit conventions, PR checklist) see CONTRIBUTING.md. AI agents working on the codebase must also read AGENTS.md.

Guiding principles

These are the four principles every design decision is judged against. They are documented at length in ARCHITECTURE.md.

1. First principles. Every construct exists because we proved we need it, not because it's how things are usually done.
2. Modular. Any component can be replaced without rewriting the rest.
3. Extensible. New variants don't require breaking changes.
4. Config-driven by the user. Behavior is shaped by configuration, not by code.

What Memento is

• Local-first. Your memory lives in a single SQLite file under your home directory. No outbound network calls by default.
• LLM-agnostic. No model dependencies. No proprietary APIs. Works with whatever LLM your tools use.
• Tool-agnostic. Exposes its full surface over both MCP (for AI agents) and a CLI (for humans and scripts). The two are kept in lockstep by a single command registry.
• Privacy-conscious. A built-in regex-based scrubber strips secrets before they are persisted. Patterns are user-configurable.
• Auditable. Every write produces an event in an append-only log. You can answer "why is this memory here?" and "when did this change?" at any time.
• Versioned. Schema migrations are append-only. Memories are typed, validated at the boundary, and have explicit lifecycles (active, superseded, forgotten, archived).

What Memento is not

• Not a chat history store. It records distilled, structured memory — preferences, facts, episodes, lessons — not raw transcripts.
• Not a knowledge graph or semantic database. Use the right tools for that.
• Not a cloud service. Memory lives on your machine; cloud embedders, sync across machines, and team-shared memory are not part of the product.
• Not a plugin platform. The architecture leaves the door open, but Memento ships with a fixed surface to hold the line on quality.

The full list of out-of-scope and current limitations is in KNOWN_LIMITATIONS.md.

How it fits together

┌─────────────────────────────────────────────────────────┐
│  Clients: Claude Desktop, Claude Code, Cursor, Copilot, │
│           OpenCode, custom agents, …                    │
└──────────────────────┬──────────────────────────────────┘
                       │ MCP (stdio)
┌──────────────────────▼──────────────────────────────────┐
│  memento-server (MCP adapter)                           │
└──────────────────────┬──────────────────────────────────┘
                       │ Command registry
┌──────────────────────▼──────────────────────────────────┐
│  memento-core: services, scope resolver, scrubber,      │
│                conflict detector, decay engine          │
└──────────────────────┬──────────────────────────────────┘
                       │ Repository interfaces
┌──────────────────────▼──────────────────────────────────┐
│  SQLite (better-sqlite3) + FTS5 + optional sqlite-vec   │
└─────────────────────────────────────────────────────────┘

A full architectural walkthrough lives in ARCHITECTURE.md. Each significant decision has an Architecture Decision Record.

For contributors (human or AI)

Contributions are welcome from both human and AI-assisted authors. We treat them with the same standards.

• Read AGENTS.md if you are an AI agent or working with one. It is the canonical instruction set; CLAUDE.md and .github/copilot-instructions.md are thin pointers to it.
• Read CONTRIBUTING.md for development setup, branching, commit conventions, and the PR lifecycle.
• Open a design proposal issue before any non-trivial change.
• Use the PR template. It asks you to justify, not just describe, the change.

We use GitHub Discussions for questions and ideas; the issue tracker is for bugs and accepted work.

License

Apache-2.0. See NOTICE for attribution.

Packages

Memento is a small workspace of focused packages. The architecture is documented in docs/architecture/ and the design decisions in docs/adr/; both are the source of truth for what Memento does and why.

Package	Notes
@psraghuveer/memento-schema	Memory / event / scope / scrubber / conflict / config / result schemas, plus per-ConfigKey value schemas.
@psraghuveer/memento-core	Storage and migrations, memory + event repositories, scope resolver, scrubber, decay engine with compact archival pass, conflict detection + supersession workflow, embedding hook + bulk re-embed driver, EmbeddingProvider interface, FTS + brute-force vector retrieval pipeline + ranker, and the command registry with validating execute path (ADR 0003).
@psraghuveer/memento-server	MCP adapter — buildMementoServer projects the @psraghuveer/memento-core command registry as MCP tools; serveStdio wires it to stdio. Used by memento serve.
@psraghuveer/memento-embedder-local	Local EmbeddingProvider backed by transformers.js + bge-base-en-v1.5. Ships as a regular dependency; lazy single-flight init downloads the model on first use. See ADR 0006.
@psraghuveer/memento (CLI)	The published memento binary (npx @psraghuveer/memento or npm i -g @psraghuveer/memento). Lifecycle commands (init, serve, dashboard, context, doctor, status, ping, backup, export, import, store migrate, completions, explain, uninstall) plus a generic projection of the registry surface (memento <namespace> <verb>). See docs/reference/cli.md.
@psraghuveer/memento-dashboard	Local-first web dashboard. Hono server in-process with the engine + Vite-built React SPA. Launched by memento dashboard; binds 127.0.0.1 only. See ADR-0018 and docs/guides/dashboard.md.
@psraghuveer/memento-landing	Marketing landing page. Static SPA, deployed to GitHub Pages on every push to main that touches packages/landing/**. Mirrors the dashboard's design tokens; light/dark toggle. Private (not published to npm).