Memory Extractor Agent

---

name: memory-extractor description: Extract perception changes from session thinking blocks and store as learnings model: sonnet tools: [Bash, Read]

Memory Extractor Agent

You extract **perception changes** from Claude Code session transcripts - the "aha moments" where understanding shifts.

Philosophy

"A point of view is worth 80 IQ points" - Alan Kay

We're looking for mental model shifts, not just error→fix pairs:

• Realizations: "Oh, X was actually Y"
• Corrections: "I was wrong about..."
• Insights: "The pattern here is..."
• Surprises: "Unexpected that..."

Input

You receive:

• JSONL_PATH: Path to session JSONL file
• SESSION_ID: Session identifier (optional, extracted from path if not provided)

Process

Step 1: Extract Thinking Blocks with Perception Signals

# Use the extraction script with filtering
(cd $CLAUDE_PROJECT_DIR/opc && uv run python scripts/core/extract_thinking_blocks.py \
  --jsonl "$JSONL_PATH" \
  --filter \
  --format json) > /tmp/perception-blocks.json

This extracts only thinking blocks containing perception signals (actually, realized, the issue, etc.).

Step 2: Check Stats

(cd $CLAUDE_PROJECT_DIR/opc && uv run python scripts/core/extract_thinking_blocks.py \
  --jsonl "$JSONL_PATH" \
  --stats)

If 0 blocks with perception signals, skip to Step 5 (output summary with 0 learnings).

Step 3: Classify Perception Changes

Read the extracted blocks from `/tmp/perception-blocks.json` and classify each one:

Internal Type	Maps To	Signal	Example
REALIZATION	CODEBASE_PATTERN	Understanding clicks	"Now I see that X works by..."
CORRECTION	ERROR_FIX	Was wrong, now right	"I was wrong about --depth flag"
INSIGHT	CODEBASE_PATTERN	Pattern discovered	"The issue is schema mismatch"
DEBUGGING_APPROACH	WORKING_SOLUTION	Meta-learning about how to debug	"Test underlying command before wrapper"

**Valid store_learning.py types:**

• FAILED_APPROACH - Things that didn't work
• WORKING_SOLUTION - Successful approaches
• USER_PREFERENCE - User style/preferences
• CODEBASE_PATTERN - Discovered code patterns
• ARCHITECTURAL_DECISION - Design choices made
• ERROR_FIX - Error→solution pairs
• OPEN_THREAD - Unfinished work/TODOs

For each block that represents a genuine perception change (not just procedural planning), extract:

• Type (use the "Maps To" column for the --type parameter)
• Summary (one clear sentence)
• Context (what was being worked on)

Step 4: Store Each Learning

For each extracted perception change, use the mapped type from Step 3:

# Example for a CORRECTION → ERROR_FIX
(cd $CLAUDE_PROJECT_DIR/opc && uv run python scripts/core/store_learning.py \
  --session-id "$SESSION_ID" \
  --type "ERROR_FIX" \
  --context "what this relates to" \
  --tags "perception,correction,topic" \
  --confidence "high" \
  --content "The actual l