Skip to content

The Curator

Your brain, then your team's brain, then your agents' brain. Drop in documents and it compounds them into an interlinked markdown wiki you own — readable in Obsidian, synced…

Install

$git clone https://github.com/talirezun/the-curator

Install command taken from the project's README or registry entry. Always review code before running it.

The Curator

Build a second brain from what you read, share it with a team, and give it to your agents.

Official website: mycurator.xyz — ask its assistant anything about The Curator.

What it is, in plain words

One knowledge folder on your own computer, three things you can do with it — always in this order, and each one optional past the first:

What it is Where
① Second brain Your reading, turned into a wiki that compounds with every source Domains, Chat
② Shared Brain (optional) The same wiki, written together with a team a domain's Shared Brain section
③ Agent memory (optional) What your agents read at the start of a session, and save as they work Context

A local app that turns what you read into a compounding wiki, shares it with a cohort, and holds your projects' context — Documents, Memory and Knowledge — so any agent, in any harness, resumes where the last one stopped. Plain markdown, in your own repo.

The Curator is the context engine. It builds and keeps the context your work runs on — what you have read, where the work stands, and the documents a project is built against — as plain markdown files on your own computer, and carries all three across sessions, machines, AI tools and models.

The building half is what you touch first. You drop in the things you read — PDFs, Markdown and text files: articles, notes, transcripts — and The Curator turns them into a connected personal wiki: a page for every person, tool and idea worth one, all linked to each other. Every new source updates the pages that already exist instead of adding another copy, so the wiki gets better the more you feed it, and you can ask it questions in ordinary language and get answers that point at the pages they came from. None of it needs an account, a database, or anything of yours on anyone else's server.

The three kinds of context it carries

Kind What it holds How it changes Example
Compounded knowledge — the wiki Entities, concepts and summaries, cross-linked into a graph Accumulates — a new source updates existing pages instead of duplicating them A page per person, tool and idea across everything you have read
Volatile state — the standing brief, the handoff, the journal (on screen since v3.65.1: Memory) Where a piece of work stands, per project Supersedes — each save replaces the last, because a resolved blocker must not come back Where you stopped, what you decided, what to do next
Canonical documents — foundations, new in v3.59.0 (on screen since v3.65.1: Documents) Architecture, decisions, conventions, roadmap — verbatim Replaced whole — always added through two doors, Add from this computer and Add from GitHub, both always enabled; since v3.69.0 one project can mix documents written here, copied in, and mirrored from up to 8 folders and GitHub repositories at once, each kept fresh by its own Refresh The document an agent should not start work without

Similar plugs

The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.

Java 面试 & 后端通用面试指南,覆盖计算机基础、数据库、分布式、高并发、系统设计与 AI 应用开发

Build Agentic workflows, RAG pipelines, with rich AI model and tool support on one collaborative workspace. Deploy on cloud, VPC, or self-hosted, so teams move from prototype…

A cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Grok Build & Hermes Agent. Only official website: ccswitch.io