v13.12.0
thedotmack/claude-memv13.12.0Jul 22, 2026by thedotmack
AI Summary
Introduces a Two-Lane Cloud Sync architecture for cmem.ai Pro, moving sync to a Durable Object-based hub with offline support and near-real-time nudges.
Key Highlights
- New Two-Lane Cloud Sync architecture with Durable Objects.
- Sync is OFF by default; requires configuration via CLAUDE_MEM_CLOUD_SYNC_HUB_URL.
- Includes schema migration v41 and hardened verifier authentication.
- Features offline persistence and advisory WebSocket speed layer.
New Features
- Two-Lane Cloud Sync
- Cloud sync status API
Full Release Notes
## Two-Lane Cloud Sync (cmem.ai Pro) This release ships the complete two-lane sync architecture between your local claude-mem database and the cmem.ai sync hub (PR #3333): - **Per-user Durable Object sync hub** — a Cloudflare Worker (`workers/sync-hub`) serving isolated HTTP push/pull lanes per user (Phase 1) - **Client apply path + schema migration v41** — deterministic application of remote changes into the local SQLite store (Phase 2) - **Hub push/pull transport + mutation outbox** — local mutations queue durably and survive offline periods and retries (Phase 3) - **Advisory WebSocket speed layer** — near-real-time sync nudges; correctness never depends on the socket staying up (Phase 4) - **Guardrails + monitoring** — kill switch, watchdog, canary, and a full sync-matrix E2E suite (Phase 5) - **Canonical v2 projection pipeline** and SyncHub-only client cutover - Hardened verifier authentication on the sync hub **Sync is OFF by default.** `CLAUDE_MEM_CLOUD_SYNC_HUB_URL` defaults to empty — nothing leaves your machine unless you configure a hub URL (see the `cloud-sync` skill or https://docs.claude-mem.ai/cloud-sync). ### Fixes - Restored process-global `mock.module` cleanup that broke CI under Linux readdir ordering