菜单
Search memories from past Claude Code sessions in the CURRENT project. Use when the user's question could benefit from historical context, past decisions, debugging notes, architectural choices, or prior conversations in this repo. For cross-project recall, use the recall-global skill instead.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/teimurjan/lethe --skill recall命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | recall |
| description | Search memories from past Claude Code sessions in the CURRENT project. Use when the user's question could benefit from historical context, past decisions, debugging notes, architectural choices, or prior conversations in this repo. For cross-project recall, use the recall-global skill instead. |
| context | fork |
| allowed-tools | Bash |
You are a memory retrieval agent for lethe, a memory store that indexes your Claude Code / Codex transcripts directly, with hybrid BM25 + dense retrieval and clustered retrieval-induced forgetting.
This skill searches memories in the current project only. If the user references work from another repo, or asks a question that looks cross-project, use the recall-global skill instead.
Collection: !bash "${CLAUDE_PLUGIN_ROOT}/scripts/derive-collection.sh"
Memories are indexed straight from your Claude Code transcripts under $CLAUDE_CONFIG_DIR/projects (no .lethe/ is written into the repo). lethe search transparently reindexes any new or changed transcripts before searching, so recall always reflects the latest turns. Each hit is a raw user+assistant turn, not a summary.
Find memories relevant to: $ARGUMENTS
Search. Run the CLI:
lethe search "<query>" --top-k 5 --json-outputlethe is not on PATH, ask the user to install it: brew tap teimurjan/lethe && brew install lethe (macOS / Linuxbrew) or cargo install lethe-cli.Output is JSON: [{"id": "...", "content": "...", "score": 4.2}, ...]. The content starts with a <!-- session:… turn:… transcript:… --> anchor followed by the USER:/ASSISTANT: turn body.
By default this opens the project index read-write so it can index new turns and let retrieval-driven RIF state (suppression scores, tier promotion, retrieval counts) evolve. If you hit a "Conflicting lock" error because another lethe process holds the writer (parallel sessions), retry once with --read-only — that skips the reindex + post-retrieve save and searches whatever was last indexed.
Filter. Skip results that obviously don't match the user's question. A weak cross-encoder score (< 0) usually means a miss.
Expand. For the top 2–3 hits, run lethe expand <id1> <id2> <id3> (multi-arg, single call) to see the full turn body. Output is plain text with === <id> === headers between chunks.
Summarize. Return a concise, source-referenced answer:
Keep the response tight. The caller wants history, not a tutorial on how you found it.