Curator

A curator terminal session: init, hybrid search, librarian digest, status

Curator is the knowledge plane under your personal knowledge system: any plain-markdown vault + one index database + MCP for agents + a deterministic librarian.

Status: pre-release. Contracts v1 are published and stable; APIs around them are still settling. Not yet packaged — install is build-from-source (Quickstart).

The interactive TUI

curator review opens a tabbed terminal app over your vault: Review proposals (coloured diff, a non-destructive pre-flight drift check, apply/reject), Search the corpus (hybrid retrieval, open notes, related), and preview or generate the librarian Digest.

The Review screen: a proposal queue with status glyphs, the selected proposal's metadata, a green pre-flight banner, and a coloured diff

Every screen, key, and the Search / Digest walkthroughs are in the CLI reference.

Where to start

you want toread
try it in under a minuteQuickstart
understand the design commitmentsConcepts
plug in a reader, Zotero, or your own toolIntegrations
run it on a server, back it up, upgrade itOperations
look something upConfiguration · CLI · MCP tools

The four contracts

Everything that crosses the system boundary is one of four published contracts; everything else is internal and changes freely. Consumers pin versions; additive changes are minors, breaking changes are majors, each contract keeps its own changelog.

contractgovernsspec
kp-note/v1note identity + enrichment frontmattercontracts/kp-note/v1.md
kp-config/v1curator.toml configuration (legacy name kp.toml)contracts/kp-config/v1.md
proposals/v1the only agent write pathcontracts/proposals/v1.md
MCP surface v1the agent tool surfacecontracts/mcp/v1.md

Any producer that writes conforming markdown+frontmatter into the vault is a valid producer — that sentence is the whole integration story. Write a producer spells it out; the sibling Curio reader and Zotero integrate exactly this way.

Source

Curator lives at github.com/alexnodeland/curator. This site is generated from the repo's docs/site/ sources — same sources, same bytes, on every build.