Lore MCP server

📖 Lore

Shared, full-fidelity, session history for every AI agent you use.

Any Agent. Any Session. Any Turn. Anytime.

The session you ran in Claude Code this morning, Openclaw can pull up this afternoon. The debugging thread Cursor worked through last week, Hermes can read like it was sitting right there. Lore gives all of your coding agents one shared memory: across every tool, across every session, and it never expires.

That is the part most "agent memory" misses. Other tools remember things for one agent, inside one app. Lore makes every session any of your agents has ever had searchable by any other agent, anytime. What Codex figured out, Claude Code knows. What you solved on Tuesday is one search away on Friday, in whatever agent you happen to be in.

And yes, it survives compaction. When a context window fills up and compacts, the work isn't gone, it's sitting right there on disk. Lore just makes it reachable again, fully searchable, right where your agents work. Local, private, and yours forever.

https://github.com/user-attachments/assets/b5c0f077-47da-4502-bf78-2ce08abf034f

Inspired by RLM

v0.2.0 release

This release turns Lore from a search box over old transcripts into a small workflow substrate for agents that have to continue real work:

again. lore status --json reports both schemaVersion and supportedSchemaVersion, so stale global installs are obvious before sync, index, or push writes fail.

• Schema 5 write support. Current installs can read and write the live store

window is ready, missing, stale, or possibly unsynced before it writes a brief or handoff from incomplete memory.

• Freshness checks. lore status tells an agent whether a source/project

transcript tree incrementally. This covers codex (~/.codex/sessions, with archived sessions as a compatibility fallback) and claude-code (~/.claude/projects) without forcing agents to remember raw paths.

• Live detected-source sync. lore sync indexes a detected active

lore-handoff, and lore-dev-verification alongside the base lore skill. They include references, examples, eval specs, validators, and committed test reports.

• Workflow skills. The npm package now ships lore-recall, lore-brief,

validates the real tarball so README, help text, skill folders, executable mode, and package metadata are checked together.

• Package smoke proof. npm run package:smoke builds, packs, unpacks, and

Already installed? Refresh the global command before testing any schema or sync behavior:

npm install -g @jordanhindo/lore@latest
lore help
lore status --json

If your shell cached the old path, open a new terminal or run hash -r and retry lore help.

✨ Why you'll want it

Hermes histories all land in one store (separate from their own /. stores), and any MCP client reads it. A session in one agent is instantly readable by all the others. What Codex figures out, Claude Code knows.

• 🔀 One memory, every agent. Claude Code, Codex, openclaw, Cursor, and

Last week's reasoning is one search away.

• 🧠 It outlives the context window. Compaction stops meaning amnesia.

stay findable as whole words, not shredded into noise.

• 🔍 Search that speaks code. getUserById, foo.bar.ts, and trust-metadata

machine. Nothing phones home. Ever.

• 🔒 Local by default. Everything lives at ~/.lore/lore.db on your

🚀 Quick start (paste this into your agent)

Lore sets itself up. Drop the blurb below into any coding agent. It installs Lore, indexes your own history, and proves search works before it calls itself done. It is server-free by default, with no MCP registration required.

Shortened. The full README is on GitHub.