Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
glebis avatar

Session Finder

  • 136 installs
  • 339 repo stars
  • Updated August 4, 2026
  • glebis/claude-skills

Locate a prior Claude Code session by date, project, or metadata when you need to resume context or audit what the agent did last week.

About

The session-finder skill helps Claude Code discover specific historical coding sessions using metadata and filesystem cues, enabling operators to reopen the right conversation, continue interrupted work, and audit past agent actions without manually browsing log directories.

  • Filters sessions by time, path, or project signals
  • Speeds recovery of lost agent context
  • Supports audits of prior automated changes
  • Reduces duplicate work across long-running products

Session Finder by the numbers

  • 136 all-time installs (skills.sh)
  • Ranked #1,227 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/glebis/claude-skills --skill session-finder

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs136
repo stars339
Last updatedAugust 4, 2026
Repositoryglebis/claude-skills

What it does

Locate a prior Claude Code session by date, project, or metadata when you need to resume context or audit what the agent did last week.

Files

SKILL.mdMarkdownGitHub ↗

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

1. 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

2. Embedding — documents are embedded with gemini-embedding-exp-03-07 via llm CLI 3. Storage — SQLite at ~/.claude/session-finder.db 4. Search — query is embedded, cosine similarity ranks all sessions, top match is the default to open

Workflow

When user asks to find a session: 1. Run search with their query 2. Present results with confidence scores 3. Offer to resume the top match via claude --resume <id>

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.