Save something worth remembering across sessions.

Store durable facts, decisions, preferences, and project context — not transient chatter. The text is embedded locally so it can be found later by meaning, not just exact words.

Find memories by meaning.

Semantic search over everything stored, so "what database did we pick?" finds a memory that says "we went with SQLite". Results are ranked by similarity, highest first.

To page through more matches, keep the same query and advance offset by limit — ranking is stable, so pages don't overlap or skip. An offset past the last match returns no results.

Re-read a specific memory by id, or the most recent memories.

Use this when you already know which memory you want (from a previous store_memory or search_memory call), or to catch up on what was recorded most recently. To find memories by meaning, use search_memory instead.

Enumerate memories with tag filtering, ordering, and pagination.

Use this to browse stored memories without requiring a search query — to audit memories, paginate through tag categories, or view memories in chronological or reverse-chronological order.

Filtering and ordering only — no embedding model or scoring is used.

Correct an existing memory in place.

Use this when a stored memory is wrong — a misremembered decision, a misspelled name, a fact that has since changed. It edits the original record rather than adding a related one, and re-embeds the text so search finds the correction. Only the fields you pass are changed.

Permanently delete one memory by id.

Use this when a stored memory is wrong beyond correction, sensitive, or simply no longer wanted — prune it so stale facts stop outranking current ones. To fix a memory instead of deleting it, use update_memory. The delete is hard: the row is gone, not hidden.

Permanently delete memories by tag and/or age.

Use this to prune stale facts en masse — drop every memory tagged "scratch", or everything older than 90 days. At least one filter is required; an unfiltered call is rejected so the store can't be wiped by accident. Deletion is hard: matching rows are gone, not hidden.

Report where memories are stored, how many there are, and which model is used.