Search Memory (Semantic)

Search through memory episodes using Claude's semantic understanding, not just keyword matching.

Instructions for Agent

1. Find All Episodes

Get configuration path:

bash

Use Bash: echo $YW_CONFIG_REPO_PATH

If empty or not set, return error:

code

Error: YW_CONFIG_REPO_PATH not configured.

Please set in ~/.claude/settings.json:
{
  "env": {
    "YW_CONFIG_REPO_PATH": "C:\\Users\\username\\repos\\yoshiwatanabe-configurations"  (Windows)
    "YW_CONFIG_REPO_PATH": "/mnt/c/users/username/repos/yoshiwatanabe-configurations"  (WSL)
  }
}

Find all episode files:

Use the path from YW_CONFIG_REPO_PATH environment variable:

code

Use Glob tool with pattern: {YW_CONFIG_REPO_PATH}/domains/dev/memory/episodes/*.md

Examples:

•
Windows: If YW_CONFIG_REPO_PATH is C:\Users\username\repos\yoshiwatanabe-configurations, then glob for: C:\Users\username\repos\yoshiwatanabe-configurations\domains\dev\memory\episodes\*.md
•
WSL/Linux: If YW_CONFIG_REPO_PATH is /mnt/c/users/username/repos/yoshiwatanabe-configurations, then glob for: /mnt/c/users/username/repos/yoshiwatanabe-configurations/domains/dev/memory/episodes/*.md

Note: Replace "username" with your actual username. The agent will use the actual value from your YW_CONFIG_REPO_PATH environment variable.

If Glob returns empty:

code

Error: No episode files found.

Checked: {YW_CONFIG_REPO_PATH}/domains/dev/memory/episodes/
Directory exists but no episodes saved yet.

Use /save-memory to create your first episode.

Sort by filename (most recent first) and limit to 50 most recent episodes if there are many.

2. Read Episode Frontmatter

For each episode file:

code

Use Read tool: Read first 40 lines (YAML frontmatter + summary)

Extract from YAML:

•id: Episode ID
•timestamp: When created
•machine: Which machine
•os: Operating system
•repository.name: Repository
•repository.branch: Git branch
•repository.commit: Commit hash (show first 7 chars)
•summary: Episode summary
•keywords: Keywords list
•context.tags: Tags list

3. Semantic Analysis

CRITICAL: Use semantic understanding, not keyword matching!

Analyze which episodes are relevant to user's query by:

•Understanding query intent (what is the user really asking?)
•Considering synonyms and related concepts
•Looking at context in summary, keywords, and tags
•Weighing recency (recent work often more relevant)

Examples of semantic understanding:

•Query: "plugin development" → Match: "Claude Code extensions", "marketplace", "skills"
•Query: "authentication" → Match: "OAuth", "login flow", "security tokens", "auth"
•Query: "what did I do last week?" → Match: Recent episodes by timestamp

Don't just grep for exact words - understand meaning!

4. Rank Results

Select top {limit} most semantically relevant episodes.

Sort by:

•Relevance to query (primary)
•Recency (secondary tiebreaker)

5. Format Output

For each result:

code

Found {count} episodes matching "{query}":

1. {Summary first sentence} ({relative_date})
   Machine: {machine} ({os})
   Repository: {repo_name} ({branch})
   Commit: {first_7_chars_of_commit}

   {Full summary from episode}

   → Why relevant: {Explain semantic connection to query}

2. {Next episode...}

Relative dates:

•Today → "Today"
•Yesterday → "Yesterday"
•This week → "3 days ago"
•Older → "Jan 15, 2026"

If no relevant episodes:

code

No episodes found matching "{query}" semantically.

You have {total_count} episodes. Try:
- Broader terms: "authentication" vs "OAuth2 PKCE flow"
- Different phrasing: "API work" vs "endpoint development"
- /list-recent-repos to see recent activity

6. Explanation Quality

Always explain WHY each episode matches. Examples:

✅ Good: "Relevant because: Discusses plugin architecture and marketplace setup" ✅ Good: "Relevant because: Authentication work using OAuth, matches your query" ❌ Bad: "Relevant because: Contains keyword 'plugin'" ❌ Bad: "Relevant because: Recent"

Advantages Over Keyword Search

✅ Understands synonyms (auth = authentication = OAuth) ✅ Contextual (knows "marketplace" relates to "plugins") ✅ Natural queries ("what did I work on?" vs keywords) ✅ Explains relevance (not just shows matches)

Example Queries

Broad:

•"What did I work on this week?"
•"Show me authentication work"

Specific:

•"Which repo has OAuth implementation?"
•"When did I work on marketplace plugin?"

Conceptual:

•"Security improvements"
•"Cross-platform fixes"