rememberLABSCO SUMMARY
It captures from the work, not from you remembering to write things down.
The problem it goes after is not a forgotten fact but repeated work — an agent re-proposing the approach you rejected last month, or re-discovering the constraint that broke production. Hooks record sessions, commits and failures as they happen, and the graph layer supersedes what has been overtaken instead of letting two contradictory memories both come back. It is one SQLite file on your machine, and the cloud is optional.
What it is
MeMesh gives coding agents a memory that survives the session. Hooks capture it from real work — sessions, commits, failures — rather than from notes someone remembered to write, recall injects it at the moment the agent acts, and a knowledge-graph layer supersedes what has been overtaken and flags memories that contradict each other.
What you get
- Nine tools the agent calls directly:
remember,recall,forget,learn,briefing,task_state,user_patterns,exportandimport - Auto-capture inside Claude Code — hooks fire at session start and before file edits, so what lands in the store is what happened
- Recall that runs before an edit rather than only when asked for
- Keyword search on SQLite FTS5 out of the box, with meaning-based search as an opt-in needing an embedder — Ollama locally, or a cloud one you configure
- One database shared by both install paths, so a memory captured in a Claude Code conversation is recallable from Codex CLI, Gemini CLI or Cursor
- A local dashboard and an HTTP API over the same store, served by
memesh serve memesh doctorto verify the install end to end, andmemesh setupto detect the hosts you use and wire each one
Requirements
Node 22.13 or newer, and nothing else — no Docker, no cloud, no compiler, because the store is Node's own node:sqlite and the memory lives at ~/.memesh/knowledge-graph.db. There are two install paths and most people want both. Inside Claude Code, /plugin marketplace add PCIRCLE-AI/memesh then /plugin install memesh@pcircle-memesh wires the hooks, tools and skill. In a terminal, npm install -g @pcircle/memesh puts memesh and the memesh-mcp stdio binary on PATH for Codex, Gemini, Cursor and other MCP clients. Installing the plugin does not put the CLI on PATH — that is the one that catches people out.
Setup effort
One command — npm install -g @pcircle/memesh
USE CASES
Stopping an agent re-proposing something you rejected
Store the decision with its reason, so the next session recalls it before suggesting the same thing again.
Starting a session already knowing where things stand
Read the briefing and the state of the work in progress before the first edit.
Turning a long session into something durable
Convert what actually happened into lessons instead of leaving it in a transcript.
Carrying the memory to another machine
Export the store, then import it where the other agent runs.
Dropping a fact that no longer holds
Remove the memory rather than letting it keep surfacing in recall.
9 tools
Listed in project docs. Your client may show a different list.
recallforgetexportimportlearntask_statebriefinguser_patternsBEFORE YOU INSTALL
What to know first
Tools you get
9 tools named in the project's documentation.
Requires
memesh-mcp on PATH
INSTALLATION
Connect your client
Server setup
npm install -g @pcircle/memeshMCP Clients
Claude Code
/plugin marketplace add PCIRCLE-AI/memesh
/plugin install memesh@pcircle-memeshGemini CLI
gemini mcp add -s user memesh memesh-mcpCursor
{
"mcpServers": {
"memesh": {
"command": "memesh-mcp"
}
}
}Hermes Agent
hermes memory setup memesh