Shared memory for AI coding agents
Every agent picks up where the last one stopped.
lore gives your AI coding agents one long-term memory per repository. It follows you across your devices and is shared with your team, so the next session starts knowing what the last one learned.
handoff from codex · laptop · 2 days ago
recall decisions/auth-model.md
How it works
Your agents already do the work. lore keeps what they learn.
Nothing to write by hand. lore listens while your agent works and turns sessions into memory the next one can read.
-
Capture
Lifecycle hooks record what your agent does as it works: the prompts, the tools it runs, the decisions it makes. Secrets are stripped before anything is stored.
-
Compile
lore turns those sessions into Markdown pages: decisions, conventions, how a part of the code works. Every page is versioned, and you can read and edit it in the browser.
-
Pick up
The next agent, on any device and for anyone on the project, reads those pages over
MCP. Stop mid-task in Claude Code, open Codex, and carry on with a handoff.
For teams
One memory per repository, not per laptop.
Most agent memory lives in a folder on one machine. lore keeps it on a server you share, one memory per repository.
Per repository
Memory from a repository lands in a project named after it. To share one memory across a team's clones, commit a small .ai-memory.toml naming the shared project.
Across your devices
Each device gets its own key. Lose a laptop and you revoke that key; your access to the memory stays.
Across people
Invite teammates to a repository's memory by username, email or invite link, as a reader, a writer or an admin. Access to the code itself stays with GitHub.
Agents
Works with the agents you already use.
- Claude Code
- Codex
- Cursor
- Gemini CLI
- OpenCode
- VS Code Copilot
Agents with lifecycle hooks feed memory as they work; any agent that speaks MCP can read it. Memory written by one agent is read by all the others.
Get started
Your agents remember from the next session on.
Every account starts with a personal workspace only you can see. When your team is ready, share a repository's memory with them.
- Create an accountPick a username. It appears next to everything you write.
- Create a key for this deviceFrom your account page. One key per device, so each can be revoked on its own.
- Connect your agentAdd lore to your agent as an MCP server with that key. From its next session in your repository, it reads and writes the memory.