← ClaudeAtlas

find-sessionlisted

Finds a past Claude Code session by what was said in it — words from a prompt the user typed, a compaction summary or the session's name — across every repo on this machine, and gives the claude --resume command that reopens it. Runs the script bundled with the skill over the transcripts on disk, ranks one prompt holding every term above terms scattered through a long session, and reports how far back the transcripts reach, since an older session is gone. Naming the current session is /rename; running and background sessions are claude agents.
wardawgmalvicious/claude-plugins · ★ 0 · AI & Automation · score 78
Install: claude install-skill wardawgmalvicious/claude-plugins
# Finding a past session The user remembers a session by what happened in it — "there was a session where I was exploring…" — and wants it back. Its name is a weak index: Claude Code titles a session once, from its first prompt, so one that wandered keeps the title of where it began (each of 233 titled sessions held exactly one title, 2026-10-06). The bundled script reads the words instead, in every transcript under `~/.claude/projects/`, from every repo on this machine. ## 1. Search ```bash uv run --no-project ${CLAUDE_SKILL_DIR}/scripts/find-session.py <term> <term> ... ``` - **Every term must appear in the session**, as a substring, ignoring case: in its name, a prompt the user typed, or a compaction summary. Take two or three of the user's own distinctive words, not a paraphrase; a common word matches most of the store. Words given after `find-session` are the terms. - **Keep `--no-project`.** Without it, `uv run` in a repo that has its own Python project syncs that project first. The script needs no dependencies. - **Drop a leading `/`.** Git Bash rewrites `/<name>` into `C:/Program Files/Git/<name>` before the script sees it, quoted or not, and the search answers `0 of … sessions matched`, exit 1, which reads as an honest miss (2026-10-06). The script records a typed command as `/<name> <args>`, so `<name>` finds it. PowerShell passes the slash intact. ## 2. Read the hits ```text 2026-09-29 23:18 my-repo contributing-md prompt: …ood poi