Remembering Conversations

Core principle: Search before reinventing. Searching costs nothing; reinventing or repeating mistakes costs everything.

Mandatory: Use the Search Agent

YOU MUST dispatch the search-conversations agent for any historical search.

Announce: "Dispatching search agent to find [topic]."

Then use the Task tool with subagent_type: "search-conversations":

CODEBLOCK0

The agent will:

1. 1. Search with the search tool
2. Read top 2-5 results with the show tool
3. Synthesize findings (200-1000 words)
4. Return actionable insights + sources

Saves 50-100x context vs. loading raw conversations.

When to Use

You often get value out of consulting your episodic memory once you understand what you're being asked. Search memory in these situations:

After understanding the task:

• - User asks "how should I..." or "what's the best approach..."
• You've explored current codebase and need to make architectural decisions
• User asks for implementation approach after describing what they want

When you're stuck:

• - You've investigated a problem and can't find the solution
• Facing a complex problem without obvious solution in current code
• Need to follow an unfamiliar workflow or process

When historical signals are present:

• - User says "last time", "before", "we discussed", "you implemented"
• User asks "why did we...", "what was the reason..."
• User says "do you remember...", "what do we know about..."

Don't search first:

• - For current codebase structure (use Grep/Read to explore first)
• For info in current conversation
• Before understanding what you're being asked to do

Direct Tool Access (Discouraged)

You CAN use MCP tools directly, but DON'T:

• - INLINECODE3
• INLINECODE4

Using these directly wastes your context window. Always dispatch the agent instead.

See MCP-TOOLS.md for complete API reference if needed for advanced usage.