When your agent hits a wall and works its way out, it writes down what it learned — and the next agent to hit that wall gets the lesson with the error, on any machine, in any tool. What keeps recurring becomes a rule. What nobody uses gets archived.
npx @lorekit/cli installlive demo
Two sessions, one store, no re-explaining.
memory store
— none yet —
Memories survive session ends · Shared across Claude Code, Cursor & any MCP client
01 / why not just a CLAUDE.md?
A rules file holds what you knew to write down before anything broke. LoreKit captures what your agents find out the hard way — and keeps sorting it: what recurs becomes a rule, what nobody uses gets archived.
a month in the life of one lesson
day 1 · your laptop
Fixed on the fourth try — and written down by the agent. Nobody asked it to.
day 4 · a teammate’s laptop
The lesson arrived with the error, on a machine that had never seen it.
day 9 · CI
Three hits in three places earned it a permanent rule. Now it’s applied before the run.
day 90 · nightly sweep
Lore nobody opens stops riding along in every session. Archived, never deleted.
| Aspect | CLAUDE.md / AGENTS.md | LoreKit |
|---|---|---|
| Written by | You, when you remember to. | Your agents, the moment they hit friction. |
| Knows | What you predicted would matter. | What actually broke — and the fix that worked. |
| Shows up | All of it, every session. | What matches: at session start, on each prompt, on the failing call. |
| Over time | Grows until someone prunes it. | Promotes what recurs. Archives what nobody uses. |
Keep your CLAUDE.md. LoreKit is how you find out what has earned a place in it.
Error-matched recall runs on Claude Code’s hooks; Cursor reads lessons through its rule and an end-of-turn hook.
02 / how it works
The teammate on day 4 got the lesson because of three things: every agent is connected, every lesson knows which repo it belongs to, and the team shares one store.
One command wires the MCP server, the skills and the hooks into Claude Code, and picks up your repo’s scope from its git remote. Cursor is three copied files.
Every lesson lands under a scope: a branch, a repo, a project, or everywhere. Agents read narrowest first, so one repo’s lore never crowds another’s.
Bind repo::acme/* to your org and every teammate’s agent reads and writes the same lessons — one copy, updated for everyone at once. CI reads with a read-only token; anything unbound stays personal.
03 / what you get
A store that learns from the work you already do, and tells you when a lesson has stopped paying for itself.
Every lesson delivered into a session costs tokens whether the agent uses it or not. LoreKit tracks how often each lesson is actually chosen versus merely delivered, estimates what your store costs you a month, and shows you the lore that is earning nothing.
Point a GitHub webhook at a repo and review comments become candidate lessons. Noise is filtered out, and a candidate expires unless it proves useful.
Browse, search and filter everything your agents have learned in the dashboard — who wrote it, where it applies — and edit or archive it in place. Local lore is plain markdown you can grep.
Retention policies find the lore nobody has opened in months and archive it — previewed first, then reviewed by you or swept nightly. Anything archived comes back with one command.
04 / where your lore lives
The same memory tools run against any of the three.
No account, no network.
Markdown files under ~/.lorekit and <repo>/.lorekit — greppable, diffable, and yours. Commit them to share via git, or gitignore them to keep them private.
Shared across machines and teammates.
Every memory is personal by default; org sharing is opt-in. The free plan holds 5,000 active memories at 120 requests a minute.
Your own infrastructure.
The whole stack — MCP server, dashboard, database — deploys to your own Supabase and Vercel projects. MIT licensed.
Start local and move up later — lorekit migrate previews the whole plan before it changes anything.
05 / the fine print, up front
Better you read it here than find it on day one.
get started
Free · Open source · No card, because there is nothing to charge for yet
Run one command
npx @lorekit/cli installPaste a token, or go offline
Sign in for a free token to share lessons across machines, teammates and CI. Or skip it and switch to local mode — lessons stay on this machine as markdown you can read and commit.
Check it’s wired
npx @lorekit/cli doctor confirms the connection, the token and the scopes. With hooks on, every session after starts with the lessons that apply to it.