memorix 1.9.0 → 1.9.2

package/CHANGELOG.md

@@ -4,6 +4,45 @@ All notable changes to this project will be documented in this file.
 
 ## [Unreleased]
 
+## [1.9.2] - 2026-09-11
+
+### Fixed
+- **Non-interactive MCP startup** -- running the package without arguments
+  through piped stdio now starts the MCP server, while a real terminal keeps
+  opening the bundled memcode agent. This makes generic npm MCP launchers and
+  registry handshake checks use the correct protocol entry point.
+- **Maintenance initialization** -- dashboard Consolidate uses its
+  request-scoped observation store, and CLI deduplication initializes the
+  project memory LLM before checking availability.
+
+## [1.9.1] - 2026-09-08
+
+### Changed
+- **Large-scale retrieval** -- SQLite FTS5 is now the persistent lexical
+  candidate index. It stays synchronized on insert, update, delete, and can be
+  rebuilt from the durable observations table.
+- **Disk-backed semantic retrieval** -- the optional local LanceDB shadow index
+  stores only vector IDs and metadata, uses HNSW with scalar quantization once
+  the corpus is large enough, and fuses bounded semantic candidates with FTS5
+  results. Search falls back to Orama when the optional native package is not
+  available.
+- **Lazy large-corpus startup** -- projects above the Orama hydration threshold
+  keep SQLite as the source of truth and do not load the complete observation
+  corpus into the interactive agent process. Detail, export, and maintenance
+  paths can still load the data they explicitly need.
+- **Large-store acceptance** -- adds regression coverage and verified gates for
+  1k, 10k, 40k, and 100k records without reducing the durable memory corpus.
+- **Post-threshold vector writes** -- newly generated vectors still reach the
+  persistent semantic index after the in-memory Orama corpus is released.
+
+### Fixed
+- **Stale lexical index on upsert** -- replace-style SQLite writes could leave
+  old terms in an external-content FTS index. Observation upserts now preserve
+  trigger-visible row updates so old terms are removed.
+- **Optional native dependency bundling** -- LanceDB is resolved at runtime so
+  unsupported platforms or installations without its native binary continue
+  to build and use the FTS5/Orama fallback.
+
 ## [1.9.0] - 2026-09-07
 
 ### Added

package/README.md

@@ -63,7 +63,11 @@ Use Claude Code today, Codex tomorrow, and Cursor in the afternoon. The agent ca
 | Static rule files drift | Gotchas, fixes, and project skills evolve from real work |
 | Parallel agent work gets messy | `memorix orchestrate` coordinates task context, handoffs, locks, verification, and review loops |
 
-Memorix is local-first. SQLite is the canonical store, Orama handles search, and LLM-backed formation/embedding is optional. Without model keys, Memorix still works with local full-text retrieval.
+Memorix is local-first. SQLite is the canonical store. Small projects use the
+in-process Orama path; larger projects use a persistent SQLite FTS5 candidate
+index and, when available, an optional local LanceDB semantic shadow index.
+Both indexes are rebuildable and are never a limit on how many durable memories
+you can keep. LLM-backed formation and embedding remain optional.
 
 ### Capabilities
 
@@ -313,6 +317,11 @@ If your agent only needs a manual MCP entry, use stdio:
 }
 ```
 
+For an npm-based MCP client or registry tester, use the complete command
+`npx -y memorix serve`. The `serve` argument matters: `memorix` without
+arguments opens the bundled memcode terminal agent when run by a human, while
+MCP clients should start the stdio server explicitly.
+
 For a manually managed Claude Code entry, add `"alwaysLoad": true` inside the `memorix` server object. This lets Claude Code expose Memorix tools during print-mode startup; `memorix doctor agents --agent claude` can detect and repair a missing setting.
 
 HTTP is not required for normal setup. Use it only when you intentionally want a shared background service, dashboard, VPS Docker deployment, or multiple clients using the same endpoint. Local development uses the Node service directly and does not require Docker:
@@ -589,6 +598,14 @@ npm test
 npm run build
 ```
 
+## Community
+
+Desktop and shell integrations built on Memorix:
+
+- [omarchy-memorix](https://github.com/mbot11/omarchy-memorix) — a native [Omarchy](https://omarchy.org) shell bar widget: pool stats, live global search, per-project breakdown, recent memories, and a workbench launcher. Read-only over `~/.memorix/data`; no daemons, no telemetry.
+
+Built something on top of Memorix? Open a PR to list it here.
+
 <h2 id="acknowledgements"><picture><source media="(prefers-color-scheme: dark)" srcset="assets/tags/light/section-acknowledgements.svg"><img src="assets/tags/section-acknowledgements.svg" alt="Acknowledgements" height="32" /></picture></h2>
 
 Memorix draws from the MCP ecosystem and prior memory projects such as mcp-memory-service, MemCP, claude-mem, and Mem0. memcode is based on the Pi coding-agent codebase and adapts its terminal-agent model for the Memorix ecosystem.
@@ -601,10 +618,10 @@ Memorix draws from the MCP ecosystem and prior memory projects such as mcp-memor
 
 <a href="https://github.com/AVIDS2/memorix/stargazers">
   <picture>
-    <source media="(prefers-color-scheme: dark)" srcset="assets/star-history-dark.svg">
-    <source media="(prefers-color-scheme: light)" srcset="assets/star-history-light.svg">
-    <img alt="Memorix Star History" src="assets/star-history-light.svg" width="100%">
+    <source media="(prefers-color-scheme: dark)" srcset="https://mem.rglens.com/metrics/star-history-dark.svg">
+    <source media="(prefers-color-scheme: light)" srcset="https://mem.rglens.com/metrics/star-history-light.svg">
+    <img alt="Memorix Star History" src="https://mem.rglens.com/metrics/star-history-light.svg" width="100%">
   </picture>
 </a>
 
-<sub>Generated daily from GitHub stargazer events by GitHub Actions.</sub>
+<sub>Updated automatically from GitHub's privacy-safe star history API. No generated PRs.</sub>

package/README.zh-CN.md

@@ -62,7 +62,7 @@ Memorix 给你已经在用的 AI 编程 Agent 加上一套共享、可检索的
 | 静态规则文件容易过期 | 坑点、修复和项目技能从真实工作中持续沉淀 |
 | 并行 Agent 工作容易乱 | `memorix orchestrate` 负责协调任务上下文、交接、文件锁、验证和 review 流程 |
 
-Memorix 是本地优先的。SQLite 是权威存储，Orama 负责搜索，LLM 记忆整理和 embedding 是可选能力。没有模型 key 时，Memorix 仍然可以用本地全文检索工作。
+Memorix 是本地优先的。SQLite 是权威存储。小项目使用进程内 Orama；数据量较大时，关键词检索使用持久化的 SQLite FTS5 候选索引，并在可用时使用本地 LanceDB 语义影子索引。索引都可以重建，也不会限制你能长期保存多少条记忆。LLM 记忆整理和 embedding 仍然是可选能力。
 
 ### 能力矩阵
 
@@ -310,6 +310,10 @@ memorix setup --agent grok --global
 }
 ```
 
+如果是 npm 方式启动 MCP 客户端或收录平台测试器，请使用完整命令
+`npx -y memorix serve`。`serve` 参数不能省略：人类在终端里直接运行
+`memorix` 会打开内置 memcode，而 MCP 客户端应明确启动 stdio MCP 服务。
+
 如果是手动维护 Claude Code 的 MCP 配置，需要在 `memorix` server 对象里加上 `"alwaysLoad": true`。这样 Claude Code 在 print-mode 启动时就会暴露 Memorix tools；`memorix doctor agents --agent claude` 可以检查并修复缺失的设置。
 
 普通安装不需要 HTTP。只有在你明确需要共享后台服务、Dashboard、VPS Docker 部署，或多个客户端共用一个端点时才使用。本机开发直接运行 Node 服务，不需要 Docker：
@@ -575,10 +579,10 @@ Memorix 借鉴了 MCP 生态和 mcp-memory-service、MemCP、claude-mem、Mem0
 
 <a href="https://github.com/AVIDS2/memorix/stargazers">
   <picture>
-    <source media="(prefers-color-scheme: dark)" srcset="assets/star-history-dark.svg">
-    <source media="(prefers-color-scheme: light)" srcset="assets/star-history-light.svg">
-    <img alt="Memorix Star History" src="assets/star-history-light.svg" width="100%">
+    <source media="(prefers-color-scheme: dark)" srcset="https://mem.rglens.com/metrics/star-history-dark.svg">
+    <source media="(prefers-color-scheme: light)" srcset="https://mem.rglens.com/metrics/star-history-light.svg">
+    <img alt="Memorix Star History" src="https://mem.rglens.com/metrics/star-history-light.svg" width="100%">
   </picture>
 </a>
 
-<sub>由 GitHub Actions 根据 GitHub stargazer 事件每日生成。</sub>
+<sub>由 GitHub 隐私安全的 Star History API 自动更新，不再生成自动 PR。</sub>