getscribe.dev valid

scribe

scribe is the compiled, LLM-written knowledge base — the [LLM Wiki pattern](https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f) Andrej Karpathy described, as a single-binary Go CLI: plain markdown in git, no vector DB, no RAG. It's memory your AI agents read before they decide, not a second brain you maintain and never reopen. It turns your git repos, coding-agent sessions, and self-sent URLs into a curated personal knowledge base with BM25 and local vector search. It mines every

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T09:53:25.297Z. Cached copy · Source on getscribe.dev

# scribe

> scribe is the compiled, LLM-written knowledge base — the [LLM Wiki pattern](https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f) Andrej Karpathy described, as a single-binary Go CLI: plain markdown in git, no vector DB, no RAG. It's memory your AI agents read before they decide, not a second brain you maintain and never reopen. It turns your git repos, coding-agent sessions, and self-sent URLs into a curated personal knowledge base with BM25 and local vector search. It mines every provider indexed by ccrider; project discovery covers Claude Code and Codex, while the query-KB + drop-file handshake also reaches Amp. Cross-project, cron-driven, and runs 100% on local Ollama with zero API spend. In team mode, a small team shares one git-backed KB with a trust layer (shared config is untrusted by default), a deterministic secret-scan commit gate, and per-git-remote approval — keeping secrets, private client repos, and hostile config changes out of shared history.

scribe is an LLM-written knowledge base pipeline. It mines:

- git repository commits for new decisions and patterns
- Coding-agent sessions via ccrider's FTS5 index — Claude Code, Codex CLI, Copilot CLI, OpenCode, Pi, Antigravity, Amp when imported by ccrider, and future providers
- Codex CLI rollouts — project discovery, plus opt-in direct session mining through the same session-extraction path
- URLs you text yourself via iMessage (macOS only)
- drop files committed inside other projects under `.claude/<your-kb-name>/`

It writes a wiki of typed markdown articles (decisions, patterns, learnings, tools, research, projects) with YAML frontmatter and `[[wikilink]]` connections, indexed by qmd for BM25 keyword and semantic vector search. The whole pipeline runs on macOS LaunchAgents or Linux cron — set up once with `scribe init` + `scribe cron install`, then your KB grows on its own. `scribe init` writes maintained handshake blocks into `~/.claude/CLAUDE.md`, `~/.codex/AGENTS.md`, and `~/.config/amp/AGENTS.md`, so Claude Code, Codex, and Amp query the KB before decisions and write reusable lessons back as drop files under the same shared `.claude/<your-kb-name>/` path.

The product is the curated wiki, not raw chunks. Every dense source fans out into multiple entity-first wiki pages via a two-pass absorb. LLM-generated retrieval-context paragraphs get spliced into every article so embedding models catch implicit entities. **Every LLM op in scribe — per-project extraction, absorb, dream, assess, deep, session-mine, relations migrate — routes through a local Ollama server when `llm.provider: ollama` is set; there is no remaining `claude -p` callsite in a normal `scribe sync`.** The maintainer's KB is 8,128 articles as of Aug 2026, none typed by hand. Because articles are markdown in git with their source session or commit recorded in frontmatter, wrongness is auditable rather than opaque: `scribe contradictions list` surfaces articles that disagree, `scribe stale list`
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=getscribe.dev · GET /v1/domain/getscribe.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for getscribe.dev:
1. POST https://agentwebmap.com/v1/sites/getscribe.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://getscribe.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/getscribe.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/getscribe.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.