Teamlore

= 18" />

  Break things only once. Shared memory for your team's Claude Code —
  one dev's agent learns a lesson, every teammate's agent remembers it.

Table of Contents

- teamlore
- Why teamlore
- scarmap — see the scars move
- How it works
- Getting Started
  - Requirements
  - Install
  - Uninstall
- The lore contract
- Lore is code — review it
- Our own brain
- Telemetry
- Roadmap
- License

teamlore

teamlore is shared memory for your team's Claude Code. Agents distill
hard-won lessons into small, reviewable files in a .lore/ folder; every
teammate's agent recalls them automatically when they touch the relevant code.

No server. No accounts. No embeddings. The brain is a folder in git —
onboarding a teammate is git pull.

Why teamlore

Monday: Billy's Claude causes double refunds. She fixes it.
Tuesday: your Claude opens the same file — and almost does it again.
The lesson existed. It was trapped in her session history.

teamlore ends that. One agent distills the lesson into a small lore file.
Every teammate's agent recalls it. When it stops a repeat, the terminal says so:

teamlore is built for teams that want their agents to compound knowledge
instead of repeating mistakes. It helps you:

- Capture lessons at the moment they're learned — corrections, surprising
  failures, decisions with a stated why
- Recall them exactly where they matter — path-scoped, never a full dump
- Keep humans in control — every memory is reviewed and merged like code
- See the whole picture — render the brain as a living scar map

scarmap — see the scars move

One command renders .lore/ as a living scar map — a force-directed
graph that settles in front of you, in your browser. Every node is a lesson,
sized by severity (mistake > gotcha > decision) and colored by decay
(fresh →…