Working Memory Management
Private scratchpad for maintaining context across sessions. User does not read this — be candid.
File Location
.claude/context/working-memory.md (auto-loaded every message)
What to Record
Operational context:
- •Blockers, awaiting-input states, pending decisions
- •Deadlines and time-sensitive items
- •Status of in-flight work
Observations & reflections:
- •User preferences and working patterns I've noticed
- •Things that seem off or concerning (missed deadlines, avoidance patterns)
- •Strategic notes about priorities or approach
Planning notes:
- •Things to raise or check on
- •Reminders to self about how to handle situations
- •Questions to ask when opportunity arises
What NOT to Record
- •Event records (→ diary)
- •Completed items (delete once done)
- •Duplicates of Todoist tasks or README content
Entry Format
code
[YYYY-MM-DD] [Project?] Note content here
Examples:
- •
[2026-01-08] [SV USA] Awaiting John's input on 4 questions (Fri 10 Jan). - •
[2026-01-08] [Career] User says gentle nudges OK — help keep it moving. - •
[2026-01-08] [Observation] Invoices have been overdue 3x now — might need reminder system.
When to Update
- •User shares important info — preferences, decisions, blockers
- •End of day — capture context before session ends
- •After summaries — note new insights or status changes
- •Before compacting — save critical context
- •When I notice patterns — observations worth remembering
Maintenance — RUTHLESS TRIMMING
- •Delete entries >7 days old (unless still actively relevant)
- •Delete records of what happened (diary's job)
- •Delete completed/resolved items
- •Delete duplicates of Todoist/README content
- •Consolidate repetitive entries into single current-state notes
- •When in doubt, delete — this is a scratchpad, not an archive
- •One line per note — keep it scannable
Integration Points
- •
/end-day— update before wrapping up - •
/summary— update with new insights - •
/resumeday— review auto-loaded context - •PreCompact hook — save critical context before compacting