Use case · claude-mem for VS Code

claude-mem for VS Code

Reach your memory from any MCP-capable VS Code extension.

cmem lets you reach your memory from any MCP-capable VS Code extension. The open-source engine captures structured observations locally; CMEM Cloud links them to VS Code through one private MCP endpoint, shared with every other MCP client. Your agent remembers across the whole editor.

How it fits VS Code
Capability
Without cmem
cmem.ai
Connection
No shared memory
Private MCP link in VS Code
Memory persistence
Per-session only
Across every project & machine
Capture
Manual notes
A second model writes observations
Recall
Scroll back & paste
Semantic vector search
Price
$0 cloud during early access
How it integrates

Up and running with VS Code

01

Install the engine

Run npx claude-mem@latest install to set up local memory capture.

02

Add the MCP link

Add your private MCP link to any MCP-capable VS Code extension.

03

Recall in the editor

VS Code reads the same memory as every other agent you use.

What you get

Memory that compounds, built in

Automatic capture

A second model writes structured notes out-of-band — no prompting, no slowdown.

Auto-categorization

Decision, bugfix, feature, discovery, security — every note lands in a taxonomy.

Search three ways

Semantic, keyword, and timeline search over everything your agents have done.

Causality threading

Before/after links connect why a change happened to what came next.

Local-first & private

Memory lives in local SQLite with privacy stripping; cloud sync is opt-in.

Smart-explore

Structural codebase exploration that is 6–12× cheaper than reading files in full.

See all features →

Early access

Bring memory to VS Code

The engine is open source and free to install today. Cloud sync is $0 during early access — join the waitlist and your private MCP link arrives by email.