codemem

Persistent memory for OpenCode and Claude Code. codemem captures what you work on across sessions, retrieves relevant context using hybrid search, and injects relevant context automatically in OpenCode.

• Local-first — everything lives in SQLite on your machine
• Hybrid retrieval — FTS5 BM25 lexical search + sqlite-vec semantic search, merged and re-ranked
• Automatic injection — the OpenCode plugin injects context into every prompt, no manual steps
• Claude Code plugin support — install from the codemem marketplace source
• Built-in viewer — browse memories, sessions, and observer output in a local web UI
• Peer-to-peer sync — replicate memories across machines without a central service

Light	Dark

Quick start

Prerequisites: Python 3.11+ and uv

If uv is not installed yet:

# Homebrew
brew install uv

# mise
mise use -g uv@latest

1. Install the CLI and plugin:

uv tool install --upgrade codemem

2. Add the plugin to your OpenCode config (~/.config/opencode/opencode.jsonc):

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": ["@kunickiaj/codemem"]
}

By default, the OpenCode plugin resolves backend CLI calls from a uvx source pinned to the plugin version, so plugin and backend stay aligned unless you override CODEMEM_RUNNER / CODEMEM_RUNNER_FROM.

3. Restart OpenCode, then verify:

codemem stats
codemem raw-events-status

That's it. The plugin captures activity, builds memories, and injects context from here on.

Claude Code (marketplace install)

In Claude Code, add the codemem marketplace source and install the plugin:

/plugin marketplace add kunickiaj/codemem
/plugin install codemem

The Claude plugin starts MCP with:

• uvx codemem==<plugin-version> mcp

We still recommend installing/upgrading the CLI for local hook ingestion and manual codemem commands:

uv tool install --upgrade codemem

Claude MCP launch uses uvx; first startup may be slower because uvx can fetch/install tooling on demand.

Claude hook ingestion also auto-falls back to uvx codemem==<plugin-version> ingest-claude-hook when a local codemem binary is unavailable.

Claude hook events are ingested through codemem ingest-claude-hook and share the same raw-event queue pipeline used by OpenCode.

Migrating from opencode-mem? See docs/rename-migration.md.

How it works

Adapters hook into runtime event systems (OpenCode plugin and Claude hooks). They capture tool calls and conversation messages, flush them through an observer pipeline that produces typed memories, and surface retrieval context for future prompts.

sequenceDiagram
participant OC as OpenCode
participant PL as codemem plugin
participant ST as MemoryStore
participant DB as SQLite

OC->>PL: tool.execute.after events
OC->>PL: experimental.chat.system.transform
PL->>ST: build_memory_pack with shaped query
ST->>DB: FTS5 BM25 lexical search
ST->>DB: sqlite vec semantic search
ST->>ST: merge rerank and section assembly
ST-->>PL: pack text
PL->>OC: inject codemem context

Loading

Retrieval combines two strategies: keyword search via SQLite FTS5 with BM25 scoring and semantic similarity via sqlite-vec embeddings. In the pack-building path, results from both are merged, deduplicated, and re-ranked using recency and memory-kind boosts.

Injection happens automatically. The plugin builds a query from the current session context (first prompt, latest prompt, project, recently modified files), calls build_memory_pack, and appends the result to the system prompt via experimental.chat.system.transform.

Memories are typed — bugfix, feature, refactor, change, discovery, decision, exploration — with structured fields like facts, concepts, files_read, and files_modified that improve retrieval relevance. Low-signal events are filtered at multiple layers before persistence.

For architecture details, see docs/architecture.md.

CLI

Command	Description
codemem stats	Database statistics
codemem recent	Recent memories
codemem search <query>	Search memories
codemem embed	Backfill semantic embeddings
codemem serve	Launch the web viewer
codemem db prune-memories	Deactivate low-signal memories (--dry-run to preview)
codemem export-memories	Export memories by project
codemem import-memories	Import memories (idempotent)
codemem sync	Peer-to-peer sync commands

Run codemem --help for the full list.

MCP tools

To give the LLM direct access to memory tools (search, timeline, pack, remember, forget):

codemem install-mcp

This updates your OpenCode config to register the MCP server. Restart OpenCode to activate.

Configuration

Config file: ~/.config/codemem/config.json (override with CODEMEM_CONFIG). Environment variables take precedence over file settings.

Common overrides:

Variable	Purpose
CODEMEM_DB	SQLite database path
CODEMEM_INJECT_CONTEXT	0 to disable automatic context injection
CODEMEM_VIEWER_AUTO	0 to disable auto-starting the viewer

The viewer includes a grouped Settings modal (Connection, Processing, Device Sync) with shell-agnostic labels and an advanced-controls toggle for technical fields.

• Settings show effective values (configured or default) and only persist changed fields on save.

Observer runtime/auth in 0.16:

• Runtime options: api_http and claude_sidecar.
• api_http defaults to gpt-5.1-codex-mini (OpenAI path) unless you set observer_model.
• claude_sidecar defaults to claude-4.5-haiku; if the selected observer_model is unsupported by Claude CLI, codemem retries once with Claude's CLI default model.
• claude_sidecar command is configurable with claude_command (CODEMEM_CLAUDE_COMMAND) as a JSON argv array.
  • Config file example: "claude_command": ["wrapper", "claude", "--"]
  • Env var example: CODEMEM_CLAUDE_COMMAND='["wrapper","claude","--"]'
• Auth sources: auto, env, file, command, none.
• observer_auth_command must be a JSON string array (argv), not a space-separated string.
  • Config file example: "observer_auth_command": ["iap-auth", "--audience", "example"]
  • Env var example: CODEMEM_OBSERVER_AUTH_COMMAND='["iap-auth","--audience","example"]'
• Header templates support ${auth.token}, ${auth.type}, and ${auth.source} (for example Authorization: Bearer ${auth.token}).
• Queue cadence is configurable with raw_events_sweeper_interval_s (seconds) in Settings/config.

Export and import

Share project knowledge with teammates or back up memories across machines.

# Export current project
codemem export-memories project.json

# Import on another machine (idempotent, safe to re-run)
codemem import-memories project.json --remap-project ~/workspace/myproject

# Import from claude-mem
codemem import-from-claude-mem ~/.claude-mem/claude-mem.db

See codemem export-memories --help and codemem import-memories --help for full options.

Peer-to-peer sync

Replicate memories across devices without a central server.

codemem sync enable        # generate device keys
codemem sync pair          # generate pairing payload
codemem sync daemon        # start sync daemon
codemem sync install       # autostart on macOS + Linux

Project filters, per-peer overrides, and config keys are documented in docs/user-guide.md.

Semantic recall

Embeddings are stored in sqlite-vec and written automatically when memories are created. Use codemem embed to backfill existing memories. If sqlite-vec cannot load, keyword search still works.

aarch64 Linux note: The PyPI wheels currently ship a 32-bit vec0.so on aarch64. See docs/user-guide.md for the workaround.

Alternative install methods

Local development, uvx, git install

Local development

uv sync
source .venv/bin/activate  # bash/zsh
source .venv/bin/activate.fish  # fish
codemem --help

Via uvx (no install)

uvx --from git+ssh://git@github.com/kunickiaj/codemem.git codemem stats

Install from GitHub

uv pip install git+ssh://git@github.com/kunickiaj/codemem.git

Plugin from git (advanced)

uvx --from git+ssh://git@github.com/kunickiaj/codemem.git codemem install-plugin

Plugin for development

Start OpenCode inside the codemem repo directory — the plugin auto-loads from .opencode/plugin/.

Documentation

• Architecture — data flow, retrieval, observer pipeline, design tradeoffs
• User guide — viewer usage, sync setup, troubleshooting
• Plugin reference — plugin behavior, env vars, stream reliability
• Migration guide — migrating from opencode-mem
• Contributing — development setup, tests, linting, releases