open-memex 0.8.0-alpha.3 → 0.8.0

package/AGENTS.md

@@ -144,8 +144,9 @@ Every write path (tool, keyword hook, CLI `add`) must:
 
 Capture-time aliases (D61): `memory_add`/`supersede` may carry up to 4
 `aliases` (alternate phrasings) into frontmatter; they index in their own FTS
-column. Only when `cfg.captureAliases` is on (init asks once, default on) —
-when off, passed aliases are dropped. Always pass them through
+column. Always on since 2026-10-07 (Stone: init no longer asks) —
+`cfg.captureAliases` still gates them for backward compatibility with
+installs that set it manually, but new installs never see the question. Always pass them through
 `normalizeAliases`; the keyword-capture path (no agent in the loop) never
 invents aliases. Checkpoint-proposal guidance (propose, never auto-draft) is
 copy, not mechanism: keep the rubric wording in sync across the skill, the

package/CHANGELOG.md

@@ -9,7 +9,9 @@ the `@alpha` tag are development snapshots and are not listed individually.
 
 ## [Unreleased]
 
-- User-defined alias vocabulary as query-time expansion (D81): any memory type may now carry `alias:` (nickname, e.g. 香蕉计划) and `target:` (referent, e.g. 支付系统重构项目) frontmatter — an alias memory defines vocabulary once per scope. At query time, query terms hit the alias registry (exact match, one cheap SELECT per search) and the query is rewritten with the other side of the relation — bidirectional, depth < 3, cycle-safe — then re-run as round 2/3. Rounds merge by normalized-max (`mergeRounds` in `src/retrieve/alias-memory.ts`): each round's BM25 scores are divided by that round's best, so an alias-side champion competes evenly with a literal-side champion; the merged pool is re-ranked and cut to [1.5K, 2K], never back to K. No reindex when an alias changes. Creation: `memory_add` alias/target params, CLI `add --alias/--target`, or frontmatter edit (v1: user-explicit only). Fixture grows to 54 memories / 44 queries (3 bidirectional alias queries): recall@1 0.750, recall@5 **0.977**, MRR 0.857. Also rewords the init `captureAliases` prompt — it was never the synonym switch (D80's expansion always applies).
+## [0.8.0] - 2026-10-07
+
+- User-defined alias vocabulary as query-time expansion (D81): any memory type may now carry `alias:` (nickname, e.g. 香蕉计划) and `target:` (referent, e.g. 支付系统重构项目) frontmatter — an alias memory defines vocabulary once per scope. At query time, query terms hit the alias registry (exact match, one cheap SELECT per search) and the query is rewritten with the other side of the relation — bidirectional, depth < 3, cycle-safe — then re-run as round 2/3. Rounds merge by normalized-max (`mergeRounds` in `src/retrieve/alias-memory.ts`): each round's BM25 scores are divided by that round's best, so an alias-side champion competes evenly with a literal-side champion; the merged pool is re-ranked and cut to [1.5K, 2K], never back to K. No reindex when an alias changes. Creation: `memory_add` alias/target params, CLI `add --alias/--target`, or frontmatter edit (v1: user-explicit only). Fixture grows to 54 memories / 44 queries (3 bidirectional alias queries): recall@1 0.750, recall@5 **0.977**, MRR 0.857. Also removes the init `captureAliases` and keyword-capture questions — both are now always on (Stone 2026-10-07).
 
 - Index-time synonym/translation expansion (D80, supersedes D79): the curated map (`src/retrieve/synonyms.ts` — EN dev-domain groups, ZH groups and EN↔ZH translation pairs in one bidirectional list) is now applied at sync/index time — `writeRow` expands each memory's keywords (`expansionVariantsForDoc()`, capped at 32) into the indexed `aliases` column, so any related word matches in a plain round-1 query. The query-time second-chance round is removed (`search()` is a single FTS round; `SearchStats.secondRound` gone); `expandQueryWithSynonyms` stays as a bench-only export. Fixture (51 memories / 41 queries): recall@1 0.732 → 0.756, recall@5 0.854 → **0.976**, MRR 0.791 → **0.859** — all 5 EN↔ZH vocabulary misses rescued at rank 1–3. Map updates need a reindex to backfill.
 

package/README.md

@@ -406,8 +406,8 @@ Three ways memories get in:
 **Aliases.** Each saved memory can carry up to 4 alternate phrasings
 (synonyms, another language's equivalent) that are indexed with it, so a
 question worded differently still finds the memory — "vacation days" finds the
-holiday policy. `init` asks once whether to enable this (default on); turn it
-off any time with `open-memex config set captureAliases false`.
+holiday policy. Always on — the agent may attach up to 4 per memory, and you
+can pass your own via `open-memex add --aliases`.
 
 Three ways to add them: `open-memex add "text" --aliases "phrase one; phrase
 two"` (semicolon-separated, up to 4); ask the agent ("remember: 小宝贝 is my

package/README.zh-CN.md

@@ -263,7 +263,7 @@ open-memex uninstall --yes
 - **检查点提议**：一个任务收尾时，助手会提议 1–3 条从这轮工作里提炼的候选记忆——决定及其理由、约定、踩过的坑、走过又放弃的路——只有你点头的那几条才存。不会有任何东西在你不知情时被写下来。
 - **CLI**：`open-memex add "…"`，可选 `--scope` / `--tag` / `--type` / `--aliases`。
 
-**别名。** 每条记忆可以带最多 4 个换一种说法（同义词、另一种语言的对应词），和记忆一起进索引，这样问法不同也能找到——比如搜 "vacation days" 能找到假期政策那条。`init` 时会问一次是否开启（默认开）；随时可用 `open-memex config set captureAliases false` 关掉。
+**别名。** 每条记忆可以带最多 4 个换一种说法（同义词、另一种语言的对应词），和记忆一起进索引，这样问法不同也能找到——比如搜 "vacation days" 能找到假期政策那条。永远开启：agent 每条记忆最多可附 4 个，你也可以用 `open-memex add --aliases` 自己加。
 
 三种加法：`open-memex add "正文" --aliases "说法一; 说法二"`（分号分隔，最多 4 个）；直接跟 agent 说（"记住：小宝贝是我的 AI agent，别名加上小沐"）；或直接改那条记忆的 `aliases:` frontmatter——Markdown 是事实来源，sync 会吃进去。
 

package/dist/.build-stamp

@@ -1 +1 @@
-115d72be5408b8ae31133dbb253693d370cc97b4c4a46ba0ea9522170367f794
+55d6d5c601b1769ad9c4813aebefcb25ee3b29cab0c6c30f8450d9388fe83a6a

package/dist/cli.js

@@ -116,8 +116,7 @@ Flags:
   --aliases  alternate phrasings of this fact (up to 4), indexed with the
              memory so differently-worded searches still match; separate
              with ; (commas also accepted — use ; when an alias itself
-             contains one). Stored only when capture aliases are enabled
-             (init default)
+             contains one). Always on.
   --alias --target  D81: define user vocabulary once — e.g. --alias 香蕉计划
              --target 支付系统重构项目. Later queries mentioning either side
              trigger a second search round on the other side (both

package/dist/init.js

@@ -811,19 +811,17 @@ export async function initProject(opts) {
         // Install-time settings (D19). Non-default answers persist to the JSONC
         // config file; `open-memex config set` changes them later.
         const patch = {};
-        const keywordCaptureEnabled = await askBool("Auto-capture keywords like remember… / note that… into memory?", DEFAULT_CONFIG.keywordCaptureEnabled);
-        if (keywordCaptureEnabled !== DEFAULT_CONFIG.keywordCaptureEnabled)
-            patch.keywordCaptureEnabled = keywordCaptureEnabled;
+        // Keyword auto-capture is always on (Stone 2026-10-07): no init
+        // question — there is no reason to turn it off. The
+        // `keywordCaptureEnabled` config key is still honored if set manually.
         const injectOnFirstTurn = await askBool("Inject relevant memories when a session starts?", DEFAULT_CONFIG.injectOnFirstTurn);
         if (injectOnFirstTurn !== DEFAULT_CONFIG.injectOnFirstTurn)
             patch.injectOnFirstTurn = injectOnFirstTurn;
-        // D61: capture-time aliases — the agent may attach its own alternate
-        // phrasings to each memory so differently-worded questions still find it.
-        // Distinct from D80's automatic index-time synonym expansion, which
-        // applies regardless of this setting.
-        const captureAliases = await askBool("Let the agent attach its own alternate phrasings (aliases) to memories? (The built-in synonym map applies regardless.)", DEFAULT_CONFIG.captureAliases);
-        if (captureAliases !== DEFAULT_CONFIG.captureAliases)
-            patch.captureAliases = captureAliases;
+        // D61 capture-time aliases are always on (Stone 2026-10-07): the agent
+        // may always attach its own alternate phrasings — no init question.
+        // (Distinct from D80's automatic index-time synonym expansion, which
+        // also always applies.) The `captureAliases` config key is still
+        // honored if someone sets it manually; init just never asks anymore.
         if (Object.keys(patch).length > 0) {
             const file = saveConfig(patch);
             console.log(`  + settings saved to ${file} (change later with \`open-memex config set <key> <value>\`)`);

package/dist/tools/ops.js

@@ -58,7 +58,7 @@ export const scopeArg = z
 export const aliasesArg = z
     .array(z.string())
     .optional()
-    .describe("Optional: alternate phrasings of this fact — synonyms, another way a question might be worded, equivalents in the user's other language (e.g. 节假日 for 'public holidays'). They are indexed with the memory so differently-worded questions still match. Only used when the install has capture aliases enabled (init default). Send at most 4; extras and blanks are dropped silently, never an error.");
+    .describe("Optional: alternate phrasings of this fact — synonyms, another way a question might be worded, equivalents in the user's other language (e.g. 节假日 for 'public holidays'). They are indexed with the memory so differently-worded questions still match. Always on. Send at most 4; extras and blanks are dropped silently, never an error.");
 export const memoryAddArgs = {
     content: z.string().min(1).describe("The fact to remember. One idea per memory."),
     type: z
@@ -242,8 +242,8 @@ export async function addMemory(getScope, cfg, args) {
     const fm = buildFrontmatter(s, {
         type: args.type ?? "fact",
         tags: args.tags ?? [],
-        // D61: aliases are stored only when the install enables them (init
-        // asks once, default on); normalize caps at 4 and drops junk silently.
+        // D61: aliases are always stored (Stone 2026-10-07: init no longer asks;
+        // default on). Normalize caps at 4 and drops junk silently.
         // Aliases pass through the same redaction as content (write-path
         // invariant) — an alias carrying a token gets masked, not stored raw.
         aliases: cfg.captureAliases

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "open-memex",
-  "version": "0.8.0-alpha.3",
+  "version": "0.8.0",
   "mcpName": "io.github.stoneskin/open-memex",
   "description": "Local-first memory layer and protocol for AI coding agents. Markdown source of truth, SQLite FTS5 index, zero cloud.",
   "keywords": [

package/server.json

@@ -3,7 +3,7 @@
   "name": "io.github.stoneskin/open-memex",
   "title": "open-memex",
   "description": "Local-first memory for AI coding agents — Markdown + SQLite FTS5, shared across editors via MCP.",
-  "version": "0.7.3",
+  "version": "0.8.0",
   "repository": {
     "url": "https://github.com/stoneskin/open-memex",
     "source": "github"
@@ -13,7 +13,7 @@
     {
       "registryType": "npm",
       "identifier": "open-memex",
-      "version": "0.7.3",
+      "version": "0.8.0",
       "runtimeHint": "npx",
       "packageArguments": [
         {

package/src/cli.ts

@@ -133,8 +133,7 @@ Flags:
   --aliases  alternate phrasings of this fact (up to 4), indexed with the
              memory so differently-worded searches still match; separate
              with ; (commas also accepted — use ; when an alias itself
-             contains one). Stored only when capture aliases are enabled
-             (init default)
+             contains one). Always on.
   --alias --target  D81: define user vocabulary once — e.g. --alias 香蕉计划
              --target 支付系统重构项目. Later queries mentioning either side
              trigger a second search round on the other side (both

package/src/init.ts

@@ -893,28 +893,20 @@ export async function initProject(opts: {
     // Install-time settings (D19). Non-default answers persist to the JSONC
     // config file; `open-memex config set` changes them later.
     const patch: Record<string, unknown> = {};
-    const keywordCaptureEnabled = await askBool(
-      "Auto-capture keywords like remember… / note that… into memory?",
-      DEFAULT_CONFIG.keywordCaptureEnabled,
-    );
-    if (keywordCaptureEnabled !== DEFAULT_CONFIG.keywordCaptureEnabled)
-      patch.keywordCaptureEnabled = keywordCaptureEnabled;
+    // Keyword auto-capture is always on (Stone 2026-10-07): no init
+    // question — there is no reason to turn it off. The
+    // `keywordCaptureEnabled` config key is still honored if set manually.
     const injectOnFirstTurn = await askBool(
       "Inject relevant memories when a session starts?",
       DEFAULT_CONFIG.injectOnFirstTurn,
     );
     if (injectOnFirstTurn !== DEFAULT_CONFIG.injectOnFirstTurn)
       patch.injectOnFirstTurn = injectOnFirstTurn;
-    // D61: capture-time aliases — the agent may attach its own alternate
-    // phrasings to each memory so differently-worded questions still find it.
-    // Distinct from D80's automatic index-time synonym expansion, which
-    // applies regardless of this setting.
-    const captureAliases = await askBool(
-      "Let the agent attach its own alternate phrasings (aliases) to memories? (The built-in synonym map applies regardless.)",
-      DEFAULT_CONFIG.captureAliases,
-    );
-    if (captureAliases !== DEFAULT_CONFIG.captureAliases)
-      patch.captureAliases = captureAliases;
+    // D61 capture-time aliases are always on (Stone 2026-10-07): the agent
+    // may always attach its own alternate phrasings — no init question.
+    // (Distinct from D80's automatic index-time synonym expansion, which
+    // also always applies.) The `captureAliases` config key is still
+    // honored if someone sets it manually; init just never asks anymore.
     if (Object.keys(patch).length > 0) {
       const file = saveConfig(patch);
       console.log(

package/src/tools/ops.ts

@@ -101,7 +101,7 @@ export const aliasesArg = z
   .array(z.string())
   .optional()
   .describe(
-    "Optional: alternate phrasings of this fact — synonyms, another way a question might be worded, equivalents in the user's other language (e.g. 节假日 for 'public holidays'). They are indexed with the memory so differently-worded questions still match. Only used when the install has capture aliases enabled (init default). Send at most 4; extras and blanks are dropped silently, never an error.",
+    "Optional: alternate phrasings of this fact — synonyms, another way a question might be worded, equivalents in the user's other language (e.g. 节假日 for 'public holidays'). They are indexed with the memory so differently-worded questions still match. Always on. Send at most 4; extras and blanks are dropped silently, never an error.",
   );
 
 export const memoryAddArgs = {
@@ -350,8 +350,8 @@ export async function addMemory(
   const fm = buildFrontmatter(s, {
     type: args.type ?? "fact",
     tags: args.tags ?? [],
-    // D61: aliases are stored only when the install enables them (init
-    // asks once, default on); normalize caps at 4 and drops junk silently.
+    // D61: aliases are always stored (Stone 2026-10-07: init no longer asks;
+    // default on). Normalize caps at 4 and drops junk silently.
     // Aliases pass through the same redaction as content (write-path
     // invariant) — an alias carrying a token gets masked, not stored raw.
     aliases: cfg.captureAliases