hermes-remember

name	hermes-remember
description	Manually extract and store memories from the current session into Archy. Use to checkpoint what's been learned before a /compact, /new, or long context switch.

Hermes Remember

Manually triggers memory extraction for the current session — stores key facts, decisions, and patterns in Archy so they survive session boundaries.

When to use

• Before issuing /compact or /new to preserve context
• When you want to checkpoint important decisions mid-session
• After a productive debugging/design session to ensure nothing is lost
• Any time you want to say "remember this for next time"

Steps

1. Find the current session's transcript — the most recently modified .jsonl under ~/.claude/projects/:

   find ~/.claude/projects -name "*.jsonl" -newer ~/.claude/projects -printf "%T@ %p\n" | sort -n | tail -1
   

2. Read the last 40 user/assistant turns from the file, extracting text content from each entry's message.content array.

3. For each significant fact, decision, or pattern worth remembering, call mcp__archy__memory_store with:

   • The specific memory content (be concrete, not vague)
   • Relevant tags for later retrieval
   • An importance score

4. Report how many memories were stored and what they covered.

What to store

Good candidates:

• Architectural decisions and why they were made
• Files modified and the reason for changes
• Bugs found and how they were diagnosed/fixed
• Patterns or workflows that proved effective
• User preferences expressed during the session
• Technical constraints or context that is non-obvious from the code

Skip: trivial confirmations, obvious facts, one-off commands with no lasting relevance.

Notes

This is the manual trigger for the same extraction that compress_hook.py runs automatically on context compression and session_sweep.py runs on session idle timeout. Use it when you want to guarantee capture without waiting for those triggers.