On Launch Llama
session-indexer
For developers: session-indexer searches your Claude Code history semantically so you recall past decisions and context without manual notes.
Built by Valentyn Solomko
Free
Visit website → Upvotes · 89
session-indexer is a Product Hunt listing on Launch Llama with 89 total upvotes, founded by Valentyn Solomko who joined in Aug 2026, compared against 6 alternatives.
Product Hunt listing
Listing status
89upvotes
Community score
Valentyn Solomko (Joined Aug 2026)
Founder
Compared against 6 alternatives
Market comparison
Key Features
- Index JSONL transcripts into SQLite database
- Retrieve sessions via semantic embeddings with fallback search
- Automatically inject relevant past context at session start
- Search session history by semantic similarity
About
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.
Use Cases
- Find past decisions across multiple sessions by semantic similarity instead of grep
- Recall what was discussed across all session history for context
Pricing
session-indexer is free to use. See the website for details.
Verdict
In the competitive automation tools space, session-indexer stands out as a solid option. With 89 upvotes from the Launch Llama community, it's clearly resonating with founders. Per-project semantic search over your Claude Code session history — not a shared or centralized memory store. If for developers: session-indexer searches your claude code history semantically so you recall past decisions and context without manual notes is a priority for your team, it's worth giving session-indexer a closer look.
FAQ
What is session-indexer?
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.
Who should use session-indexer?
session-indexer is a strong fit if you are one of: • indie hackers and solo founders • early-stage startup teams If that does not sound like you, skim the features and site before committing time.
What problem does session-indexer solve?
session-indexer is built around this outcome: For developers: session-indexer searches your Claude Code history semantically so you recall past decisions and context without manual notes. Use the site demo or docs to confirm it matches the bottleneck you are trying to remove.
How to find past decisions across multiple sessions by semantic similarity instead of grep?
session-indexer is set up for this: Find past decisions across multiple sessions by semantic similarity instead of grep. Open the official site from this page and run that workflow on a real task to confirm fit.
What are the main features of session-indexer?
session-indexer includes: • Index JSONL transcripts into SQLite database • Retrieve sessions via semantic embeddings with fallback search • Automatically inject relevant past context at session start • Search session history by semantic similarity
Is session-indexer free?
session-indexer is free to use. See the website for details. Check the official site before you buy so you see current plans, trials, and limits. Confirm on the product site that free usage covers your volume and that there are no surprise limits.
How much does session-indexer cost?
session-indexer is free to use. See the website for details. Check the official site before you buy so you see current plans, trials, and limits.
Is session-indexer worth trying?
It promises: For developers: session-indexer searches your Claude Code history semantically so you recall past decisions and context without manual notes. A concrete use case founders care about: Find past decisions across multiple sessions by semantic similarity instead of grep.. It has 89 community upvotes on Launch Llama, which is a signal of interest — not a guarantee it fits you. Worth trying if that problem is painful for you this week; skip it if you only need a one-off workaround you already have.
How do I try session-indexer?
Open the official session-indexer website from this page, run the smallest real task you care about (not a toy demo), and decide in one session whether it removes friction. Check pricing and data/privacy terms before you put production work into it.
Alternatives
- Claudebin
For developers: Claudebin exports Claude Code sessions as shareable URLs with full context—message threads, file changes, bash commands, and tool calls—so you can link in PRs or resume locally.
- Claude Code Desktop App Redesigned
For developers: Claude Code desktop runs parallel coding agents across repos, reviews diffs, and ships code—all in one workspace.
- PMB
For AI coding users: PMB gives Claude, Cursor, and Zed persistent project memory so agents understand your codebase without re-explanation.
- ContextPool
For AI coding teams: ContextPool gives your agent persistent memory by extracting bugs, fixes, and design decisions from past sessions and loading relevant context automatically.
- Agentmemory
For developers: Agentmemory gives Claude Code and coding agents searchable persistent memory, reducing token usage by 92% while keeping 100% of observations accessible.
- Context Gateway
For developers: Context Gateway reduces latency and token costs for Claude Code by compressing tool output while preserving context, cutting spend without quality loss.
Ask AI
ChatGPT Claude Perplexity Grok
For agents
llms.txt · llms-full.txt · ai.txt · Live fact sheet · Full catalog (.md) · Endpoint index · API spec · REST access · Agent server · Server manifest · Server discovery