LoreConvo + LoreDocs

Two vaults, one memory layer for Claude
LoreConvo remembers what you talked about -- sessions, decisions, open questions, and the flow of work across time.
LoreDocs remembers what you know -- documents, references, configs, and structured knowledge organized by project.

💬
LoreConvo

Session memory across surfaces
What It Stores

Session summaries, decisions made, artifacts created, open questions, skill usage, persona tags, and cross-session links.

MCP Tools (12)
save_session search_sessions get_context_for get_recent_sessions vault_suggest tag_session link_sessions create_project get_project list_projects get_session get_skill_history

📚
LoreDocs

Knowledge management for AI projects
What It Stores

Versioned documents organized into vaults, with full-text search, category/priority tagging, cross-vault linking, and Free/Pro tier gating.

Key MCP Tools (32)
vault_create vault_list vault_add_doc vault_search vault_inject_summary vault_link_doc vault_find_related vault_suggest vault_export_manifest vault_tier_status vault_set_tier vault_info
🗃
SQLite + FTS5
~/.loreconvo/sessions.db
🗃
SQLite + FTS5 + Filesystem
~/.loredocs/loredocs.db + vaults/
Where They Run
⌨
Claude Code
Terminal. Full plugin support. SessionEnd hook auto-saves to LoreConvo.
LoreConvo LoreDocs
🖥
Cowork
Desktop app. Plugin support via .plugin files. Mount ~/.loreconvo for shared DB.
LoreConvo LoreDocs
🎨
Claude Chat
Web. No plugin support. Use export-to-chat.sh to bridge context via clipboard.
Clipboard bridge
Cross-Project Context Sharing
💬
Project A
Work happens here -- decisions, artifacts, questions
➡
💾
save_session
LoreConvo captures the session summary
➡
🗃
Shared DB
Global SQLite -- not scoped to any project
➡
🔍
get_context_for
Search by topic from any project
➡
💬
Project B
Context arrives without moving the chat

How They Complement Each Other

📋
Session saves reference docs
LoreConvo's artifacts field tracks which LoreDocs docs were created or updated during a session.
🔌
Vaults link to projects
LoreDocs' linked_projects maps vaults to LoreConvo project names, so both systems share a project namespace.
💡
Proactive suggestions
Both have a vault_suggest tool. LoreConvo surfaces open questions; LoreDocs surfaces related docs you might need.
🛠
Skill tracking bridges both
LoreConvo logs which skills were used per session. LoreDocs organizes the reference docs those skills need.
🕑
Temporal vs. structural
LoreConvo is a timeline -- "what happened when." LoreDocs is a library -- "what do we know." Together they cover both dimensions.
🔒
Same local-first architecture
Both use SQLite + FTS5, store data on your machine, run over stdio MCP transport, and cost zero API calls. Same DNA, different jobs.
LoreConvo sessions + decisions LoreDocs documents + knowledge shared project names Code | Cowork | Chat All surfaces read from both vaults
Labyrinth Analytics Consulting -- local-first AI memory layer