search-history

Search Claude conversation history by running the Python CLI tool with a search term against your JSONL session files. The tool scans all conversations, filters by session if needed, and returns matching messages with surrounding context to help you locate past discussions, decisions, and code solutions quickly.

Yes. The search tool supports session filtering via --session flag, context extraction with --context to show surrounding messages, and options like --list-sessions to view available conversations. You can also limit results with --max and get full message content using --full for complete context.

Conversation history must be stored as JSONL files in your ~/.claude/services directory. JSONL (JSON Lines) format stores one complete message record per line, enabling efficient line-by-line parsing and retrieval of specific conversations and decisions across multiple sessions.

Use the search history tool to query your JSONL conversation files with a relevant term or topic. The tool retrieves matching messages with optional context windows and session filtering, letting you quickly recall prior code solutions, architectural decisions, or discussion outcomes for debugging or knowledge reuse.

Yes. Use the --verbose flag for extended context or --full to retrieve complete message content from JSONL files. These options support auditing decisions, reviewing code discussions in detail, and preserving full context for compliance or knowledge documentation purposes.

Store JSONL session files in ~/.claude/services with descriptive names reflecting their content or date. The tool can list and filter sessions, so organizing files by project, topic, or timeframe enables faster targeted searches and helps you retrieve relevant context across many stored conversations.