Per-project semantic search over your Claude Code session history — not a shared or centralized memory store. Indexes JSONL transcripts into a local SQLite file, retrieves via bge-m3 embeddings (Ollama) with automatic FTS5 BM25 fallback, and auto-injects relevant past context at session start. Companion to session-end: session-end gives "where I left off," session-indexer gives "what we decided" — same Stop/SessionStart hooks. Apache 2.0, 75 passing tests, go install and nothing to deploy.
I kept losing track of why we made past decisions across long-running projects — session-end gives you "where I left off," but not "what did we decide about X three weeks ago." So I built session-indexer to close that gap: a per-project SQLite index of your Claude Code session history, searchable by semantic similarity via bge-m3, with an automatic FTS5 keyword fallback so it never has a hard dependency on Ollama. It hooks into the same Stop/SessionStart events as session-end, so both just run together — no extra setup, no shared backend, nothing to deploy.
this is a real gap - I've had the "what did we decide about X" problem plenty of times across long-running Claude Code sessions. Curious how it behaves for a monorepo setup where frontend and backend live in separate directories but are logically one project - does the per-project indexing stay strictly siloed to each directory, or is there a way to point it at a shared index across a few related repos?
About session-indexer on Product Hunt
“Semantic search over your own Claude Code session history”
session-indexer launched on Product Hunt on August 25th, 2026 and earned 89 upvotes and 3 comments, placing #18 on the daily leaderboard. Per-project semantic search over your Claude Code session history — not a shared or centralized memory store. Indexes JSONL transcripts into a local SQLite file, retrieves via bge-m3 embeddings (Ollama) with automatic FTS5 BM25 fallback, and auto-injects relevant past context at session start. Companion to session-end: session-end gives "where I left off," session-indexer gives "what we decided" — same Stop/SessionStart hooks. Apache 2.0, 75 passing tests, go install and nothing to deploy.
session-indexer was featured in Open Source (68.8k followers), Developer Tools (518.5k followers), Artificial Intelligence (477.4k followers) and GitHub (41.4k followers) on Product Hunt. Together, these topics include over 242.6k products, making this a competitive space to launch in.
Who hunted session-indexer?
session-indexer was hunted by Valentyn Solomko. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how session-indexer stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Valentyn Solomko