memorix 1.8.8 → 1.9.0

package/CHANGELOG.md

@@ -4,6 +4,42 @@ All notable changes to this project will be documented in this file.
 
 ## [Unreleased]
 
+## [1.9.0] - 2026-09-07
+
+### Added
+- **Opt-in multi-device sync** -- adds a project-scoped observation
+  event contract with privacy filtering, local outbox retry, conflict evidence,
+  device-clone protection, bounded relay pulls, and filesystem/GitHub/S3/
+  Postgres transport boundaries. It is disabled by default and keeps local
+  SQLite as the canonical store.
+- **Sync hardening** -- retracts records that become private or agent-targeted,
+  keeps imported observations and sync state atomic, rejects immutable-key
+  collisions, verifies every pulled content hash, and uses stable continuation
+  cursors so large pulls do not skip events.
+- **Resource hardening** -- coalesces deferred vector workers across hook
+  processes, respects retry cooldowns, drains due vector jobs through one
+  recoverable worker, removes the redundant full-document detail cache, and
+  batches startup vector hydration to reduce CPU/RAM peaks without imposing a
+  small corpus limit.
+
+## [1.8.9] - 2026-09-06
+
+### Added
+- **Grok Build integration** -- adds native lifecycle hook capture for session,
+  prompt, tool, compaction, and stop events, plus Grok-specific `AGENTS.md`
+  guidance. Thanks to @RaviTharuma for the original integration.
+
+### Changed
+- **Host-owned Grok MCP** -- `memorix setup --agent grok --global` uses Grok's
+  hook and rules surfaces without writing Grok's `config.toml` or MCP entries.
+- **Agent documentation** -- the English and Chinese README matrices and setup
+  guides now list Grok Build and its trust model.
+
+### Fixed
+- **Safe Grok hook updates** -- preserves unrelated user hooks, removes only
+  Memorix-owned entries, supports `GROK_HOME`, and reports project hook trust
+  accurately without claiming that Memorix can approve it.
+
 ## [1.8.8] - 2026-09-03
 
 ### Changed

package/README.md

@@ -6,7 +6,7 @@
 
 <p align="center">
   <strong>Local-first shared memory layer for AI coding agents.</strong><br>
-  One project memory system for Claude Code, Codex, CodeBuddy Code, Cursor, Windsurf, Copilot, Gemini CLI, OpenCode, OpenClaw, Hermes Agent, Oh-my-Pi, Pi, Kiro, Antigravity, Trae, DeepSeek Harness, WorkBuddy, and any MCP-capable agent.
+  One project memory system for Claude Code, Codex, CodeBuddy Code, Cursor, Windsurf, Copilot, Gemini CLI, OpenCode, Grok Build, OpenClaw, Hermes Agent, Oh-my-Pi, Pi, Kiro, Antigravity, Trae, DeepSeek Harness, WorkBuddy, and any MCP-capable agent.
 </p>
 
 <p align="center">
@@ -85,6 +85,7 @@ Memorix is more than a memory store. It also installs agent integrations, keeps
 | Orchestration and team work | Task planning, worker handoffs, file locks, messages, verification gates, and review loops | `memorix orchestrate`, `memorix team`, `memorix lock` |
 | memcode | A bundled terminal coding agent that already reads and writes the same project memory | `memorix`, `memcode` |
 | CLI and SDK | Scriptable access for automation, imports/exports, diagnostics, and custom integrations | `memorix ...`, `createMemoryClient()` |
+| Optional multi-device sync | Project-scoped, privacy-filtered observation events with local SQLite kept canonical; GitHub JSONL, filesystem, S3, or Postgres relay | `memorix sync store status\|push\|pull` |
 
 <h2 id="works-with-your-agent"><picture><source media="(prefers-color-scheme: dark)" srcset="assets/tags/light/section-agents.svg"><img src="assets/tags/section-agents.svg" alt="Works with every agent" height="32" /></picture></h2>
 
@@ -181,6 +182,11 @@ Memorix connects through the interfaces each agent already supports: plugin pack
 <strong>Any MCP Client</strong><br>
 <sub>stdio or HTTP MCP</sub>
 </td>
+<td align="center" width="12.5%">
+<a href="https://github.com/xai-org/grok-build"><img src="https://github.com/xai-org.png?size=120" alt="Grok Build" width="48" height="48"></a><br>
+<strong>Grok Build</strong><br>
+<sub>native hooks + AGENTS.md</sub>
+</td>
 </tr>
 </table>
 
@@ -213,6 +219,12 @@ CLI, MCP, and HTTP are different entry points:
 - `memorix serve` is the stdio MCP bridge used by IDEs and coding agents. Its default tool profile is `micro`, so agents see only the compact core tool set.
 - `memorix background start` / `memorix serve-http` run the HTTP service for a shared endpoint, dashboard, VPS Docker deployment, or multiple clients.
 
+Multi-device store sync is opt-in and separate from HTTP sharing. It never
+uploads the live SQLite database or WAL files. By default it only relays
+qualified project-visible observations; personal, agent-targeted, candidate,
+ephemeral, and other-project records stay local. Set `MEMORIX_SYNC_PROVIDER` and
+inspect `memorix sync store status --json` before the first push.
+
 <h2 id="install"><picture><source media="(prefers-color-scheme: dark)" srcset="assets/tags/light/section-install.svg"><img src="assets/tags/section-install.svg" alt="Install" height="32" /></picture></h2>
 
 Requirements:
@@ -262,6 +274,7 @@ memorix setup --agent codebuddy --global
 memorix setup --agent omp --global
 memorix setup --agent dsh --global
 memorix setup --agent workbuddy --global
+memorix setup --agent grok --global
 ```
 
 What it installs depends on the target agent, but the goal is the same: make Memorix available wherever you open that agent without asking you to wire every repo by hand.
@@ -281,6 +294,7 @@ What it installs depends on the target agent, but the goal is the same: make Mem
 - Oh-my-Pi: installs an `omp.extensions` package with extension hook events, a `memorix` command, official skills, and writes MCP config.
 - DeepSeek Harness: writes a Memorix `@deepseek-ai/dsh-mcp-client` row into `$DSH_HOME/cordis.patch.yml` (default `~/.dsh/cordis.patch.yml`), appends guidance to the harness `AGENTS.md`, and installs official skills under `$DSH_HOME/skills`. The row follows DSH's own shipped Memorix reference, so tools appear as `mcp__memorix__*`.
 - WorkBuddy: writes a Memorix MCP server row into `~/.workbuddy/mcp.json` (or `<project>/.workbuddy/mcp.json` for project installs) and appends guidance to `AGENTS.md`. Tools appear as `mcp__memorix__*`; there is no hooks surface.
+- Grok Build: installs native lifecycle hooks under `~/.grok/hooks/memorix.json` and guidance in `~/.grok/AGENTS.md`. It leaves Grok's MCP configuration host-owned; project-local hooks require Grok `/hooks-trust`, while global hooks are trusted. Set `GROK_HOME` to use a custom Grok home.
 
 Need a quieter install? Add `--noHooks` for targets where setup can control hook capture separately from the host's official package entry. It keeps MCP and guidance, but skips Memorix hook capture.
 

package/README.zh-CN.md

@@ -6,7 +6,7 @@
 
 <p align="center">
   <strong>面向 AI Coding Agent 的本地优先共享记忆层。</strong><br>
-  让 Claude Code、Codex、CodeBuddy Code、Cursor、Windsurf、Copilot、Gemini CLI、OpenCode、OpenClaw、Hermes Agent、Oh-my-Pi、Pi、Kiro、Antigravity、Trae、DeepSeek Harness 和任何 MCP Agent 共用同一套项目记忆。
+  让 Claude Code、Codex、CodeBuddy Code、Cursor、Windsurf、Copilot、Gemini CLI、OpenCode、Grok Build、OpenClaw、Hermes Agent、Oh-my-Pi、Pi、Kiro、Antigravity、Trae、DeepSeek Harness、WorkBuddy 和任何 MCP Agent 共用同一套项目记忆。
 </p>
 
 <p align="center">
@@ -84,6 +84,7 @@ Memorix 不只是一个记忆库。它还负责安装 Agent 接入、保留有
 | Orchestration 和团队协作 | 任务规划、worker 交接、文件锁、消息、验证门和 review loop | `memorix orchestrate`、`memorix team`、`memorix lock` |
 | memcode | 内置终端 Coding Agent，默认读写同一套项目记忆 | `memorix`、`memcode` |
 | CLI 和 SDK | 给自动化、导入导出、诊断和自定义集成使用的本地接口 | `memorix ...`、`createMemoryClient()` |
+| 可选多设备同步 | 按项目隔离、经过隐私过滤的记忆事件同步；本地 SQLite 仍是主库 | `memorix sync store status\|push\|pull` |
 
 <h2 id="支持你的-agent"><picture><source media="(prefers-color-scheme: dark)" srcset="assets/tags/light/section-agents.svg"><img src="assets/tags/section-agents.svg" alt="Works with every agent" height="32" /></picture></h2>
 
@@ -180,6 +181,11 @@ Memorix 通过目标 Agent 已有的接口接入：插件包、MCP、项目规
 <strong>Any MCP Client</strong><br>
 <sub>stdio or HTTP MCP</sub>
 </td>
+<td align="center" width="12.5%">
+<a href="https://github.com/xai-org/grok-build"><img src="https://github.com/xai-org.png?size=120" alt="Grok Build" width="48" height="48"></a><br>
+<strong>Grok Build</strong><br>
+<sub>原生 hooks + AGENTS.md</sub>
+</td>
 </tr>
 </table>
 
@@ -212,6 +218,11 @@ CLI、MCP 和 HTTP 是不同入口：
 - `memorix serve` 是给 IDE / Coding Agent 使用的 stdio MCP 桥。
 - `memorix background start` / `memorix serve-http` 是 HTTP 服务，用于共享端点、Dashboard、VPS Docker 部署或多客户端。
 
+多设备记忆同步是可选功能，和 HTTP 共享服务不是一回事。它不会上传
+`memorix.db`、WAL 或 SHM 文件。默认只同步当前项目中已确认且项目可见的
+观察记录；个人、指定 Agent、候选、短期和其它项目的记录会留在本地。设置
+`MEMORIX_SYNC_PROVIDER` 后，先运行 `memorix sync store status --json` 再 push。
+
 <h2 id="安装"><picture><source media="(prefers-color-scheme: dark)" srcset="assets/tags/light/section-install.svg"><img src="assets/tags/section-install.svg" alt="安装" height="32" /></picture></h2>
 
 要求：
@@ -260,6 +271,8 @@ memorix setup --agent hermes --global
 memorix setup --agent codebuddy --global
 memorix setup --agent omp --global
 memorix setup --agent dsh --global
+memorix setup --agent workbuddy --global
+memorix setup --agent grok --global
 ```
 
 它会做的事情取决于目标 Agent，但目标是一致的：你以后在哪里打开这个 Agent，Memorix 就可以在哪里被使用，而不是让你一个仓库一个仓库重复配置。
@@ -278,6 +291,7 @@ memorix setup --agent dsh --global
 - CodeBuddy Code：安装用户级本地市场插件到 `~/.codebuddy/memorix-local`，包含 MCP、skills 和 hooks。它不会修改既有的 CodeBuddy 模型、权限或 settings 文件；第三方 hook 仍由 CodeBuddy 自己的 `/hooks` 流程确认。
 - Oh-my-Pi：安装 `omp.extensions` package，包含 extension hook 事件、`memorix` command、官方 skills，并写入 MCP 配置。
 - DeepSeek Harness：向 `$DSH_HOME/cordis.patch.yml`（默认 `~/.dsh/cordis.patch.yml`）写入一行 Memorix `@deepseek-ai/dsh-mcp-client`，向 harness 的 `AGENTS.md` 追加使用规范，并把官方 skills 安装到 `$DSH_HOME/skills`。这一行遵循 DSH 自带的 Memorix 参考配置，因此工具以 `mcp__memorix__*` 形式出现。
+- Grok Build：把原生生命周期 hooks 安装到 `~/.grok/hooks/memorix.json`，把使用规范写入 `~/.grok/AGENTS.md`。Grok 的 MCP 配置仍由 Grok 自己管理；项目级 hooks 需要在 Grok 中执行 `/hooks-trust`，全局 hooks 默认可信；也可以用 `GROK_HOME` 指定自定义 Grok 目录。
 
 如果你想要更安静一点的安装，可以对那些 setup 能独立控制 hook capture 的 target 加 `--noHooks`。它会保留 MCP 和使用规范，只跳过 Memorix 的 hook 自动捕获。