brain-wiki
One long-term memory for all your AI agents, kept as plain Markdown that you own.
Your agents (Claude Code, Codex, Antigravity, Cursor, OpenClaw, or any MCP client) share one brain: a folder of Markdown notes they search before answering and keep up to date as they work. It runs on your machine, needs no server or API keys, and opens in Obsidian.
- Plain files. Read, edit, diff, and sync the brain like any folder, or adopt an Obsidian vault as it is.
- Knows what changed. Search returns a note together with the notes that replace or contradict it.
- Safe to let agents write. Changes are checked, logged, and undoable, and committed when the brain is a git repository.
- No network calls. Your own agent does the thinking; brain-wiki stores and checks.
Quick start
Needs Python 3.11+ and uv.
1. Install.
uv tool install brain-wiki
2. Set it up.
-
Recommended: paste this into your agent (Claude Code, Codex, Antigravity, Cursor, OpenClaw, ...):
Set up brain-wiki by running
brain setup --guideand following it. -
Or, in a terminal: run
brain setup, which asks the same questions step by step.
Either way, setup explains each choice (where the brain lives, which agents to connect, what each may do) and shows every change before making it.
3. Use it in your agent.
Remember that I prefer pnpm over npm, and that our team ships on Thursdays.
What did we decide about the database migration last week?
Maya moved to the platform team. Update her note.
Consolidate my brain.
4. See your brain. brain viz opens a local 3D map of your notes, and
brain obsidian opens the brain's folder as a vault in Obsidian. With several
brains, both ask which one, or name it: brain viz work.
How it works
agents ──log──► inbox ──consolidate──► notes (topics/*.md) ◄── you, in Obsidian
▲ (checked ops) │
└────────────── search · read ───────────────┘
Agents log what they learn to an inbox. When you ask, your agent folds the
inbox into topic notes through small operations that brain-wiki checks before
writing, and brain undo reverses any change.
Status
Alpha: expect breaking changes before 1.0. Known limits:
- No access scopes inside a brain: every connected agent reads all of it. Keep work and personal notes in separate brains.
- Maintenance runs when you ask; there is no scheduler.
- Chat apps that need a remote MCP server (ChatGPT, claude.ai, the Gemini app) are not supported yet.
Learn more
Getting started · Agents · Maintenance · Import a vault · Privacy · Reference · Design · Changelog
Metadata
Release files for brain-wiki 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| brain_wiki-0.1.1.tar.gz | 722.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| brain_wiki-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.3 MB
Release files / brain_wiki-0.1.1.tar.gz
| Download URL | brain_wiki-0.1.1.tar.gz |
|---|---|
| Size | 722.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6bc2c012943e28cd75432b5040f6186b0ee5514a8926f1b84c67837807099ae3
|
|
BLAKE2b-256 checksum How to use checksums |
d29340d6bfb10be6b64c5bdafb11112dbc45c721d034f5c1db948ea2bb71e6b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 15, 2026.
Transparency logRelease files / brain_wiki-0.1.1-py3-none-any.whl
| Download URL | brain_wiki-0.1.1-py3-none-any.whl |
|---|---|
| Size | 564.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eeec5939930a401dbd780751b72e8f6423ef36f1dbb3224d2437510fefa6edb9
|
|
BLAKE2b-256 checksum How to use checksums |
803f29c26fb3432950989960729dcb7d18109ac5bfd09327929e85784b43d99f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 15, 2026.
Transparency log