| name | find-session |
|---|---|
| description | Find and resume past Claude Code sessions. Triggers: find session, search past sessions, find where I worked on, resume session, cass search, what session did I, find the conversation where, search my history. |
Search past AI coding sessions using cass and offer to resume them.
- cass (Coding Agent Session Search) — Rust CLI/TUI that indexes and searches session histories from Claude Code, OpenCode, Cursor, Aider, and 11+ other AI coding tools. Provides sub-60ms full-text search across all your conversations. Install:
cargo install coding_agent_session_searchor grab a binary from releases.
Translate the user's description into keyword queries. Tips:
- Use specific nouns/verbs from what they describe, not abstract descriptions
- Try 2-3 different keyword strategies if first doesn't hit
- Single-word queries often work better than multi-word
cass search "<keywords>" --limit 20 --jsonResults come as hits array. Filter out noise:
- Skip paths containing
observer-sessions(claude-mem internals) - Skip paths containing
/subagents/(sub-conversations) - Skip titles starting with
<observed_fromorYour task is to create a detailed summary - Deduplicate by session UUID (extract from source_path)
For each match, show:
- Date (convert epoch ms
created_atto human date) - Workspace (extract project from source_path)
- Title
- Snippet (if relevant)
- Message count
- Resume: Extract UUID from source_path (the filename without .jsonl extension), offer
claude --resume <UUID> - Export:
cass export <source_path>for markdown export - View context:
cass expand <source_path> --line <N>to see messages around a match
~/.claude/projects/<encoded-project>/<UUID>.jsonl
- UUID is the session ID for
claude --resume - Project is encoded with hyphens replacing path separators
- cass index may be stale — if results seem incomplete, suggest
cass index --full - Search returns
hitsnotresultsin JSON output created_atis epoch milliseconds, not seconds- Multiple queries are better than one complex query