pickfit

BrowseDeveloper CLIs

session-indexer

Per-project semantic search over Claude Code session history stored in SQLite.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Go 1.26.9+
  • System packages: jq
  1. Download prebuilt linux_amd64 binary to ~/.local/bin

    mkdir -p ~/.local/bin && curl -fsSL -o ~/.local/bin/session-indexer https://github.com/valpere/session-indexer/releases/download/v0.3.0/session-indexer_v0.3.0_linux_amd64 && chmod +x ~/.local/bin/session-indexer

Check that it works

session-indexer --help

The output should contain “Available Commands:”.

First thing to try

mkdir -p .claude && cat > sample.jsonl <<'EOF'
{"type":"user","sessionId":"test-session-1","timestamp":"2026-08-25T10:00:00Z","message":{"role":"user","content":"We discussed the config validation approach using a schema validator with strict mode enabled for the project"}}
{"type":"assistant","sessionId":"test-session-1","timestamp":"2026-08-25T10:00:05Z","message":{"role":"assistant","content":[{"type":"text","text":"For config validation approach we decided to use a ring buffer style validator with strict schema checks and detailed error messages."}]}}
{"type":"user","sessionId":"test-session-1","timestamp":"2026-08-25T10:01:00Z","message":{"role":"user","content":"What did we decide about the event queue implementation for handling background tasks?"}}
EOF
cat sample.jsonl
session-indexer mine sample.jsonl --db .claude/sessions.db

Run session-indexer mine <file> --db .claude/sessions.db to index a session transcript into a project database.

What it does

  • Index JSONL transcripts into a SQLite database
    How to use it
    1. Run session-indexer mine <file> --db .claude/sessions.db with your JSONL transcript.
    2. Check the output line for how many chunks were inserted.
    Tested
  • Search past Claude Code sessions by meaning
    Not shown working
  • Add relevant past context automatically
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 1 of 3 features work
  4. Works offline

macOS and Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • find what was decided about a topic across past sessions
  • inject relevant past context at session start
  • index JSONL transcripts into per-project SQLite store
  • query distilled facts about implementation status
  • browse what is in the index by day without a query

An alternative to mempalace, agentmemory and MemMachine.

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026

Differences the test machine hit

  • README: go install ./cmd/session-indexer (needs Go 1.26.9+)
    In the test: download prebuilt session-indexer_v0.3.0_linux_amd64 binary from GitHub Releases to ~/.local/bin and chmod +x; no Go toolchain needed
  • README: retrieves via bge-m3 embeddings (Ollama) with FTS5 BM25 fallback
    In the test: search prints '(embedding unavailable — FTS5 keyword results only)' and still returns keyword hits with no Ollama running

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.