Contextual
Freemium
Individual developers managing local codebases
Every time a new agent spins up on your codebase, it starts cold — re-learning the same dead ends, re-asking the same questions, rebuilding context your last session already paid for. claude-mem with CMEM Cloud exists to stop that cycle.
The open-source claude-mem engine hooks into Claude Code, Cursor, Windsurf, and CLI agents, writing decisions and dead ends into a local SQLite observations database as your agent works. CMEM Cloud mirrors that database behind a private MCP endpoint any agent or IDE can read, so the context one agent built in one session is available to the next one without manual handoff. Vector search over the observations store means retrieval is semantic, not keyword-based — you query by meaning, not by remembering what you typed three sprints ago. The ceiling appears at the team coordination layer: role-based read/write scoping and per-project isolation are paid-only features, so solo developers get the full engine but teams hit a paywall before they get the shared-brain behavior the product is built around.
Bottom line: Pick this when you are tired of re-explaining your architecture to every new agent session — but plan for the shared team memory and brainbeat routing you actually want to require a paid CMEM Cloud account.
Free Local memory for your coding agent. Install and run the engine on your own machine.
Your captured context, synced across connected machines and available through your private MCP link.
More included observation usage.
The largest included allowance, plus billed overages.
View full pricing on cmem.ai →
Pricing may have changed since last verified. Check the official site for current plans.
Find your fit
More options in RAG Frameworks. Compare pricing, platforms, and features side by side.
Freemium
Individual developers managing local codebases
Freemium
Teams needing deterministic rules plus RAG explanations
Most AI coding agents have no memory between sessions. You rebuild context every time: same repo walkthrough, same explanation of why you chose the edge runtime, same warning about the dead end in the KV store. claude-mem is the open-source engine that runs as a hooks layer inside your agent, capturing decisions, fixes, and dead ends as structured observations into a local SQLite database. One install command — no config, no account required — wires the engine into Claude Code, Cursor, Windsurf, Codex CLI, Gemini CLI, and any other MCP-compatible client. CMEM Cloud then mirrors that local database to a private MCP link, making the accumulated memory reachable from every machine, IDE, and agent on the same account.
The differentiating mechanism is the brainbeats system. Rather than waiting for an agent to query memory, the cloud layer fires targeted context briefings — brainbeats — when a stored observation becomes relevant to what is happening now. The vendor describes this as routing context ‘the moment it is needed, not in a digest’: a checkout error rate spike triggers a triage agent briefing automatically, a merged API contract triggers a docs agent rewrite. This moves the memory layer from passive recall toward something closer to ambient awareness across a fleet of agents.
The tool fits tightest for individual developers running multiple agents across multiple machines who are losing context between sessions. Teams that need shared memory, per-project isolation, and role-based access get those features, but they sit behind a paid CMEM Cloud tier — the open-source engine is single-node. For projects where the branching logic or agent coordination happens inside the agents themselves rather than in a memory layer, claude-mem adds little; it is a recall and briefing tool, not a workflow runner.
The open-source engine installs via npx and ships Apache-2.0 licensed. The vendor cites 88,600-plus observations in the public browse view, ships a changelog described as weekly cadence, and documents the CLI reference and MCP spec in the developer docs. The CMEM Cloud tier exposes a private MCP link at a fixed endpoint any MCP client can point at, and the vendor states the architecture is offline-first with cloud mirroring — the local database is the source of truth, sync is secondary.
Sign in to rate this tool or suggest an edit.