Memory Keeper (Proactive Context Maintenance)

Memory Keeper automates context synchronization by detecting staleness triggers—code changes, task completions, phase transitions—and proactively prompts you to sync. Upon confirmation, it updates active_context.md, tasks_plan.md, and lessons-learned.md, eliminating manual checks and ensuring fresh information for your AI assistant.

Memory sync triggers include context older than 2 hours, new git commits, task completion events, phase transitions, constitutional violations, and quality gate failures. Memory Keeper monitors active_context.md modification time, git commit history, and task markers to detect these conditions automatically.

Yes. Memory Keeper integrates with git to monitor commit history and works within dynamic coding assistant and collaboration workflows. It requires jq and git as dependencies and monitors cross-file consistency across active_context.md, tasks_plan.md, and test events, making it suitable for team environments.

Use user-initiated commands 'Sync memory', 'Update context', or 'Capture learnings' to trigger an immediate check. Memory Keeper prompts for your confirmation before executing the /memory-sync command, giving you control over when updates occur.

Memory Keeper logs the detection reason and prompts you with specific actions before proceeding. Upon your confirmation, it executes /memory-sync to update all relevant memory files, capturing learnings and maintaining consistency across your project's context and task tracking.

Memory Keeper's core dependencies are jq and git. It integrates with Read, Write, and Bash tools for memory file operations and requires a structured workflow with active_context.md, tasks_plan.md, and phase markers. Custom integrations are possible through script and reference components.