Provide persistent session memory for Claude Code by vaulting conversation decisions, artifacts, and context locally. Retrieve and review past session details across Code, Cowork, and Chat sessions to maintain project continuity and avoid re-explaining yourself.
First-time setup wizard for LoreConvo. Verifies the MCP server is connected, the database is accessible, hooks are configured, and runs a test save/load cycle. Use when the user says "set up loreconvo", "onboard", "/lore-onboard", "verify loreconvo", "test loreconvo setup", or after first installing the plugin.
Vault your Claude conversations for cross-session recall. Use this skill when the user asks to "save this session", "vault this", "remember this", "what did we decide about", "load context for", "/vault save", "session history", "find past sessions", "export session", or wants to recall decisions, artifacts, or context from previous Code, Cowork, or Chat sessions. Also triggers on "tag as persona", "link sessions", "project context", or "skill history".
Overview and orientation for LoreConvo. Use this skill when the user asks "what is LoreConvo", "how do I use LoreConvo", "how does LoreConvo work", "show me what LoreConvo can do", "tour LoreConvo", "intro to LoreConvo", or any other overview or orientation request about the product. Does NOT trigger on action phrases like "save this session" or "search my sessions" -- those go directly to the loreconvo action skill.
Admin access level
Server config contains admin-level keywords
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Your memory follows your identity, not your tool — with your consent.
LoreConvo is the only AI memory that carries your context across Claude Code, Codex, Cursor, and Hermes Agent. One install, one memory, everywhere you code.
Available on the Anthropic Marketplace. Install directly from Claude, or via PyPI:
uvx loreconvo
LoreConvo works across Claude Code, Cursor, Codex, and Hermes -- the same memory layer, no matter which client you reach for. When you switch mid-project, your context travels with you automatically.
Most tools wall off memory by machine or workspace. LoreConvo stores everything locally in a SQLite database you own, and surfaces it wherever you are. You decide what gets saved; nothing is written without your action.
Competing tools auto-write to memory without asking. LoreConvo puts you in control: you decide what's worth keeping, and you can delete any memory at any time.
Every memory shows you exactly where it came from — which surface captured it, when, what project context it belongs to, and which skill generated it. No mystery. Full provenance.
LoreConvo stores everything in a SQLite database on your own machine. No data leaves your computer. No cloud accounts. No vendor with access to your session history.
Your sessions live in ~/.loreconvo/sessions.db -- a file you own, can back up, and can delete whenever you want.
LoreConvo captures two types of memory for each session:
Together these give Claude a structured, searchable record of your project's history, not just a pile of chat transcripts.
LoreConvo's FTS5 search is benchmarked against a 60-session synthetic corpus (6 topic areas, 36 labeled queries).
| Variant | Recall@5 | MRR |
|---|---|---|
| FTS5 + compound token expansion (default) | 88.9% | 0.875 |
| FTS5 baseline (no expansion) | 72.2% | 0.708 |
Compound token expansion (camelCase / snake_case query preprocessing) lifts Recall@5 by +35.7 pp on queries using technical identifiers like autoSave, pipeline_tracker, and get_context_for.
Full benchmark report | Reproduce
One command to install:
bash install.sh
This creates a virtual environment, installs dependencies, and verifies everything works. No system Python changes, no manual pip commands.
Start a session with the plugin loaded:
claude --plugin-dir /path/to/loreconvo
Or load it inside an existing session:
/plugin add /path/to/loreconvo
Replace /path/to/loreconvo with wherever you saved the source folder.
After making code changes, use /reload-plugins to refresh without restarting.
Once loaded, Claude has access to all 28 LoreConvo MCP tools automatically. Ask Claude to "save this session" or "recall what we discussed about X" and it will use the tools on its own.
loreconvo source folderImportant: Shared Database Access
Cowork runs in a sandboxed VM and can't see your Mac's filesystem by default. To read sessions saved by Claude Code, ask Claude in Cowork:
"Mount my ~/.loreconvo folder"
Once mounted, Cowork reads and writes to the same database as Claude Code. Sessions saved in Code appear instantly in Cowork.
Chat doesn't support plugins, so LoreConvo provides a one-command bridge. Run this in your terminal:
bash export-to-chat.sh
This exports your last session and copies it to your clipboard (macOS). Switch to Chat and paste (Cmd+V). Chat instantly has the context from your Code or Cowork session.
To search for a specific session:
bash export-to-chat.sh "tax prep"
The core value of LoreConvo is that context persists across Claude surfaces automatically. Here is the full chain:
Claude Code (~/.claude/settings.json via `claude mcp add`)
|-- SessionEnd hook --> auto_save.py --> ~/.loreconvo/sessions.db
|-- SessionStart hook <-- auto_load.py <-+
|
Cursor (.cursor/mcp.json) <--MCP-----+
Codex (~/.codex/config.toml) <--MCP-+
Hermes Agent (~/.hermes/config.yaml) <-MCP-+
All surfaces: save_session / get_recent_sessions / search_sessions
Claude Chat (web)
|-- export-to-chat.sh --> clipboard --> paste into Chat
Searchable, organized, version-tracked knowledge base for your AI projects. Store documents, tag them, search across them, and inject context into any Claude conversation.
npx claudepluginhub labyrinth-analytics/claude-plugins --plugin loreconvoCross-session, cross-project conversation recall with SQLite storage, auto-tagging, compaction recovery, highlight sharing, and proactive recall assistant skill
Use Memind as persistent memory for Claude Code sessions.
Persistent local memory for Claude Code. Cross-session recall with vector search, automatic archiving, zero cloud dependencies.
Long-term semantic memory for Claude Code, powered by OpenViking. Auto-recall relevant memories at session start and capture important information during conversations.
Universal memory runtime — ambient working-memory substrate for Claude Code. Memory is not a feature you invoke — it's the substrate the agent operates on.
Skills and hooks for rekal: memory redirect hooks, session capture (rekal-save), project bootstrap (rekal-init), and maintenance (rekal-hygiene).