[FEATURE] time-based reminders/triggers in auto-memory (MEMORY.md)

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Claude Code's auto-memory (MEMORY.md) persists across sessions but has no concept of time-based triggers. Users cannot set reminders like:

• "After 2026-06-01, check if law X has taken effect and review its final state"
• "Every quarter, check for firmware/driver updates for component Y"
• "In 2 weeks, follow up on topic Z"

Currently, memory entries are passive — Claude only references them if they seem relevant to the current task. There is no mechanism to proactively surface time-sensitive notes at session start.

Proposed Solution

Add a structured reminder system to auto-memory:
## Reminders

• [2026-06-01] Check final state of regulation XYZ
• [quarterly] Check for Intel AX210 WiFi firmware updates
• [2026-03-15] Follow up on 5.1 surround system purchase decision

At session start, Claude Code could:

1. Compare current date against stored reminder dates
2. Surface due/overdue reminders before proceeding
3. Allow snooze, dismiss, or mark as done
4. Support one-time dates ([2026-06-01]) and recurring intervals ([quarterly], [monthly])

Use Cases

• Regulatory/legal tracking — reminder after effective date
• Hardware/software lifecycle — periodic driver/firmware update checks
• Purchase decisions — re-evaluate market after expected product launches
• Project milestones — revisit architecture decisions after dependency updates

Why This Matters

Auto-memory persists knowledge across sessions. Time-awareness would add intent — turning Claude Code from a purely reactive assistant into one that helps track commitments over weeks and months.

Alternative Solutions

• Manual "reminder check" keyword at session start — defeats the purpose
• External cron/desktop notifications — no Claude context attached
• Writing "always ask about X" in MEMORY.md — unreliable, often ignored if session topic differs
• Always start a background Agent evaluating a separate notifications.md

Priority

Low - Nice to have

Feature Category

Interactive mode (TUI)

Use Case Example

• Regulatory/legal tracking — reminder after effective date
• Hardware/software lifecycle — periodic driver/firmware update checks
• Purchase decisions — re-evaluate market after expected product launches
• Project milestones — revisit architecture decisions after dependency updates

Additional Context

_No response_