session-search

To search past Claude Code sessions, run a query-driven discovery using the aichat search tool to retrieve up to 10 matching sessions. It parses results to extract session_id, project, creation date, snippet, and file_path for quick reference and audit.

Finding old aichat sessions by topic is handled by applying the aichat search tool with a text query. The tool returns matching sessions with structured fields including project name and snippets, enabling engineers to quickly locate earlier decisions or code patterns.

Yes, you can read local session files for deeper analysis. After retrieving a session_id, the tool reads the corresponding JSONL file located at ~/.claude/projects/*/[session-id].jsonl to extract and return a more detailed, concise summary with references.

Yes, session-search works with Codex-CLI session histories. It enables engineers to quickly locate and interpret earlier Claude Code or Codex-CLI sessions for reference, audit, or pattern discovery by searching and reading the local project files.

To extract session_id and snippet from aichat search results, run aichat search --json -n 10 "[query]" and pipe the output through jq. This parses the JSON output to isolate fields like session_id, project, created, snippet, and file_path for quick review.

A limitation of searching past code agent sessions is that the initial search retrieves a maximum of 10 matching sessions. Deeper review requires reading local JSONL files from the ~/.claude/projects directory, which may restrict analysis to locally available session histories only.