Install kluris. Create a brain.

A brain is a git repo of curated markdown that every AI agent on your team reads as a subject matter expert. One command to install. One wizard to create your first one.

$ brew install pipx
$ pipx ensurepath
$ pipx install kluris

$ python3 -m pip install --user pipx
$ pipx ensurepath
$ pipx install kluris

> pip install pipx
> pipx ensurepath
> pipx install kluris

$ kluris create

Brain name: acme-brain
What does this brain cover? Shared brain for ACME projects
Location: ~/Projects/acme-brain
Brain type [project-group, personal, product, research, blank]: project-group
Git setup [1=local, 2=with remote, 3=no git]: 1
Default branch: main

Install specmint companions for this brain?
  [1] specmint-core  (spec-driven-development)
  [2] specmint-tdd   (spec-driven-development + TDD focus)
  [3] both           [4] skip
Choice: 3

  ✓ Created acme-brain (project-group · 3 lobes)
  ✓ Git initialized on main
  ✓ Registered acme-brain
  ✓ Installed /kluris-acme skill for 8 agents
  ✓ Bundled specmint-core + specmint-tdd companions

Next: open any project in your AI agent and
      type /kluris-acme learn this service

acme-brain/
├── kluris.yml              # gitignored — your local config
├── brain.md                # root directory, auto-generated
├── glossary.md             # domain terms, hand-edited
├── README.md               # usage guide
├── .gitignore
├── projects/
│   └── (your neurons go here)
├── infrastructure/
│   └── (your neurons go here)
└── knowledge/
    └── (your neurons go here)

Every brain is a git repo. Your knowledge is markdown. Nothing is magic.

See the whole brain.

One command. A local, interactive map you can share.

$ kluris mri

MRI complete — brain-mri.html
  51 neurons, 491 synapses
  → file:///.../brain-mri.html

Open it in any browser. Commit it, email it,
drop it in Slack — it runs anywhere, no server.

Live counts (51 neurons · 491 synapses), a lobe breakdown you can collapse and filter, and a fuzzy search across names, paths, lobes, and tags. Click a lobe to isolate it; click a node to open it.

One click on any node opens its neuron, fully rendered, with the related-neuron tabs across the top so you can walk a topic in seconds. This is what agents see — now visible to you.

Lines between neurons are synapses — cross-links agents follow to load related context. A pre-digested brain means agents spend far fewer tokens orienting to a codebase than without one.

Your brain grows with your team.

Add lobes, add neurons, keep going — all through the agent.

> /kluris-acme add a compliance lobe for SOC2
         and GDPR notes

Proposing new lobe: compliance/
  ✓ will create compliance/map.md
  ✓ will link into brain.md

[a]pprove  [c]ancel: 

> /kluris-acme remember that SOC2 audit evidence
         lives in the compliance-evidence/ bucket,
         rotated yearly

Proposing: compliance/soc2-evidence.md
──────────────────────────────────────
# SOC2 audit evidence

Evidence artifacts live in the
`compliance-evidence/` S3 bucket. Rotation is
annual. Access is restricted to the security team.
──────────────────────────────────────

[a]pprove  [e]dit  [s]kip: 

Lobes are folders, neurons are markdown files inside them — but you don't create them by hand. Ask the agent. It proposes the structure, shows you the diff, and writes it only after you approve. Nesting works the same way: "add a sublobe for the endpoints of acme-api" and the agent puts it in the right place.

Run kluris dream to regenerate maps after structural changes. Commit and share with git directly — kluris brains are plain git repos. Have more than one brain? Each installs as /kluris-<name> and everything above works the same.

Close the loop on every pairing session.

At the end of a long pairing session — research, debugging, decisions, gotchas — sweep the conversation into the brain in one step. The agent replays the chat, pulls every brain-worthy fact, and walks you through proposed neurons one at a time. No retyping. Same approval flow.

> /kluris-acme remember everything
                      from this session

Replaying the conversation...
Identifying brain-worthy items:

  › Decision: use TIMESTAMPTZ for every timestamp column
  › Convention: API errors must include error_code alongside message
  › Gotcha: Cloudflare Tunnel blocks port 587 — use 465 SMTPS
  › Stakeholder: legal flagged session-token storage for review
  ... 3 more candidates

Routing each to the right lobe...

Item 1 / 7
Proposing: knowledge/timestamps-tz.md
──────────────────────────────────────
# Use TIMESTAMPTZ for every timestamp column

Decided 2026-05-12. Standardized on
TIMESTAMPTZ over TIMESTAMP across all
schema migrations. Reason: avoids the
silent UTC drift gotcha when servers
or clients sit in different timezones.

Related: [../projects/btb-core/data-model.md]
──────────────────────────────────────

[a]pprove  [e]dit  [s]kip: a

✓ 5 of 7 captured, 2 skipped, 0 edited

Or capture a single decision in one line: /kluris-acme remember we chose raw SQL over JPA. Same flow, just narrower.

Your AI agents, finally on your team.

Kluris is a tiny idea that compounds: a git repo becomes a brain, a brain becomes a subject matter expert, and that expert shows up in every agent on every laptop every morning — grounded in what your team actually knows.

$ pipx install kluris
$ kluris create                         # new brain from scratch
  # — or — 
$ git clone [email protected]:team/brain.git ~/brains/team && kluris register ~/brains/team   # join a team brain
→ agent skills auto-install · open any repo · type /kluris-acme in chat