
Scribe
CLI tool that builds a searchable knowledge base from your coding sessions and repos
Gallery
About Scribe
Scribe is a single binary CLI tool that watches your development work and turns it into a personal knowledge base. It pulls from git repositories, Claude Code sessions, Codex CLI transcripts, and self sent URLs, then organizes what it finds into curated markdown articles you can query from the terminal or from inside an AI agent. The idea is that you stop explaining the same context over and over because the system has already absorbed it and can surface it when relevant.
The problem it tackles is familiar to anyone who uses AI coding assistants heavily. You solve a tricky architecture problem in one project, write something clever in a Claude session, but three weeks later that knowledge is buried in a transcript you will never find. Scribe extracts those decisions, patterns, and learnings automatically, stores them in a local wiki indexed for semantic retrieval, and keeps everything current as you keep working.
Processing happens in two stages. First a keyword density filter runs over raw sources to avoid sending low signal content to the language model. Then a two pass absorption routine expands dense sessions into multiple wiki articles, each tied to a specific entity or decision. The result is a knowledge graph with ten relationship types (supersedes, contradicts, depends on, and so on) that lets you trace how your understanding has evolved. Weekly consolidation cycles detect contradictory claims and resolve them so the base stays coherent.
On the retrieval side, Scribe uses BM25 full text search through a companion tool called qmd. You can run queries from the terminal or inject context blocks into Claude Code and Codex sessions via a handshake protocol, which means the agent consults your knowledge base before suggesting a library you already rejected or proposing an architecture you already tried and documented.
The whole thing runs locally by default. You can point it at Ollama with models like qwen3 or gemma and pay nothing for inference. If you prefer hosted providers, it supports Anthropic Claude, OpenAI compatible endpoints like Together or Groq, and Hugging Face. Scheduling is handled through LaunchAgents on macOS or crontab on Linux, running hourly commits, regular extraction sweeps, and weekly memory consolidation without manual intervention.
The tool is open source under MIT and distributed as a single downloadable binary. It fits developers who code with AI tools frequently and want to stop losing context between sessions, teams that want a shared but version controlled knowledge base, and anyone who values owning their data in a plain markdown format they can read and edit directly.
Key Features
- Automatic knowledge extraction from git, Claude Code, and Codex
- Local first with zero API cost via Ollama
- BM25 full text search from terminal
- Agent handshake for context injection
- Typed knowledge graph with relationship tracking
- Scheduled automation via cron or LaunchAgents
Pros & Cons
What we like
- Runs entirely local with no API spend if you use Ollama
- Extracts context from AI sessions you would otherwise lose
- Plain markdown output you own and can edit directly
- Injects knowledge into agents so they stop suggesting things you already rejected
Room for improvement
- Requires local LLM setup or API keys for processing
- Younger project with a smaller community
- Best value comes from heavy AI coding assistant usage
- Initial extraction can be slow on large git histories
Frequently Asked Questions
What is Scribe?
Does Scribe require API keys?
Is Scribe free?
Who is Scribe for?
Best For
Featured in
Alternatives to Scribe
View all1Lookup
Real-time data verification API for phone, email, IP, and domain validation to fight fraud
Kevin Gabeci
Solo developer building web apps, cozy browser games, and AI creator toolkits.

Codedex
A gamified, story-driven platform that teaches Python, web dev, and more like an RPG quest
Hack2hire
Practice real SDE interview questions from top tech companies with expert worked solutions
Reviews (7)
Quietly excellent
Picked Scribe for the price, stayed for the quality. What stands out is how it handles extracts context from ai sessions you would otherwise lose. It handles the boring parts so I can focus on the work that matters. Found it works best for tracking architectural decisions across multiple repositories. Recommending it to people in a similar spot.
Does the job, a few gripes
Scribe solves a real problem for me without making a fuss about it. Where it really wins is extracts context from ai sessions you would otherwise lose. The thing I keep coming back to is how reliable it is. My only gripe is younger project with a smaller community. Glad I made the switch.
Two months in, no regrets
Came to Scribe after getting frustrated with what I had before. What stands out is how it handles scheduled automation via cron or launchagents. The defaults are sensible, so I was not fighting settings on day one. Recommending it to people in a similar spot.
Pulled its weight from week one
Scribe has quietly become part of my daily flow. Their take on automatic knowledge extraction from git, claude code, and codex is genuinely good. The output quality holds up better than I expected. Mostly using it for consolidating learnings from claude code and codex transcripts. Easy yes for anyone weighing the same trade offs.
Decent with some rough edges
Three months of Scribe later, here is what holds up. It slotted into my routine without much fuss. It fits well for tracking architectural decisions across multiple repositories. One thing that bugs me is initial extraction can be slow on large git histories. Would sign up again without thinking twice.
Worth a look
Hadn't planned on switching, but Scribe was hard to ignore. The typed knowledge graph with relationship tracking is more useful than I expected. The thing I keep coming back to is how reliable it is. Found it works best for consolidating learnings from claude code and codex transcripts. Worth it for what I get out of it.
Two months in, no regrets
Three months of Scribe later, here is what holds up. Where it really wins is local first with zero api cost via ollama. It has shaved real time off my week. Mostly using it for building a personal wiki from your coding sessions automatically. Worth it for what I get out of it.
Related Tools
Kevin Gabeci
Solo developer building web apps, cozy browser games, and AI creator toolkits.

Coolify
Self-hostable, open source alternative to Heroku and Netlify

Warp
The modern terminal reimagined with AI and collaboration

Bolt.new
Prompt-to-deployed full-stack app inside the browser