The SME your team never had.
Kluris turns your AI agents into a subject matter expert that never sleeps and never quits — built collaboratively with you, one approved entry at a time.
Two surfaces · one brain · six beats
The kluris CLI. You run these yourself — install, create a brain,
push/pull changes, regenerate the MRI.
One slash command — /kluris — followed by whatever you want to say.
Run it while your agent is open on a project so it can read the code.
With more than one brain registered it becomes /kluris-<name>.
The six beats ahead
Beat 1
Set up
Beat 2
Teach
Beat 3
See
Beat 4
Use
Beat 5
Grow
Beat 6
Self-improve
Use ← → or Space to navigate · 1–9 to jump to any slide.
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 Brain type: [1] project-group [2] personal [3] product [4] research [5] blank Choice: 1 Location: ~/Projects/acme-brain Initialize git? y ✓ Created acme-brain ✓ Git initialized on main ✓ Registered acme-brain ✓ Installed /kluris skill for 8 agents Next: open any project in your AI agent and type /kluris learn this service
project-group defaults
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)
Scaffolded defaults for the project-group brain type. You add, rename, or remove lobes as your team grows.
Every brain is a git repo. Your knowledge is markdown. Nothing is magic.
Teach the brain what your team knows.
Open your AI agent in a project — a repo, a service, a codebase — and one slash command,
/kluris, turns the conversation into knowledge. Say learn,
remember, or anything in between; the agent picks the right behavior.
Lobes are folders you create to group related ideas — one per concern, as
many as you need. Neurons are the markdown files inside them. You approve every
neuron before it lands.
> /kluris learn the auth flow Analyzing src/auth/... (14 files) Proposing neuron: projects/btb-core/auth-flow.md ────────────────────────────────────── # Auth flow We use Keycloak OIDC. Frontend obtains JWT via Keycloak, passes it to backend as Bearer token. Backend validates via JWKS. Refresh at 80% TTL. Related: [clerk-vs-keycloak.md, jwt-rotation.md] ────────────────────────────────────── [a]pprove [e]dit [s]kip [c]hange lobe:
> /kluris remember we chose raw SQL over JPA for query complexity Proposing: knowledge/use-raw-sql.md ────────────────────────────────────── # Use raw SQL over JPA ## Context Query complexity and performance on the reporting endpoints... ## Decision Use NamedParameterJdbcTemplate with explicit raw SQL... ## Consequences Less ORM magic, more typing, faster queries, clearer SQL in git diffs. ────────────────────────────────────── [a]pprove [e]dit [s]kip:
Grounded
The agent only writes what you approved. No extrapolation, no invented facts.
Reviewable
Every neuron is a markdown file with a clear path, frontmatter, and body — inspectable before it lands.
Collaborative
Teach it once. Every agent on every laptop reads the same source of truth tomorrow.
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.
Ask the brain. Get grounded answers.
Every agent on your team can search and query across the brain. The agent shows you exactly which neurons it read — no hallucinations, no vibe.
> /kluris search auth flow Found 3 neurons: projects/btb-core/auth-flow.md ★★★ knowledge/jwt-rotation.md ★★ infrastructure/keycloak-setup.md ★ Run `/kluris open auth-flow.md` to read one.
> /kluris what do we know about Docker? Reading: infrastructure/docker-builds.md infrastructure/environments.md You build multi-stage Dockerfiles with BuildKit. Images go to ghcr.io/zeespire/. Prod uses Coolify on Hetzner with Cloudflare Tunnel (zero public ports).
Search
Ranked hits across neurons, glossary, and the brain.md map. The agent opens only what actually answers the question.
What do we know
Natural-language Q&A. Ask it anything about the brain; it cites the neurons it read so you can verify.
Context sharing
Onboarding, pairing, code review — every teammate who clones the brain sees the same answer tomorrow.
Plan with context you didn't have to re-derive.
Kluris is the brain. Specmint turns a feature request into a persistent spec built from deep research and iterative interviews. Pair them and the research phase starts half-done — grounded in your code and the knowledge your team already agreed to.
1 · Shorter research
Forge reads your repo and consults the brain. Decisions the team already made don't get re-discovered from the code.
2 · Sharper interviews
Phase 2 stops asking what the brain already knows. Questions get surgical — the non-obvious trade-offs only you can decide.
3 · Traceable decisions
Every spec decision references a neuron. Six months later you know why — not just what — the code looks the way it does.
> /specmint-core:forge add OAuth sign-in with GitHub Phase 1a · Codebase research ● Reading src/auth/ (14 files) ● Reading config/GlobalExceptionHandler.kt Phase 1b · Brain research ← the kluris bit ● /kluris what do we know about auth → knowledge/auth-decisions.md → projects/btb-core/auth-flow.md → knowledge/jwt-rotation.md Phase 2 · Interview Q1. Brain says you chose Keycloak for cost. Should GitHub OAuth live behind Keycloak as an IdP, or alongside it? Q2. Auth-flow neuron says refresh-at-80% TTL. Same cadence for the GitHub session? Phase 3 · Spec written ✓ .specs/github-oauth-signin/SPEC.md ✓ 3 phases · 14 tasks · 4 decisions logged ✓ Every decision references a neuron
Enable Specmint Companions
specmint-core
Spec-firstResearch · Interview · Spec · Implement. The workflow shown above.
kluris companion add specmint-core
bundled with kluris
specmint-tdd
Red · Green · RefactorSame forge flow, with strict TDD — a failing test before any implementation.
kluris companion add specmint-tdd
bundled with kluris
Enable companions per brain; Kluris copies only the bundled SKILL.md and references it from the generated /kluris skill.
Your brain grows with your team.
Add lobes, add neurons, keep going — all through the agent.
> /kluris 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 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.
Run kluris push to commit and share with your team.
Have more than one brain? Each installs as
/kluris-<name>
and everything above works the same.
Let the brain review itself.
Ask the agent to audit the brain. It reads across every neuron, spots connections you never wrote, and proposes new synapses — you approve each one before anything changes.
> /kluris review this brain and create more synapses Reading 34 neurons across 3 lobes... Found 14 connections you haven't written yet: › projects/btb/auth-flow.md ↔ knowledge/jwt-rotation.md › infrastructure/docker-builds.md ↔ infrastructure/environments.md › knowledge/use-raw-sql.md ↔ projects/btb/reporting.md › projects/btb/import.md ↔ infrastructure/keycloak-setup.md ... 10 more Proposed update · projects/btb/auth-flow.md ────────────────────────────────────── --- title: Auth flow related: - ./clerk-vs-keycloak.md - ../knowledge/jwt-rotation.md (new) --- ────────────────────────────────────── [a]pprove all [o]ne-by-one [s]kip: o Stepping through 14 proposed synapses... ✓ 12 applied · 2 skipped ✓ bidirectional links written ✓ maps regenerated
Grounded
The agent only proposes synapses between neurons that already exist — no hallucinated references.
Reviewed
You approve every change — one-shot, one-by-one, or skip — before anything is written to disk.
Compounding
Re-run it monthly. As the brain grows, the agent finds new patterns and your knowledge graph gets denser.
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.
What you installed
A Python CLI.
One pipx install · nothing to host, nothing to log into.
What you built
A living brain.
Lobes · neurons · synapses · all markdown, all git-tracked.
What changed
Every agent, smarter.
Claude Code, Cursor, Windsurf, Copilot, Codex, Gemini, Kilo, Junie.
Start now
From zero to a smarter team.
$ pipx install kluris $ kluris create # new brain from scratch # — or — $ kluris clone git@github.com:team/brain.git # join a team brain $ kluris register ~/path/to/brain # adopt a brain already on disk → agent skills auto-install · open any repo · type /kluris in chat
Open source · MIT · Free forever · Yours, always.
kluris · a guided tour · kluris.io · source
Use ← → or Space to navigate · 1–9 to jump.