CHROMADB PUB_DATE: 2026.04.26

CLAUDE-MEM 12.4.X: RELIABILITY OVERHAUL FIXES SILENT DATA LOSS AND SLASHES RESTART LOAD

claude-mem’s 12.4.x releases quietly fix a months-long queue-drain bug, harden session/migration logic, and remove heavy startup scans. The latest cut, [v12.4....

claude-mem’s 12.4.x releases quietly fix a months-long queue-drain bug, harden session/migration logic, and remove heavy startup scans.

The latest cut, v12.4.7, finishes a “cynical deletion” sweep that removes brittle defenders/tolerators, adds multi-account isolation via CLAUDE_MEM_DATA_DIR and per-UID ports, pins chroma-mcp versions, and introduces stricter trust boundaries.

Earlier drops fixed a silent observation loss bug on session end and /clear v12.4.4, killed infinite context-overflow retries and cleaned polluted rows with a one-shot migration (v12.4.2, v12.4.3), and self-healed missing DB columns that broke fresh installs v12.4.5.

A restart hotspot was also removed: watermark caching stops Chroma metadata rescans on boot, taking CPU from 422% to near-zero on restarts v12.4.1.

[ WHY_IT_MATTERS ]
01.

Pending observations are no longer dropped on benign session clears, reducing hidden data loss in agent memory.

02.

Restarts stop thrashing CPU due to Chroma rescans, improving stability and startup time.

[ WHAT_TO_TEST ]
  • terminal

    Simulate /clear, logout, and crash-restart flows; confirm pending observations complete and aren’t abandoned.

  • terminal

    Cold-restart workers at scale; validate Chroma CPU stays low and watermarks advance correctly under partial failures.

[ BROWNFIELD_PERSPECTIVE ]

Legacy codebase integration strategies...

  • 01.

    Upgrade to v12.4.7, back up SQLite, and let the one-shot cleanup run; set CLAUDE_MEM_SKIP_CLEANUP_V12_4_3=1 only if you manage cleanup yourself.

  • 02.

    Check port isolation (CLAUDE_MEM_DATA_DIR, CLAUDE_MEM_WORKER_PORT) and verify DB migrations, especially observations.metadata (Migration 30).

[ GREENFIELD_PERSPECTIVE ]

Fresh architecture paradigms...

  • 01.

    Adopt the stricter trust boundary (CLAUDE_MEM_INTERNAL=1) and pinned chroma-mcp for reproducible installs.

  • 02.

    Design agent workflows assuming fresh-session resets on overflow and strict SSE/pagination filters stay in sync.

Enjoying_this_story?

Get daily CHROMADB + SDLC updates.

  • Practical tactics you can ship tomorrow
  • Tooling, workflows, and architecture notes
  • One short email each weekday

FREE_FOREVER. TERMINATE_ANYTIME. View an example issue.

GET_DAILY_EMAIL
AI + SDLC // 5 MIN DAILY