Skip to content

feat: cross-tool memory mirror (Claude to MCP) #46

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
franzer merged 2 commits into from
Jul 2, 2026
Merged

feat: cross-tool memory mirror (Claude to MCP) #46

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3a994e2
feat: mirror Claude memory and expose it via MCP (cross-tool memory)
franzer Jul 1, 2026
18ee2ba
docs: document cross-tool memory in README
franzer Jul 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -103,6 +103,7 @@ Linked sessions (1):
|---------|-------------|
| **Blame** | Trace any line of code to the AI session that produced it |
| **Git-ref Sync** | Sync reasoning through your existing git remotes, encrypted; share by passphrase |
| **Cross-tool Memory** | Mirror one tool's project memory so any LLM can read it over MCP |
| **Session Capture** | One history across 10+ AI coding tools |
| **Git Linking** | Connect sessions to commits |
| **Full-text Search** | Find any past conversation |
Expand All @@ -120,6 +121,16 @@ Lore syncs reasoning history through your existing git remotes, with no server a

See the [Sync Guide](https://lore.varalys.com/guides/sync/) for details.

## Memory

Coding tools write their own per-project memory (running notes, next steps, corrections) that other tools cannot see. Lore mirrors that memory and exposes it over MCP, so switching tools keeps the context. Point Codex, or any MCP client, at `lore mcp serve` and it can read the memory another tool wrote for the same repo.

- Read-only: Lore mirrors the tool's memory files, it never modifies them.
- Scoped to the current repo.
- `lore memories` lists what has been mirrored.

Currently mirrors Claude Code memory, with more tools to follow. See the [Memory Guide](https://lore.varalys.com/guides/memory/) for details.

## Supported Tools

Claude Code, Codex CLI, Gemini CLI, Amp, Aider, Continue.dev, Cline, Roo Code, Kilo Code, OpenCode
Expand Down
Loading
Loading