Al Buddy Memory

MCP文档知识

提供方 未标注

文档知识 stdio · 本地进程 API Key 社区 / 第三方 Claude DesktopClaudeCursorVS Code
查看接入方式

受治理的、可移植的AI代理记忆:每次召回都会返回谁断言了某个事实、该事实自何时起为真,以及什么取代了它。事实从不被覆盖。本地SQLite,无需API密钥。

一句话选型结论

按资料字段整理

Al Buddy Memory 属于文档知识类 MCP 服务器,stdio · 本地进程,API Key,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类文档知识 传输方式stdio · 本地进程 鉴权API Key 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

文档知识
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

记忆

安装与配置

stdio · 本地进程 API Key
客户端在本机拉起子进程,数据不出本机
npx al-buddy-memory conformance my-export.json # format auto-detected npx al-buddy-memory conformance agent.af --format blocks # block-style agent files npx al-buddy-memory conformance memories.json --format records # flat memory records npx al-buddy-memory conformance --demo # a small governed store, for comparison

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
文档检索问答

在你的文档库里按问题找答案。

知识库读写

把新资料写进知识库,随用随取。

内容整理

把零散资料归纳成结构化笔记。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在文档知识场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Al Buddy Memory当前 未标注 stdio · 本地进程 本地部署 有 未标注
dify 未标注 stdio · 本地进程 本地部署 有 2026-04-11
open-webui 未标注 stdio · 本地进程 本地部署 有 2026-04-11
JeecgBoot 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Cherry Studio 未标注 未标注 未标注 无 2026-05-17
mempalace 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

文档知识
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类文档知识本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

47.0 KB
来自项目仓库与上游目录的原文,未做删改

al-buddy-memory

> Al Buddy — that's Al, a name, said like "pal". Not A.I.

A memory that's yours.

Portable, governed, model-agnostic memory for AI agents.

A fact is invalidated, never overwritten; on a governed handle, erasure runs through policy and is audited. Raw text is the source of truth and cannot be edited. Embeddings are a disposable, model-tagged cache. Every fact and every link exports to one documented format. The memory outlives whatever model, runtime or company produced it.


Why this exists

Every agent-memory product on the market answers one question well: what does the agent recall? None of them answers the four questions that decide whether you can trust and keep that memory:

Question This library Letta Mem0 Zep
Where did this fact come from, and who asserted it? Provenance on every node and edge (UserInput / AIInferred / GuardianAdded / SystemGenerated) Memory-file git history Metadata field Graph episodes
When was it true, and what replaced it? Two queryable axes: validAt answers what was true at Y; getNodeAsOf / snapshotAsOf answer what the store believed at X from full before/after versions. They combine in one call (snapshotAsOf(X, { validAt: Y })), a read the history cannot vouch for is marked, and erasure removes the history too Git history of files, not a fact model Change history per memory (history(): old value, new value, event, timestamps) — transaction history, not valid time Temporal graph (its real strength): Graphiti edges carry valid_at / invalid_at alongside created_at / expired_at
Can I take it with me, losslessly, to another runtime? One versioned JSON export with a published schema and conformance tests .af (agent state, framework-shaped, archival memory not yet included) Cloud export Cloud-only since 2025
Does it run with no vendor, no key, no server? SQLite on disk, on-device embeddings Self-host possible; cloud is the product Self-host possible (Apache-2.0, local vector stores); needs an LLM for extraction; cloud is the product Zep is cloud; Graphiti self-hosts (graph DB + LLM key required)

Sources for the cells above, each checked against the project's own code or announcement on 2026-09-18: Mem0's per-memory history is a SQLite table with old_memory, new_memory, event, created_at, updated_at (mem0/memory/storage.py); Mem0 is Apache-2.0 and runs against local vector stores including Qdrant, Chroma, pgvector and FAISS (vector-store docs), with an LLM called to extract facts on the default add() path. Zep stopped maintaining Community Edition on 2025-04-02, in its own words: "we've decided to stop maintaining and releasing Zep Community Edition." Graphiti, the engine under Zep, is Apache-2.0 and self-hosts, and its stated requirements are a graph database (Neo4j, FalkorDB, Amazon Neptune, or the deprecated Kuzu) plus an LLM key — it "defaults to OpenAI for LLM inference and embedding."

The three local, keyless ones people will name, read against their own code on 2026-09-21. They answer the fourth question the way this library does — your machine, your files, no account — and they are the honest comparison, not the cloud products.

  • basic-memory (AGPL-3.0; Markdown notes on disk are the truth, SQLite is a rebuildable index). It has valid time, and that is worth saying plainly: an observation can carry @effective2026-06-10,2026-07-27) in the note itself, parsed into a time index ([models/knowledge.py) and rebuilt from the file, so the file stays the source of truth. What it does not carry on a local install is who asserted a fact: created_by / last_updated_by exist and hold a cloud user id, null for local and CLI use. Portability is the strongest kind and the least specified: the notes are the format, so nothing is trapped, and there is no versioned schema to import them into something else. Capture and full-text search need no key; semantic search is opt-in and does.
  • The MCP memory server (the reference implementation most agents meet first; one JSONL file). Entities, relations and observations, and nothing else: no field for who said it, no timestamps at all, and deleteObservations filters the old value out of the array, so what was true before is gone rather than closed. The file is its own export. Nothing calls a model; nothing leaves the machine.
  • Memori (Apache-2.0; your own SQL database — SQLite, Postgres, MySQL, Oracle). A fact in memori_entity_fact has content, an embedding, a count and a last-seen date; who asserted it is only recoverable by walking the foreign keys back to a conversation message, not a property of the fact, and there is no valid time — date_updated replaces. "Your data stays in your database" is the portability story, with no interchange format published. It is local in the sense that matters for your data, but capture is not keyless: extraction and embeddings call an LLM, and the default SDK path expects a Memori account as well.

Also worth naming: OpenMemory MCP (Mem0, launched May 2025) shipped the same distribution idea — one local memory store shared across MCP clients — and Mem0 archived it; its README now opens "This project has been archived." Its schema is the contrast this table is about: models.py gives a memory content, created_at, updated_at, archived_at, deleted_at and a state, with no field for who asserted the fact and no valid time, and content is rewritten in place on update. It does keep a state-transition history and an access log, and it does have a ZIP export — so it is not the absence of portability that separates the two, it is provenance, valid time and an immutable raw.

Recall benchmarks (LOCOMO, LongMemEval, DMR) measure what an agent remembers. None of them scores a memory system on provenance, invalidation or portability. This library is built for that axis, and the conformance scorer below is one attempt at measuring it. The table is our reading of each project's own code and public docs, dated above; if we have a cell wrong, a PR with a link fixes it.

We run LongMemEval anyway, so a recall number people recognise sits beside the conformance score rather than in place of it, along with a small benchmark of our own for the part recall benchmarks skip: when a fact changes, does recall return the value that is true now? See Benchmarks.

Start here

An empty memory gives an assistant nothing to stand on. docs/STARTER.md seeds
yours in ten minutes: pin who the person is and how they want to be treated (including "never a
yes-person"), choose the rules the store enforces, and let it derive the rest nightly.

Upgrading from an earlier version: CHANGELOG.md marks anything that changes what
an existing caller gets back. 0.4.0 has breaking changes (immutable content, governed erasure, a new
listNodes on the store interface, the MCP exports moved to al-buddy-memory/mcp), so read that
entry before you upgrade.

What is in the box

  • MemoryStore: a storage-agnostic interface; SqliteMemoryStore and InMemoryStore ship, with a conformance suite any backend can run against itself.
  • ProjectMemory: one brain scoped by project or person, each in its own SQLite file.
  • HybridRetriever: lexical + semantic recall with decay-aware confidence; embeddings on-device via transformers.js (no API key). Recall can be scoped (memory type, tags, minimum confidence, privacy and retention tiers), and the scope applies to the keyword and the vector side alike. Two opt-in aids for questions whose answer is spread across conversations, both computed at read time and never stored: a reranker (LocalReranker, an on-device cross-encoder) that rereads the question with each candidate and reorders them, and expand, which reads a question's time and counting cues (analyzeQuery: "in April", "the past two weeks", "how many", "A and B") and recalls for each.
  • exportPortable / importPortable: the lossless interchange format, versioned, with a JSON Schema.
  • PinnedBlocks: a size-capped tier of facts that belong in every prompt, editable by the agent itself, on top of the governed store.
  • consolidate: a sleep-time pass that reads recent raw memory and writes new derived facts with provenance edges back to their sources; the raw is never rewritten and nothing is summarised away.
  • verifyDerived: every conclusion stores the exact words it rests on (evidence), checked when it is written; this re-checks them any time, and retracts, never deletes, one whose evidence no longer holds.
  • Mental models: standing questions with answers kept current in the background, so reading one costs no model call (defineMentalModel, refreshMentalModels, getMentalModel). Every answer quotes the facts it rests on, keeps its history ("what did we think in June"), and reads as stale the moment one of those facts stops being true or is erased.
  • Current state: "where does X stand now?" held as one live memory per subject (recordState, currentStates, statesMentionedIn). A newer state closes the one it replaces and keeps it as history; a state that arrives late never overturns a newer one. Recall can also weigh recency (freshness), so the newest of several matching notes comes first.
  • explainFact: why a fact is believed, in one call — provenance and origin, validity and what replaced it, a conclusion's evidence with each quote checked, and its history. Through a governed handle a source the reader may not see is named as withheld, never shown.
  • Conclusions go with their facts: a fact that stops being true retracts what was concluded from it (kept, marked); a fact that is erased takes everything built from it (SPEC §8a).
  • listConsolidations / undoConsolidation: review what each pass concluded, with the evidence for every fact, and take back one pass's conclusions. Undo retracts (validTo) and records who withdrew each fact and why; it never deletes, so the history still shows what was believed, when it was withdrawn, and the reason.
  • buildSourceProvenance / readSourceProvenance, renderMemoryBlock, exportMemoryMarkdown, decay helpers.
  • Integrations: al-buddy-memory/ai-sdk (Vercel AI SDK tools + middleware), al-buddy-memory/langchain (a LangGraph long-term memory store + LangChain tools), al-buddy-memory/mastra (an input processor + tools). The frameworks are optional peer dependencies; every write is governed and records which agent made it. Guides in docs/integrations.

Node ≥ 20. One runtime dependency (better-sqlite3, with prebuilt binaries for Node 22, 24, 25
and 26 on macOS, Linux and Windows; on Node 20 it compiles from source, which needs Python and a
C++ toolchain). Postgres (pg), the MCP SDK and the on-device model (transformers.js) are optional:
they load only if you use them, and npm install --omit=optional leaves them out.

Prior art: the Letta project published the idea of a pinned memory tier and a background pass over memory (memory blocks; sleep-time agents). What is different here: every derived fact must cite the raw it rests on or it is refused, the raw is never rewritten, and a whole pass can be reviewed and undone, with the undo and its reason kept on record.```ts
import { SqliteMemoryStore, ProjectMemory, PinnedBlocks, exportPortable } from "al-buddy-memory";

const store = new SqliteMemoryStore("./brain.db");
await store.addNode({ provenance: "UserInput", memoryType: "Lesson", content: { text: "Chris prefers decisions over options." }, / …governance fields… / });
const pins = new PinnedBlocks(store);
await pins.pin({ text: "Never present options without a recommendation.", label: "rule" });
const snapshot = await exportPortable(/ … /); // → docs/portable-format.schema.json


Full contract: docs/SPEC.md. Design record: docs/DECISION-2026-07-07.md.

---

## Python, and other languages

The MCP server and the portable format are the language-neutral surface: a Python agent can
use the governance server today, and any language can read the export (it is plain JSON with
a schema). A native Python package is planned; open an
issue if you need it sooner and say what you would use first.

## License

Apache-2.0. See LICENSE.

## Governance is enforced, not implied

The vocabulary — Public / Private / Sensitive / Sealed, retention tiers, provenance on
every fact and relation — ships with the store. `govern()` is what enforces it: policies
in front of every write, update, read and export, and an append-only audit trail of who
read what and why.```ts
import { SqliteMemoryStore, govern, personalDefaults, storeAudit } from "al-buddy-memory";

const inner = new SqliteMemoryStore("brain.db");
const store = govern(inner, {
  policies: [personalDefaults({ owner: "chris" })],
  context: () => ({ actor: currentActor() }),
  // The trail goes in the database, hash-chained, in the same transaction as
  // the fact it describes. `new ChainedAudit("audit.jsonl")` puts it in a file
  // instead — for a store that is not SQLite, or when you want it outside the
  // file it describes. See docs/GOVERNANCE.md for what each one proves.
  audit: storeAudit(inner),
});

To make sure nothing is ever erased by accident, add memoryLock() to the policies: while it
is there, erasure is refused for everyone, the owner included, until you take it out (or flip
the switch it reads). Invalidating a fact still works; that is not erasure. The raw store and
the database file are outside any policy, so keep backups.

And to make a deletion something you can take back, pass recentlyDeleted: { days: 14 } to
govern(): a delete then moves the fact out of recall for 14 days, restoreDeleted brings it
back, and purgeDeleted erases it for good once the days are up (asking the policies again, so
the lock still wins). Nothing runs on a timer, and until it is purged the fact is still in
exports and backups.

Check the trail with al-buddy-memory verify-audit brain.db. It names the first event that
was edited, removed, inserted or reordered. What it establishes, and the two things it does
not, are written out in docs/GOVERNANCE.md —
short version: the chain is tamper-evident; a tail cut off a log file is invisible to it,
a tail cut off the table is caught as long as nobody resets the table's own counter, and
only a head you anchor somewhere else catches a rewrite or a restored backup.

Three policies ship to copy: personal defaults (secrets auto-classified Sensitive; Sensitive
facts never reach, leave with, or get erased by anyone but the owner in person; only the owner
changes a fact), guardian mode (only a guardian may write or
change a guardian's fact), enterprise audit (low-confidence inferences hidden from
non-reviewers; exports gated to exporters). A policy is a plain object with five
optional hooks; see docs/GOVERNANCE.md.

Without any policy the store still guarantees: Sealed facts never surface in a search unless
asked for by classification; provenance, nodeId, encryptionKeyRef, raw content and the
anchor trail are immutable after write, through every path including import; every instant is
stored in one canonical UTC spelling. Two things it does not do, said plainly: provenance is what
the writer asserts (immutable once written, not verified — bind actors to provenance in a policy);
and encryptionKeyRef names a key you manage, it does not encrypt the file.

The governed handle is the boundary. govern(store, …) puts policies in front of every
operation that can change a fact or reveal one — including erasure, which is refused unless a
policy explicitly allows it. Whoever holds the inner store is not governed by anything, so hand
out the governed one.

The rules an assistant on this memory is held to are published in docs/policies:
ethical behaviour, user sovereignty and privacy, lifecycle and guardians, data stewardship — and
an honest ledger of what the code enforces, what a prompt carries, and
what is still a person's decision. They change in the open.

Enterprise

The same store for an organisation: a shared database, rules about who sees what, encryption
the operator controls, and erasure on request. SQLite stays the default, and nothing here changes
a local setup.

  • Postgres. PostgresMemoryStore (pgvector 0.8 or newer) sits behind the same
    MemoryStore interface and passes the same conformance suite. Every read and write is confined
    to one tenant key, and the audit chain is kept per tenant in the same transaction as each
    governed write; verify-audit --postgres --tenant checks it. A write reads and writes
    only the rows it acts on, so its cost does not grow with the tenant: measured flat from 1,000
    to 100,000 facts (about 1–3 ms a write, 3–6 ms governed and audited, in-process PGlite).
    docs/POSTGRES.md
  • Boundaries. A policy can declare who sees what as data: readBoundary, fact labels
    against the asking actor's attributes, with equality, membership, AND and OR. SQLite and
    Postgres compile it into their own WHERE, before ranking and before any limit, so facts
    outside it never take a place in a page. It fails closed, and beforeRead still has the final
    word. docs/policies/boundaries.md
  • Sign-in. The HTTP server can accept OIDC/JWT bearer tokens from your own identity provider
    (Okta, Microsoft Entra, Google Workspace, any OIDC issuer) instead of the owner's passphrase.
    Signature (the issuer's JWKS), issuer, audience and expiry are checked with jose; configured
    claims become the actor attributes boundaries read, and one claim can name the tenant. Any
    failed check is a 401. docs/SIGN-IN.md
  • Encryption at rest is not something this library does. On Postgres it belongs to the
    database: storage encryption with KMS-managed keys, encrypted backups, TLS. Locally the SQLite
    file is plaintext, owner-only (0600 in a 0700 directory), so use full-disk encryption
    (FileVault, BitLocker, LUKS). For file-level encryption, a SQLCipher build of SQLite is the
    route, but it is not built or tested here. encryptionKeyRef names a key you manage; it
    encrypts nothing.
  • Erasure. eraseWhere({ label: "subject", equals: "person-42" }) erases every fact
    carrying that label that the actor can see, along with what was concluded from them. Each
    fact goes through the erase policies, so a memory lock still refuses and Recently deleted
    still holds. The call returns a receipt: selector, actor and time; counts erased, refused
    (with reasons) and held; ids hashed. Its digest is chained into the audit trail, so
    verify-audit memory.db --receipt receipt.json checks it. Backups and exports made before
    the erasure are outside it
    , and the receipt says so. It behaves the same on SQLite and
    Postgres. docs/ERASURE.md

Enterprise edition

The core stays free and Apache-2.0, including everything above. A commercial enterprise
edition adds:

  • multi-process safety for serverless deployments
  • data-API query executors
  • database row-level security
  • an enterprise readiness suite

The seams these plug into are public, and so is read audit: PostgresMemoryStore with
accessAudit: { sink, reads: true } hears every read and write of a tenant, inside the call's own
transaction. docs/EXTENSION-POINTS.md

To ask about it, contact the repository owner, @flytomoon.

Limits, measured

One SQLite file, one process, one writer. Measured on an M1 Pro laptop with 100,000
facts (bench/bench.mjs, better-sqlite3, WAL):

Operation (100,000 facts) Measured
Insert, one fact per call 5,400–5,900 facts/s (17–18 s for all 100k)
Keyword recall, top 10 (FTS5 + decay re-rank) 30–50 ms median, ~150 ms worst of five terms; first query after open ~320–380 ms (cold cache)
Keyword recall through a governed handle, top 10 ~75 ms for a word in 10% of facts, ~135 ms for two such words, ~850 ms for a word in every fact — see below
Recall by filters only, top 10 0.5–1 ms
Get by id 0.1 ms
Invalidate a fact 0.5 ms
Reconstruct snapshotAsOf 2.19 s with 100,001 versions
File size 69 MB for the 100,000 facts; each recorded change adds ~738 bytes (140 MB after one update to every fact)
Audit event into audit_events, in the fact's own transaction +0.04 ms per governed write, +0.5 ms per governed read (a read is audited too, so it takes the write lock briefly)
Checking the chain — verify-audit linear, ~3 µs/event: 83 ms at 20,000 events, 325 ms at 100,000, 1.5 s at 500,000. Each process pays it once, before its first governed write and outside the write transaction, so it delays that process and blocks no other. Constant memory (the walk streams)
How fast the trail grows one event per governed write, one or two per governed read — a remember is +2, a recall +1. Nothing prunes it. At 500,000 events the trail is ~128 MB, which can exceed the facts it describes; if you drive a store that hard, keep an eye on it

Ranges are three runs of the same script on 0.4.0. Paging is exact: a page of ten is the
first ten of the full ordered read. When facts have genuinely decayed, the store may have to
read past its 200-row candidate pool to keep that promise — the worst case is a full read of
the matching facts (~300 ms at 100k), and it only happens when a decayed fact and a fresher one
would otherwise trade places.

The transaction-time measurement is one run on the same M1 Pro: 100,000 facts,
one recorded reinforcement per fact, and one earlier invalidation. Reconstructing all
100,000 facts from 100,001 versions took 2.19 s. It is an in-memory linear reconstruction,
not an indexed point lookup.

A governed keyword search is slower on purpose. It reads every match, keeps the ones the
actor may see, and ranks them with word rarity counted over those visible matches alone: the
store's BM25 counts rarity across all facts, hidden ones included, so it would let a hidden
fact reorder visible results. At a personal memory's size (a few thousand facts) the speed
difference does not show, and a test holds its quality: twelve facts asked for in plain
questions ("what is the wifi login") among two hundred distractors all land on the first page.

What that means: a personal assistant or a single-tenant service will not notice the
store. Hosted deployments can use PostgresMemoryStore with explicit tenant keys;
SQLite remains the default. Node/TypeScript only for now; the optional on-device
embedder is a 25 MB model download.

The semantic path costs more

Everything above is the keyword path. Recall with an embedder wired goes through a
brute-force linear scan: every stored vector is read, decoded and scored against the
query. Measured the same way (bench/bench-vectors.mjs, 384-dimension float32 vectors,
the width and number type of the default on-device model), on the same laptop, since
0.8.1 stores vectors as float32 bytes (the 0.8.0 JSON-text figures in brackets):

With an embedder wired 20,000 facts 100,000 facts
File size (facts + vectors) 55 MB (172 MB) 277 MB (864 MB)
Per vector, on disk 1,536 bytes (~8,000) 1,536 bytes (~8,000)
Semantic recall, top 10 — first of a session 488 ms (765 ms) 1,619 ms (3,200 ms)
Semantic recall, top 10 — thereafter 22 ms median (36 ms) 113 ms median (187 ms)

gaugeStore measures any store file this way and checkBudgets says which numbers are over
budget.

The history of this section is worth keeping: on 2026-09-19 it measured the JSON cost,
named float32 storage as the fix, and filed it here as a weak spot. It was built six days
later, when a question about backups surfaced it. A measurement with no budget is a fact
nobody owns; that is why the gauge exists.

Where the time goes, 0.8.0 → 0.8.1. On 2026-09-19, one cold call at 100,000 facts
spent 978–1,182 ms reading the vector table and 1,418–1,744 ms in JSON.parse, against
85–127 ms for the cosine scan itself: reading and parsing 8 KB text rows was 95% of the
cost, and the scan everyone suspects was 4%. Storing float32 bytes shrank the read about
5× and removed the parse; what remains of the 1.6-second first call is reading 154 MB and
turning it into JavaScript arrays. Two consequences:

  • sqlite-vec is still not the next move at this size; the scan is not the cost.
  • The vector cache is disposable and model-tagged. Vectors live in their own table
    keyed by (nodeId, model); deleting them loses nothing but time, and a vector from a
    different model is skipped rather than compared. Upgrading the embedder is a re-index,
    never a migration.

The scan is still linear in the number of facts, and a session's first call pays for the
whole vector table; later calls reuse a 60-second in-process cache.

Backups, restores and synced folders

A SQLite database in WAL mode is three files — brain.db, brain.db-wal, brain.db-shm —
and two ordinary habits will quietly lose a person's memory:

  • Restoring a backup: stop the server first, then delete brain.db-wal and
    brain.db-shm before you copy the backup into place. A -wal left beside a restored
    file is replayed over it on the next open, so the restore appears to succeed, reports no
    error, and leaves you with the data you were trying to replace. Verified, 2026-09-19.
  • Which backup command: sqlite3 brain.db ".backup out.db" and
    VACUUM INTO 'out.db' are the safe ones — both take a consistent snapshot of a live
    database, verified while another process was writing. sqlite3 .dump works too, but it
    does not carry user_version; before 0.4.2 a restored dump could not be opened at all
    (duplicate column name: valid_from), and now it migrates cleanly. Never back up by
    cp-ing a live database: a copy taken mid-write can be unreadable, and a readable one
    can still fail PRAGMA integrity_check.
  • Synced folders: never put the database in iCloud, Dropbox, OneDrive or Google Drive.
    WAL mode assumes one machine coordinating its own locks; a sync client copying
    the three files independently, or two machines writing through one folder, corrupts the
    file rather than conflicting visibly. Back the folder up by all means — copy it out on a
    schedule, or use .backup/VACUUM INTO — but do not let a sync client own the live file.

The conformance score

Try it: albuddy.com — paste any memory export, nothing leaves your browser.

Recall benchmarks are saturated. Nobody scores whether a memory system can say who
asserted a fact, since when, whether it is still true, and whether the fact
survives leaving the vendor. This does, on any export you paste in:sh npx al-buddy-memory conformance my-export.json # format auto-detected npx al-buddy-memory conformance agent.af --format blocks # block-style agent files npx al-buddy-memory conformance memories.json --format records # flat memory records npx al-buddy-memory conformance --demo # a small governed store, for comparison

Seven dimensions, each 0–100% with the reason spelled out; a dimension the sample cannot
prove (no retired facts present, say) is reported as unproven and left out of the total
instead of counted as a failure. The reference score:

Export Provenance Since when Retire without erasing Confidence Relations Portability Grade
al-buddy-memory (demo store) 100% 100% 100% 100% 100% 100% A

Score your own export the same way: --format blocks for block-style agent files, --format records for flat memory records, or paste it into the demo at albuddy.com.

Where the numbers come from, said plainly, because this is a scorer we also score
ourselves with. Five of the seven — provenance, since when, retire without erasing,
confidence, relations — are counted off the records in the file you paste; change the
sample and they move. Two are not. Whether a system keeps a retired fact, whether its
schema is published, and whether it itemises facts are properties of the system, which
no single export can prove, so the adapter author declares them in
src/conformance/adapters.ts and they show up verbatim in the report's reason line. The
one part that is executed rather than asserted is the round-trip: for our own format the
scorer imports your artifact into a fresh store, exports it again and compares — on your
file, and it says lossy if that fails.

The rulebook, including which dimension is which and what the score does not measure
(recall quality, truth, latency), is docs/SCORING.md. The adapters are
written against export shapes, not vendors. If a system starts recording provenance, its
score goes up — that is the point. Add an adapter for your shape and open a PR; if you
think we declared a trait wrongly for yours, that is a one-line PR too.

Benchmarks

The conformance score measures what recall benchmarks leave out; it does not replace them. Two
harnesses in bench/ put numbers beside it, each with its result file, commit and
settings in bench/results/:

  • LongMemEval, the public recall benchmark: 500 questions over
    chat histories of about 50 sessions each. Every question gets a fresh store holding its history,
    one memory per message through the public API, nothing extracted or summarised; recall chooses
    what the reader sees. The reader and judge prompts, the yes/no rule and the retrieval metrics are
    the official ones, held to the official code by tests. The reader and judge are Claude, run
    through the Claude Code CLI on a subscription, so a run spends no metered API money — and the
    judge is therefore not the official gpt-4o, which is why every result ships its answers in the
    official format for anyone to re-judge. node bench/longmemeval/run.mjs --limit 50 is a smoke run.

…(正文过长,页面只展示前面部分,完整内容见仓库)

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Al Buddy Memory 怎么安装?

在客户端按下面的安装命令接入:npx al-buddy-memory conformance my-export.json # format auto-detected npx al-buddy-memory conformance agent.af --format blocks # block-style agent files npx al-buddy-memory conformance memories.json --format records # flat memory records npx al-buddy-memory conformance --demo # a small governed store, for comparison。装完在客户端配置里引用同一个包或端点。

Al Buddy Memory 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Al Buddy Memory 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Al Buddy Memory 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

Al Buddy Memory 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Gemini CLI、Codex;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Al Buddy Memory 能提供哪些能力?

资料显示能力标签包括 记忆。具体工具清单以官方文档为准。

Al Buddy Memory 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

Al Buddy Memory 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。