Skip to content

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

Merged
franzer merged 2 commits into
mainfrom
feat/phase-30-memory-mirror
Jul 2, 2026
Merged

feat: cross-tool memory mirror (Claude to MCP)#46
franzer merged 2 commits into
mainfrom
feat/phase-30-memory-mirror

Conversation

@franzer

@franzer franzer commented Jul 1, 2026

Copy link
Copy Markdown
Member

Read-only mirror of a coding tool's per-project memory store, exposed over MCP so any LLM can read the memory another tool wrote (the "Codex can't see what Claude noted" gap). This is the Phase 30 MVP.

  • New memories table + FTS and a Memory model.
  • Capture (mirror) from Claude's per-project memory folder (~/.claude/projects/<slug>/memory/, the sibling of the sessions dir Lore already knows): parses MEMORY.md plus per-fact markdown (frontmatter name/description/type + body), reflects the folder state (add, update, remove), and refreshes on read so no daemon is needed. Strictly read-only: it never writes to the tool's files.
  • MCP tools lore_get_memories and lore_search_memories, scoped to the current repo (git top-level).
  • lore memories CLI to list them (text or json).

Everything is scoped to the current project. Deferred by design: git-ref sync of memories, other tools' stores (Codex, Gemini), a write path, and embeddings.

Tests: capture/parse and mirror semantics (add/update/remove/missing folder), search, slug resolution, MCP shape. Full suite green, clippy -D warnings clean. Verified live against a real Claude memory folder.

@franzer
franzer merged commit 5888eb1 into main Jul 2, 2026
5 checks passed
@franzer
franzer deleted the feat/phase-30-memory-mirror branch July 2, 2026 02:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant