memex-search

Index local Claude/Codex history and output JSONL search results.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/voznik/dotfiles --skill memex-search-voznik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memex-search
Source: https://github.com/voznik/dotfiles/tree/main/.rulesync/skills/memex-search
Command: npx skills add https://github.com/voznik/dotfiles --skill memex-search-voznik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Memex Search indexes local Claude/Codex history and retrieves results in a structured, machine-friendly JSON format for efficient search, analysis, and downstream processing.

Core Features & Use Cases

  • Incremental and full reindexing with embeddings on by default
  • Lexical, semantic, and hybrid search modes
  • Output JSONL for downstream processing and RAG pipelines
  • Flexible filtering by project, session, role, and source

Quick Start

Index your Claude/Codex history with memex index, then execute memex search to retrieve JSON-formatted results.

Frequently Asked Questions about memex-search

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I index local Claude history for RAG workflows?

You can index local Claude history for RAG by running a full or incremental reindexing process. The pipeline generates JSONL output with embeddings enabled by default, making the historical data structured and ready for retrieval.

Can I filter search results by session and project in JSON format?

Yes, you can filter search results by session, project, role, and source. This allows you to narrow down the structured JSON output to specific contexts before feeding it into downstream processing.

What's the best way to perform semantic search on Codex logs?

The best way to perform semantic search on Codex logs is using a search tool that supports embeddings and multiple retrieval modes. Lexical, semantic, and hybrid search are all supported natively.

Does incremental indexing support embeddings by default?

Yes, incremental indexing supports embeddings by default. This ensures your searchable index stays updated with new history entries without requiring a full rebuild every time.

How do I get structured JSONL output from Claude history?

You get structured JSONL output by indexing your Claude history and executing a search query. The pipeline outputs JSONL formatted results suitable for downstream RAG pipelines and analysis.

When do I need hybrid search for local AI history?

You need hybrid search when simple keyword matching is insufficient and semantic context matters. It combines lexical and semantic search modes to retrieve the most relevant results from your indexed history.