Get in touch
Development · Open source

Tools we built for ourselves, and gave away.

We open-source the infrastructure under our products when it’s useful on its own. More to come. This is the first.

PythonPyPIMCP serverVS Code

work-memory

A local-first development memory layer for VS Code and MCP clients. 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.

Install
pip install work-memory
Quick start
work-memory init
work-memory-install-vscode

# Reload VS Code and trust the MCP server when prompted

What it does

  • Cross-repository memory
    Stores turns, notes, commands, files, entities, topics, and commit references.
  • VS Code integration
    Imports local VS Code chat history from workspaceStorage.
  • MCP server
    Serves memory back into VS Code through the Model Context Protocol.
  • Deterministic retrieval
    Metadata-first filters before text search.
  • RLM-inspired recall
    Recursive recall mode with trajectory metadata and optional JSONL logs.
  • Local-first
    Designed for one-machine-first use, portable and backupable.

MCP tools exposed

memory_statussearch_memoryrecall_project_memoryrecall_cross_project_memoryrecursive_recall_memorysummarize_memory_topicstore_memory_notediscover_memory_sourcesimport_vscode_sessions
Example: store a note
work-memory store-note \
  --repo-name my-project \
  --repo-path C:/code/my-project \
  --branch main \
  --session-id session-2026-05-02 \
  --source manual \
  --title "Architecture Decision" \
  --text "Use metadata-first retrieval for better performance." \
  --tag architecture

More on the way.

Reader infrastructure, eval tooling, retrieval pipelines. Bits will surface here as they stabilize. If you have a use case, send a note.

Email usContact form