Memhub v1.0.0

Memhub 1.0 is the architecture-convergence release. It replaces the historical Plugin/Bridge side channel with one MCP runtime and one durable memory core, while keeping Local and Server deployments as two network views of the same runtime.

One runtime, two network entries

• Local clients connect directly to the loopback MCP endpoint (default 127.0.0.1:3001/mcp).
• Server deployments expose that same MCP runtime through Cloudflare Access/Tunnel or another authenticated reverse proxy; there is no second MCP implementation.
• The legacy Agent Plugin, Bridge process, port 17861, device-token ingress, and standalone /capture, /memhub/context, and /memhub/lifecycle side-channel endpoints are retired.
• Local and Server installers now share one stack implementation. Server is Local plus authenticated public ingress, not a parallel runtime.

Explicit memory and project state

• conversation_id is no longer a project-routing, Branch-binding, Todo, or L1→L2 grouping key. Project/workspace evidence is explicit and Branches are explicit project-local workstreams.
• The L1 contract is memmy_context → memmy_turn open → work → memmy_turn commit; new L1 events use durable actor_id provenance and one deterministic Core session per event.
• Existing historical L1 records using device_id remain readable without an eager data migration.
• L2/L3/L4 exact evidence references, governed Project Architecture writes, explicit-user-authorized L3/L4 replacement, progressive result transport, hydration telemetry, consolidation, and project-state visualization are part of the unified runtime.

Runtime, release, and recovery

• Linux and Windows Local/Server packages use the same Core + MCP process model and common installer logic.
• Release builds clean dist/ before compilation so removed runtime modules cannot survive as stale JavaScript artifacts.
• Immutable runtime releases and fail-closed cutover checks keep the Memory Core and Gateway independently recoverable.
• Crash recovery, distillation idempotency, privacy filtering, project isolation, installer ownership, and Cloudflare boundary checks remain covered by the current test matrix.

Breaking changes

• Remove any client configuration that points to port 17861 or depends on the retired Plugin/Bridge lifecycle hooks.
• Local MCP clients should connect directly to the loopback MCP runtime; remote clients should use the authenticated public MCP URL.
• Automation that depended on the retired HTTP capture/context/lifecycle endpoints must move to MCP tools, primarily memmy_context and memmy_turn.

ChatGPT custom app migration

If you use Memhub through a ChatGPT custom MCP app, refresh the app's tool/actions snapshot after upgrading to v1.0.0, then start a new chat before validating the schema. v1.0.0 removes the retired conversation-binding and Bridge-era tool inputs, and ChatGPT does not automatically replace an already-approved frozen tool snapshot when the MCP server changes.

Memhub v0.2.6

This release consolidates the L1 Capture → Core ingestion → distillation queue
recovery fixes, stricter Core/Gateway authentication and failure reporting,
and fail-closed deployment and process ownership checks. The memory hierarchy
and existing account/project identity boundaries remain unchanged.

Capture, distillation and safety

• Preserve immutable Core ingest intent and idempotent request identity across
  crashes, retries and concurrent recovery. Only durable Core-ingested evidence
  can be reconciled into the L2 queue; ambiguous legacy records remain subject
  to individual review instead of automatic bulk replay.
• Add fault-injection and real-Core integration regressions for Core/marker/
  enqueue crash windows, concurrent discovery and lease handling, L3/L4
  continuation and recovery, plus HTTP/MCP error classification.
• Keep external active-writer guards fail-closed when the lock or owner
  cannot be confidently reconciled. No release script clears a writer lock.

Install, recovery and cross-platform QA

• Make Linux fresh-install entrypoints reject existing state or conflicting
  user systemd units rather than rotate credentials or overwrite routes.
  Provide a separate read-only generic Linux preflight covering credentials,
  service dependencies, exact paths and protected state.
• Exercise consistent Core and Capture-index SQLite WAL backups and rollback
  with disposable data. A separate real-source v0.2.2 → v0.2.6 → restored
  v0.2.2 Linux Core/Gateway rehearsal confirms device-authenticated Capture
  and retained historical account, token and L1 state.
• Move Windows Local/Server old-task ownership checks before StateRoot
  creation, dependency preparation or credential writes; recheck the task set
  before adoption. Actual PowerShell installer refusal is exercised on Windows
  with a Task Scheduler shim. Real legacy task migration remains gated on
  exact target identity, backup and independent cutover verification.
• Keep release evidence separate from deployment evidence. A package or code
  passing tests does not by itself certify a production cutover.

Production rollout and existing-install migration remain separate acceptance gates; no automatic credential rotation, destructive data cleanup, legacy Task Scheduler takeover or external writer-lock removal is included in this release.

Memhub v0.2.5 — Documentation and verified Complete installers

Memhub v0.2.5

Documentation, repository and distribution alignment for the current Memhub runtime. This release does not change the L1–L4 memory hierarchy.

What changed

• Reworked the English and Chinese READMEs and public documentation navigation around account/project identity, evidence-backed L1–L4, Retrieval v1, project-local Branches, Skills, first-class Todos, MCP, Web Workspace, and Local/Server editions.
• Removed superseded repair, simplification and evolution plans from the active documentation tree. They remain recoverable from Git history. Runtime migration and compatibility code required by supported deployments is retained.
• Removed the retired operator-specific route from current documentation. Public product documentation is available at https://phsanqi.github.io/Memhub/.
• Aligned runtime and Plugin versions to 0.2.5, changelog, regression checks, release manifests and installers.
• Fixed Complete packages missing the Web logo assets required by the Gateway. The runtime smoke now verifies these assets before installation.
• Hardened Windows Local/Server installation when legacy scheduled tasks are absent and corrected state-directory ACL username expansion.
• Replaced fragile PowerShell-to-Node inline token generation with native cryptographic randomness. Windows Complete CI checks the generated Local and Server Memory tokens.
• Linux systemd deployment uses memhub-stack.target to manage Core, Gateway and optional Bridge together.

Downloads

Choose one of the four edition packages (Linux/Windows × Local/Server). The Complete Linux/Windows archives additionally bundle Node.js 22.20.0 and include install-complete.sh / install-complete.ps1 for an installation without a separately installed Node.js runtime. Standalone installers are attached for convenience. Verify archives and installers with SHA256SUMS.txt; inspect release-manifest.json and complete-assets.json for package metadata.

Documentation: English README · 中文 README · Documentation index · Changelog.

中文摘要

本次发布将中英文 README、公开文档目录、GitHub 简介、安装包与当前生产架构对齐；旧修复/迁移方案从当前文档树清理，历史仍可通过 Git 查看。记忆模型仍为 L1 原始证据 → L2 项目时间线 → L3 项目规则与经验 → L4 跨项目画像，Skill 是独立能力平面。公开产品文档为 https://phsanqi.github.io/Memhub/。

Memhub v0.2.2

Memhub v0.2.2

Memhub v0.2.2 consolidates the current product architecture into one release: project-aware L1–L4 memory, bounded retrieval, Branch context, executable Skills, project Todos, progressive MCP result transport, supervised Local/Server runtimes, and a cleaned public documentation surface.

Highlights

• Retrieval v1: account/project governance first, then semantic + lexical second-stage ranking, deduplication and bounded Context Capsules.
• Branch context: project-local workstream context without creating another memory hierarchy.
• Skill lifecycle: compact candidates, explicit load/invoke, execution telemetry, versioned revision and retirement.
• L1 → L2 → L3 → L4: evidence-bounded distillation with stable canonical artifacts and cross-project gating for L4.
• Runtime stability: unified process ownership, Linux systemd stack target, Windows/direct supervisor, Bridge queue recovery and dedicated Cloudflare watchdog.
• Large-result transport: progressive account-scoped result spool for oversized MCP responses.
• Documentation reset: README rewritten; docs reorganized into architecture, operations, maintainers, internal and archive sections. Historical repair/simplification notes no longer sit beside Current Truth.
• Public product documentation: https://phsanqi.github.io/Memhub/

Packages

Convenience/source packages:

• Linux Local
• Linux Server
• Windows Local
• Windows Server

Self-contained Complete packages:

• Linux x64 Complete — bundled Node.js runtime and native dependencies
• Windows x64 Complete — bundled Node.js runtime and target-native dependencies

Bootstrap installers are also attached for both normal and Complete installation paths. Verify downloads with SHA256SUMS.txt.

Validation

• Full npm test suite passed on the release tree.
• Release/package checks passed.
• Linux Complete bundled-runtime smoke passed.
• Windows Complete packaging validates target-native binaries; the repository also runs the dedicated Windows runtime smoke workflow against this release line.

---

中文摘要

v0.2.2 把当前 Memhub 的完整产品形态正式收口到一个版本：L1–L4 项目感知长期记忆、Retrieval v1、Branch 工作流上下文、Skill 执行生命周期、项目 Todo、大结果渐进传输，以及 Local/Server 的统一进程管理。

这一版同时重写了 GitHub README，并把全部公开文档重新整理为 Architecture / Operations / Maintainers / Internal / Archive 五类；旧的迁移、修复、简化记录只保留在 Archive，不再与 Current Truth 混放。

公开产品文档： https://phsanqi.github.io/Memhub/

Memhub v0.2.1

Memhub v0.2.1

This release focuses on one-line installation and first-run ergonomics, while also carrying the Todo, workspace readability, Control Plane performance, Bridge reliability, and Plugin fixes shipped on main after v0.2.0.

One-line install

Linux Local:

curl -fsSL https://github.com/PhSanqi/Memhub/releases/latest/download/install.sh | bash

Windows Local:

$p=Join-Path $env:TEMP 'memhub-install.ps1'; iwr https://github.com/PhSanqi/Memhub/releases/latest/download/install.ps1 -OutFile $p; & $p; rm $p

Linux Server:

curl -fsSL https://github.com/PhSanqi/Memhub/releases/latest/download/install.sh | bash -s -- --edition server --public-host memory.example.com

Windows Server:

$p=Join-Path $env:TEMP 'memhub-install.ps1'; iwr https://github.com/PhSanqi/Memhub/releases/latest/download/install.ps1 -OutFile $p; & $p -Edition server -PublicHost memory.example.com; rm $p

Prerequisite: Node.js 20+ and npm.

The bootstrap resolves the latest stable Release, downloads the correct Local/Server package for the current platform, verifies SHA-256, keeps the application files in a persistent directory, and runs the normal edition installer.

Included assets

• Linux Local
• Linux Server
• Windows Local
• Windows Server
• install.sh
• install.ps1
• SHA256SUMS.txt
• release-manifest.json

Other updates since v0.2.0

• First-class project Todo MCP support.
• Readable L2 chronological timeline and expanded L3/L4 workspace views.
• Faster Control Plane refreshes through lightweight distillation job summaries.
• Bridge queue race and lifecycle drain fixes.
• Correct handling for colon-bearing L1 evidence IDs.
• Codex Plugin Skill metadata compatibility fix.

---

中文摘要

v0.2.1 重点解决安装体验：Linux / Windows、Local / Server 都可以通过固定的一键安装脚本，从 GitHub 最新稳定 Release 自动下载正确安装包、校验 SHA-256、持久化解压并执行正式安装器，不再要求先 clone 整个仓库。

前置要求为 Node.js 20+ 与 npm。

Memhub v0.2.0

Memhub 0.2.0 is the first unified L1-L4 release. The same source commit ships Server and Local editions on Linux and Windows.

Memory model

• L1 is the authoritative original-conversation evidence layer. Per-turn JSON remains the source of truth; capture-index.sqlite is a rebuildable metadata index for filtering, counts and scheduling.
• L2 is the canonical project timeline.
• L3 is the canonical project rules/experience profile.
• L4 is the account-scoped cross-project user profile and requires evidence from at least two project L3 artifacts.
• Skill remains an orthogonal reusable capability layer.

MCP and distillation

• The public MCP surface is reduced to six tools: memmy_turn, memmy_context, memhub_distill, memmy_project_list, memmy_project_manage, and memmy_project.
• Retired memmy_remember, memhub_history_distill, and memhub_evolution tool surfaces are removed.
• Distillation jobs now enforce lease ownership, evidence-layer provenance, project scope and cross-project L4 evidence.
• Canonical L2/L3/L4 artifacts update in place through stable sourceArtifactId identities while write idempotency keys change only when the write body changes.
• memmy_project action=current no longer fails when a transport cannot expose a stable conversation_id; it returns binding_available=false and can canonicalize an explicit project without persisting a fake binding.

Runtime and Control Plane

• L1 indexing is moved to SQLite with crash-recovery dirty tracking; large L1 histories no longer require full raw-file scans for normal UI counts, threshold scheduling or idle scheduling.
• Admin Control Plane adds project create/update/merge/logical-delete, L1→L4 lifecycle visibility, processing policy controls and layer-specific views.
• Web mutation endpoints require JSON and add clickjacking/CSP/referrer protections.
• Cloudflare JIT first-request account refresh is fixed.
• Configurable base-path deployment is retained, including root-path production deployments.

Platform and release

• One shared runtime now backs four supported installation targets: Linux Local, Linux Server, Windows Local and Windows Server.
• @huggingface/transformers is upgraded to 4.3.x; production dependency audit is clean at release preparation time.
• The old Normify runtime is not vendored or executed. Existing architecture Markdown can still be read through the lightweight Architecture Reader compatibility layer.

Migration

Memory Core schema v8 preserves historical rows while moving the durable taxonomy to L1/L2/L3/L4/Skill. Use npm run core:preflight before a production cutover and the documented verify/preserved checks when migrating an existing database.

Memhub v0.1.0

Memhub v0.1.0

Historical v0.1.0 release, consolidated into one release entry.

Packages

• Linux Local
• Linux Server
• Windows Local
• Windows Server

Each platform package is preserved together with its original SHA-256 sidecar.

This release is kept for historical installs. For new deployments, use the latest v0.2.x release line.

---

历史 v0.1.0 发布版本，现合并为一个统一 Release。

保留 Linux / Windows 的 Local / Server 四种安装包及其原始 SHA-256 校验文件。新安装建议优先使用最新 v0.2.x 版本。