doobidoo/mcp-memory-service v8.13.4

v8.13.4 - Critical Memory Hooks Timestamp Fix

on GitHub

🔧 Critical Bugfix Release

This release fixes a critical bug in memory awareness hooks that prevented recent memories from surfacing correctly.

Fixed

Memory Hooks Showing Incorrect Ages (#195)

• Problem: Memory hooks reported ages of 20,371 days when actual age was 6 days
• Impact: Recent memories didn't surface, auto-calibration incorrectly triggered
• Root Cause: HTTP API returns timestamps in SECONDS but JavaScript Date() expects MILLISECONDS
  • API: 1758344479.729 (seconds)
  • JavaScript interpreted as: 1758344479ms = Jan 21, 1970 (55 years ago!)
• Fix: Convert timestamps from seconds to milliseconds (× 1000)
  • File: claude-hooks/utilities/memory-client.js (lines 273-294)
  • Commit: 5c54894

Results

Before Fix:

avgAge: 20371 days
medianAge: 20371 days
recentPercent: 0%
isStale: true

After Fix:

avgAge: 6 days ✅
medianAge: 5 days ✅
recentPercent: 100% ✅
isStale: false ✅

Impact

✅ Recent memories (< 7 days) now surface correctly
✅ Auto-calibration works properly
✅ Git context weight adjusts based on actual ages
✅ No more false "stale memory" warnings

Deployment

Memory hooks are loaded from the repository automatically. No server restart required.

Full Changelog: https://github.com/doobidoo/mcp-memory-service/blob/main/CHANGELOG.md#8134---2025-10-30