my-wiki 0.1.0

Shared, git-synced, LLM-maintained wiki — one knowledge base for all your AI agents

MyWiki

A shared, git-synced, LLM-maintained wiki — one knowledge base that any agent (Claude Code, Codex, ouro-cli, GoaLoop, …) on any machine reads from and writes to.

Inspired by Andrej Karpathy's LLM-wiki note: instead of re-retrieving raw documents on every query (RAG), an LLM incrementally maintains a structured markdown wiki whose knowledge compounds over time.

Idea in one picture

sources/   immutable snapshots (id = content hash)
   │  mywiki ingest  →  work order
   ▼
wiki/pages/*.md   one concept per page, every claim cited [^src-id]
   │  mywiki query  →  cited answers
   ▼
git push/pull   sync across machines, agents, users

• The CLI does the mechanical work — hashing, routing, indexing, linting, git.
• The calling agent does the reasoning — extract facts, write prose, merge conflicts — guided by PLAYBOOK.md.
• git is the coordination layer — push to GitHub/GitLab to share.

The split matters: the CLI can't call a model, so the intelligence lives in markdown (PLAYBOOK.md, exposed via mywiki help) and is executed by whatever LLM is running. That's what lets every tool share one brain.

Install

Zero-dependency Python 3 (stdlib only). Install from PyPI:

uv tool install my-wiki       # or: uv pip install my-wiki  /  pip install my-wiki

(The distribution is my-wiki; the command it installs is mywiki.)

Then create your first wiki and wire it into Claude:

mywiki init ~/my-wiki         # create + register a wiki (becomes default)
mywiki install                # deploy the bundled skill into ~/.claude/skills

Use

mywiki help                       # learn the commands
mywiki ingest notes.md            # freeze a source, get a work order
#   …agent edits wiki/pages/* per the work order…
mywiki commit-ingest src-1a2b -m "ingest: meeting notes" --push
mywiki query raft leader election # cited answers
mywiki lint                       # broken/stale/uncited check
mywiki sync                       # git pull --rebase before/after work

Multiple wikis

Each wiki is its own git repo, so you can run several independent ones (e.g. a work and a personal knowledge base). A per-machine registry (~/.config/mywiki/registry.json, not synced) gives them stable names:

mywiki init ~/work-wiki work          # create + register, first becomes default
mywiki init ~/personal-wiki personal
mywiki use research ~/some/existing    # register an existing wiki
mywiki list                            # show all, marking default + active
mywiki default personal                # change the default
mywiki -w work query raft              # target a specific wiki on any command
mywiki forget research                 # drop from registry (files untouched)

Which wiki a command hits, in order: -w <name> → $MYWIKI_HOME → the wiki you are cd'd into → the registry default.

Make agents aware of it

Each tool just needs a one-line pointer to the CLI (there is no per-tool logic — the usage lives in mywiki help):

• Claude Code: run mywiki install (deploys the bundled skills/mywiki/SKILL.md to ~/.claude/skills/).
• Codex / others: add to AGENTS.md: "A mywiki CLI maintains a shared knowledge base; run mywiki help to use it."

Layout

This repo is the tool's source. Actual wikis are created elsewhere with mywiki init and have their own sources/, wiki/pages/, wiki/log/, wiki/index.md, plus a copy of PLAYBOOK.md / .schema.md.

Path	What
mywiki/cli.py	the CLI (mechanical engine + self-docs)
PLAYBOOK.md	the workflow/prompts, served by mywiki help (canonical template)
.schema.md	what a page looks like (canonical template)
mywiki/resources/	symlinks to the templates + skill, bundled into the wheel
skills/mywiki/	the Claude skill, deployed by mywiki install
pyproject.toml	packaging (entry point mywiki = mywiki.cli:main)