Session Knowledge — Development skill for Claude Code
Turn your Claude Code session history into a searchable local knowledge base — 13 MCP tools, pure stdlib, nothing leaves your machine.
How to install Session Knowledge
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open nameforjt-afk/session-knowledge and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Session Knowledge does
Turn your Claude Code session history into a searchable local knowledge base — 13 MCP tools, pure stdlib, nothing leaves your machine.
Alternatives in Development
- Rb Refresh — Rebuild the repobrain project knowledge base after significant changes 1.3k ★
- Ag Refresh — Rebuild the antigravity project knowledge base after significant changes 1.2k ★
- Kb — Search the project knowledge base via GitMark (FTS5 bm25 + trigram/fuzzy) 75 ★
README
session-knowledge
[](https://github.com/nameforjt-afk/session-knowledge/actions/workflows/tests.yml)  [](LICENSE)
**Claude Code's memory is scoped per project directory. Your history isn't.**
Every session you've ever run is already on disk in `~/.claude/projects/**/*.jsonl` — every decision, every command that worked, every credential you pasted. But open a session in a different directory and none of it is reachable. You re-ask questions you already answered, and re-implement integrations you already wrote.
This indexes all of it and hands Claude 13 MCP tools to search it. You just ask normally.
*What was the retry logic in that deploy script?* *Which DATABASE_URL did I actually use for staging?* *Before I write the Stripe integration — has anyone here already done payment auth?*
Pure Python standard library. No third-party dependencies, no embeddings, no API calls, nothing leaves your machine.
git clone https://github.com/nameforjt-afk/session-knowledge.git
cd session-knowledge
bash install.sh
Restart Claude Code. Done.
⚠️ Read this before installing
The index lives in `~/.claude/session-index/` and **it contains plaintext credentials scraped from your sessions.** That is the precondition for "which key did I use here" to work at all.
**Never commit that directory, never sync it to cloud storage, never send it to anyone.** This repo's `.gitignore` covers the default location, but if you relocate it that's on you.
The full-text index itself is redacted: common credential shapes (API keys, Bearer tokens, JWTs, GitHub PATs, passwords inside connection strings) are replaced with `⟦SECRET:fingerprint⟧` before they are written. Plaintext lives only in `vault.db` at mode 0600, and only an explicit `creds
Related Skills
Bough
Visualize your Claude Code session history as a diagram of the work you actually did: days, tasks, prompts and
Earheart
Talk to your coding agents — press a hotkey, speak your prompt, and it lands in Claude Code, Codex, or Cursor.
Agent Wrapped
A local-first wrapped card for how you actually work with Claude Code. Nothing leaves your machine.
V Memory Refresh
(Re)index docs/superpowers prose into the local V-memory cache so recall is current. Incremental by file hash;
All Agent Shared Memory
Zero-dependency cross-agent memory + session bridge for Claude Code, Codex, opencode and ZCode: one auditable
Agent Skills Manager
Every skill, plugin and MCP server Claude Code, OpenCode and Codex load, in one searchable list on your Omarch
Related Agents
Maker
Reviews OpenCode sessions (shared links or local history), finds repeatable workflows, and proposes automation
Kb Reader
Read and summarize relevant Claude Code engineering pattern files from the local knowledge base. Keeps raw fil
Conflict Resolver
Resolves design-artifact merge conflicts when two developers worked a cycle on parallel branches. Reads the co