Learn
Wenlan AI work memory guides.
Wenlan makes AI work compound across Claude Code, Cursor, Codex, and other MCP-compatible tools. Memory is one mechanism; durable work context is the goal.
Learn topics
AI work memory
Setup guides
Client workflows
Distilled wiki pages
Named comparisons
Local-first trust
Start here
Search intent first. Start with the problem or phrase you would type into Google, then move into setup, workflow, trust, and comparison articles once the route is clear.
Popular search paths
Search demand
Claude Code memory
Understand CLAUDE.md, /memory, and when Wenlan adds shared local context.
Claude Code /memory
Decide when native Claude Code memory is enough and when shared local MCP memory helps.
MCP memory server
Connect Claude Code, Cursor, Codex, and other MCP clients to durable memory.
Cursor memory MCP
Wire Cursor to Wenlan's local MCP memory server and verify recall.
Local AI memory
Keep project context local, inspectable, and under your control.
Wenlan memory
Map the brand to the category: local AI work memory across tools.
Wenlan vs alternatives
Compare Wenlan with Basic Memory, claude-mem, Superlocal, Obsidian, and others.
Concepts
15 articles
Concept
What Is AI Work Memory?
AI work memory carries sessions, decisions, lessons, project context, and wiki pages across tools and time.
Protocol
MCP Memory Server for Claude Code, Cursor, and Codex
Learn what an MCP memory server does, how it connects AI tools to durable context, and how Wenlan keeps that memory local and inspectable.
Privacy
Local-First AI Work Memory: Keep Context on Your Machine
Local-first AI work memory keeps sensitive project knowledge, decisions, and preferences under your control while still making them useful to assistants.
Concept
Distilled Wiki Pages: Why Wenlan Composes Memory
Wenlan does not stop at storing memory snippets. It composes related captures into source-backed wiki pages that agents and humans can reuse.
Architecture
Why Wenlan Uses Readable Artifacts plus a Local Store
Wenlan keeps raw captures in a daemon-owned local store and projects readable artifacts, so AI memory stays inspectable and useful.
Decision
AI Agent Memory: Local vs Cloud
Choose between local-first memory and hosted memory based on privacy, portability, collaboration, and operational needs.
Problem
Why AI Coding Agents Lose Context Between Sessions
Understand why useful coding context disappears and how a local work-memory loop keeps decisions available.
Concept
Persistent Project Context for AI Agents
Keep project decisions, constraints, and handoffs available across Claude Code, Cursor, Codex, and other AI tools.
Setup
MCP Memory Server on localhost:7878: What to Check
Understand the local daemon boundary behind Wenlan's MCP memory tools and how to troubleshoot port 7878.
Capture
What to Capture in AI Work Memory
Use a simple test for deciding what belongs in Wenlan and what should stay out of memory.
Trust
Source-Backed Wiki Pages for AI Work
Why Wenlan distills repeated memories into pages that keep source IDs and refresh state attached.
Trust
AI Memory Provenance: Why Source IDs Matter
Understand why AI memory needs source trails, supersession, and review before old context steers new work.
Trust
Local Git History for AI Memory Artifacts
Why Wenlan versions readable memory artifacts in a local git repository under ~/.wenlan/.git.
Trust
Review Before Trust in AI Memory
Why useful AI memory should expose low-confidence captures, contradictions, revisions, and forget paths.
Trust
Project Scope for AI Memory in Wenlan
Understand how Wenlan scopes local AI work memory with spaces, project context, and deliberate product boundaries.
Comparisons
9 articles
Comparison
AI Work Memory vs Knowledge Base: Which One Do You Need?
A knowledge base stores what you know. AI work memory carries decisions, handoffs, lessons, and evolving context back into agent sessions.
Comparison
Wenlan vs Basic Memory: Local AI Work Memory vs Markdown Knowledge Base
Compare Wenlan and Basic Memory across Markdown, MCP, local-first control, workflow fit, and how each product helps AI tools use durable context.
Comparison
Wenlan vs claude-mem: Which Claude Memory Workflow Fits Your Work?
Compare Wenlan and claude-mem for Claude Code memory, observer-style capture, MCP access, local control, and work that spans tools.
Comparison
Wenlan vs Superlocal Memory: Local-First AI Work Memory for Work That Spans Tools
Compare Wenlan and Superlocal Memory as local-first AI memory tools for coding work, retrieval quality, MCP workflows, inspectability, and trust.
Comparison
Wenlan vs mcp-memory-service: Local AI Work Memory or Agent Pipeline Backend?
Compare Wenlan with mcp-memory-service across user workflow, transports, storage control, and agent-pipeline scope.
Comparison
Wenlan vs ChatGPT Memory: Built-In Personalization or Local AI Work Memory?
Compare built-in assistant memory with Wenlan's local, inspectable, cross-tool work-memory layer.
Comparison
Wenlan vs Obsidian AI Memory: Vaults, MCP Bridges, and Agent Work Context
Compare Wenlan with Obsidian, obsidian-mind, claude-obsidian, Claudian, and Obsidian MCP projects for AI agent memory.
Comparison
Wenlan vs Notion AI: Local AI Work Memory or Team Workspace AI?
Compare Wenlan's local AI work memory with Notion AI's workspace, agents, meetings, and enterprise search features.
Comparison
Wenlan vs Mem0: Personal AI Work Memory or App Memory Infrastructure?
Compare Wenlan's local AI work-memory loop with Mem0's memory infrastructure for AI agents and applications.
Workflows
19 articles
Developer workflow
Claude Code Memory: CLAUDE.md, /memory, and MCP Context
Understand CLAUDE.md, Claude Code auto memory, /memory, and when to add Wenlan's local MCP memory for shared project context.
Workflow
Wenlan for Claude Code Memory: The Daily /brief and /handoff Loop
Use Wenlan inside Claude Code with /init, /brief, /capture, /recall, /handoff, and /distill so coding context carries across sessions.
Workflow
The AI Agent Handoff Loop: How Work Carries Across Sessions
A practical model for carrying decisions, lessons, gotchas, and next steps from one AI work session into the next.
Setup
Where Wenlan Stores Claude Code Memory
Find the local files Wenlan writes when Claude Code captures memories, handoffs, and distilled pages.
Setup
How to Add Memory to Claude Code
Install Wenlan's Claude Code plugin, run /init, and verify a local memory round trip.
Claude Code
Claude Code /memory vs Wenlan: Native Memory or Shared Local Context?
Use Claude Code /memory for native project memory inspection, and use Wenlan when context needs provenance, handoff, and cross-tool MCP access.
Setup
How to Give Codex Persistent Memory
Connect Codex to Wenlan through MCP so sessions can recall local project context instead of starting from scratch.
Setup
Cursor Memory MCP: How to Add Local AI Work Memory
Wire Cursor to Wenlan's local MCP memory server so coding sessions can capture and recall project context.
Setup
Claude Desktop MCP Memory Setup with Wenlan
Connect Claude Desktop to Wenlan's local memory daemon through MCP and verify the first memory loop.
Workflow
Wenlan Workflow for Codex
Use Wenlan with Codex for session context, durable captures, recall, and cross-tool handoff.
Workflow
Wenlan Workflow for Cursor
Use Wenlan from Cursor to keep project memory available across edits, branches, and future AI sessions.
Workflow
Wenlan Workflow for Claude Desktop
Use Claude Desktop with Wenlan MCP memory for planning, research, and handoff context that later coding agents can reuse.
Workflow
Wenlan Workflow for Gemini CLI
Connect Gemini CLI as an MCP client and use Wenlan for local capture, recall, and handoff-style notes.
Workflow
Wenlan Workflow for VS Code MCP Clients
Use Wenlan as a local memory server from VS Code surfaces that support MCP.
Workflow
Claude Code Session Handoff with Wenlan
Close Claude Code sessions with enough context for the next agent to resume without replaying the chat.
Workflow
Shared Memory Between Cursor and Claude Code
Use Wenlan as the local bridge when planning, editing, and debugging happen in different AI coding tools.
Workflow
Shared Memory Between Codex and Claude Code
Use Wenlan to carry implementation context between Codex sessions and Claude Code plugin workflows.
Workflow
A Multi-Agent Memory Workflow That Stays Local
Coordinate multiple AI clients through one local memory layer without turning memory into a cloud black box.
Workflow
AI Agent Project Status Handoff
Keep project status usable for the next AI session without bloating memory with transient todos.
Ready to try the local memory loop?
Make AI work carry forward.
Install Wenlan, connect your AI tools, and verify the first memory loop locally.