You know you discussed it. You just can't find it. Native search only works if you remember the exact words.
# Auto mode: semantic + keyword "WebSocket reconnection" Semantic matches: - "Real-time messaging architecture" (discusses connection handling) - "Socket.io vs native WebSockets" (decision session) Keyword matches: - "WebSocket reconnection with exponential backoff" (implementation) - "Fix: WebSocket drops on mobile" (bug fix) Combined: 4 sessions, ordered by relevance.
Finds conceptually related content, even when the words don't match.
# Semantic search finds: - "Performance profiling the API endpoints" (keyword: latency, P99) - "Optimizing database queries" (keyword: N+1, indexing) - "CDN and caching strategy" (keyword: cache hit rate) - "React bundle size reduction" (keyword: tree-shaking, lazy loading) None of these mention "faster," but all are about performance.
Exact matching when you know the specific term.
Found 2 exact matches: 1. "Security patch for CVE-2026-1234" (March 3) Message 12: "The CVE-2026-1234 vulnerability affects..." 2. "Dependency audit" (March 10) Message 7: "CVE-2026-1234 is patched in v2.3.1..."
| Filter | Example | Description |
|---|---|---|
| source | "ccode", "claude_chat" | Filter by platform |
| role | "human", "assistant" | Only your messages or Claude's |
| after / before | "2026-03-01" | Date range |
| mode | "semantic", "keyword", "auto" | Search strategy |
| freshness | "recent", "balanced", "relevant" | Recency weighting |
| depth | "focused", "session", "connected" | Graph traversal depth |
| match | "any", "all", "exact" | Keyword matching mode |
| limit | 20 (default, max 100) | Results per query |