Session Finder

glebis/session-finder

Index and search Claude Code sessions using semantic embeddings (Gemini). Find past sessions by topic, relaunch the best match. Triggers on "find session", "which session did I", "relaunch the session where", "session about X".

5k tokens

context cost

the whole folder, loaded on every use

files

ships runnable scripts

copies elsewhere

how many repositories repackaged it

337

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/glebis/claude-skills --skill session-finder

What comes with it

16 815 bytes besides the instruction

.claude-plugin/plugin.json

scripts/session_finder.py

The instruction itself

8 sections, as written by the author

Session Finder

Semantic search across Claude Code sessions using Gemini embeddings.

Commands

Index sessions

python3 ~/.claude/skills/session-finder/scripts/session_finder.py index [--max-age-days 90]

Search

python3 ~/.claude/skills/session-finder/scripts/session_finder.py search "query" [--top 5]

Open best match directly

python3 ~/.claude/skills/session-finder/scripts/session_finder.py open "query"

Stats

python3 ~/.claude/skills/session-finder/scripts/session_finder.py stats

How it works

Document extraction — deterministic, no LLM. Each session JSONL is parsed into a structured document:
away_summary events (pre-existing Claude recaps) if available
First user message (task description)
Follow-up user messages (condensed)
First assistant response
Tools used
Project name
Embedding — documents are embedded with gemini-embedding-exp-03-07 via llm CLI
Storage — SQLite at ~/.claude/session-finder.db
Search — query is embedded, cosine similarity ranks all sessions, top match is the default to open

Workflow

When user asks to find a session:

Run search with their query
Present results with confidence scores
Offer to resume the top match via claude --resume <id>

How to use it

Copy the folder

Take glebis/session-finder from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.