find-conversation

Search stored JSONL conversation history to locate past Claude Code sessions.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/kzarzycki/agent-skills --skill find-conversation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: find-conversation
Source: https://github.com/kzarzycki/agent-skills/tree/main/workflow/skills/find-conversation
Command: npx skills add https://github.com/kzarzycki/agent-skills --skill find-conversation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The find-conversation Skill solves the problem of not being able to locate an earlier Claude Code session when you need to recall what you did or continue work from a past outcome.

Core Features & Use Cases

  • Search across saved JSONL conversation history: Finds relevant sessions across ~/.claude/projects/{encoded-cwd}/{sessionId}.jsonl using topic, content keywords, dates, or working directory context.
  • Recover context even when conversations were compacted: Uses plan files (~/.claude/plans/*.md) and scans candidate sessions to mitigate missing early content.
  • Present ranked candidate sessions for user selection: Extracts session ID, working directory, first user message, date range, and justification to help you pick the correct session before resuming.

Quick Start

Tell Claude to use find-conversation to locate the session where you discussed "X" so you can resume it.

Frequently Asked Questions about find-conversation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search past Claude Code conversations by topic or content?

To search past Claude Code conversations, this skill scans stored JSONL history files across project working directories using topic, content keywords, or dates to locate the correct session.

Can I resume a Claude Code session if the conversation history was compacted?

You can resume a compacted Claude Code session because this skill uses a compaction-aware fallback that scans plan files and candidate sessions to mitigate missing early content.

How do I find a specific session ID from my Claude Code JSONL history?

Finding a specific session ID involves parsing JSONL history files to extract match metadata, presenting ranked candidates with working directory and date range for explicit user selection.

What is the best way to locate an earlier Claude Code session across multiple working directories?

The best way to locate an earlier Claude Code session is performing a full-history search without mtime filtering across encoded project paths to recall prior decisions from any timeframe.

Does Claude Code session search work without filtering by file modification time?

Claude Code session search works without mtime filtering by requiring a full-history search across all stored JSONL files to ensure older or inactive sessions are successfully recovered.