work-memory-mcp

# Work Memory Work Memory is a local-first development memory layer for VS Code and MCP clients. It stores cross-repository work history in SQLite, keeps an append-only JSONL archive for auditability, and exposes that shared memory through a local MCP server. It is designed for one-machine-first use, but the codebase is portable and the memory store can be backed up, restored, or pointed at a synced location. ## What It Does - stores turns, notes, commands, files, entities, topics, and commit references - imports local VS Code chat history from `workspaceStorage` - serves that memory back into VS Code through MCP - keeps retrieval deterministic with metadata-first filters before text search - includes an RLM-inspired recursive recall mode with trajectory metadata and optional JSONL logs ## Quick Start ```bash python -m venv .venv .venv\Scripts\activate pip install -e .[dev] work-memory init work-memory-install-vscode ``` After that, reload VS Code and trust the `work-memory` MCP server when prompted. For a published install from PyPI, use the package name `work-memory-mcp`: ```bash pip install work-memory-mcp ``` ## VS Code Usage If you use this from another VS Code window on the same machine, that other window can query the same history as long as it is configured to launch this MCP server. The memory data is already shared machine-wide by default under `%LOCALAPPDATA%/work-memory`, so the main requirement is MCP client configuration, not a separate database per window. You do not need a global install just to use it across multiple VS Code windows on this computer. A workspace or user-level MCP config can point directly at this project's virtual environment: ```json { "command": "C:/Project/work-memory/.venv/Scripts/python.exe", "args": ["-m", "work_memory.mcp_server", "--transport", "stdio"] } ``` If you want a more stable command that does not depend on this repo path, install the package into a dedicated environment and point VS Code at `work…