Long-Term Code Project Maintenance
Continuously modify the same codebase across multiple sessions without repeatedly explaining module relationships, naming conventions, and historical decisions
Best for:Software Developers
Personal Agent / Productivity

claude-mem is an open-source plugin that enables Claude to retain and restore contextual memory across different sessions.
Website created
2026-01-10
OpenRouter token usage rank
#25
Source: OpenRouter
Monthly unique visitors
41,848
Source: SimilarWeb

This product is positioned as a session memory extension tool for Claude users, mainly running by being installed in environments such as Claude Code, Cursor, or Cowork. It records the user's interaction history with AI, code changes, and decision-making processes, then compresses them and automatically injects relevant content when a later new session starts. Its core strength is cross-platform and cross-session memory transfer, avoiding the need to rebuild context from scratch each time. It is suitable for developers who use Claude long-term for code projects or task planning, as well as individual users who need continuous collaboration. Compared with other memory tools, it integrates directly into the Claude plugin system and focuses on session history compression and automatic restoration rather than standalone knowledge base management.
One-line summary
claude-mem is an open-source plugin that enables Claude to retain and restore contextual memory across different sessions.
What people use it for
After installation, users enter commands in Claude sessions to have it record the current work, and then automatically receive the architecture, conventions, and modification history of previous projects when a new session begins. Users can also use it to continue unfinished tasks after a Cowork container restarts, without having to repeat the background information.
Best for
Individual productivity users, operations teams, and automation builders
How it works
Users typically start from the command line, IDE, or desktop app, then complete work through multi-step task planning and tool calls.
Product type
Extension / Plugin
Pricing
Unknown
The current enhanced batch dataset does not maintain real-time pricing for this product. Please refer to the official website or official documentation.
APIMaster integration
Unknown
Pending verification
Data confidence
Medium
Last verified: 2026-08-30
Automatically compresses session history into semantic summaries, stores them locally, and automatically injects relevant context into later sessions
Provides three MCP tools: search (returns memory indexes), timeline (views preceding and subsequent events), and get_observations (retrieves full details)
All memory data is stored in a local SQLite database, with support for excluding sensitive content via private tags
Memory can automatically follow and be restored across Claude Code, Cursor, and other Agent platforms
Automatically runs background tasks such as extractMemories and sessionMemory after each response to generate structured memory files
Continuously modify the same codebase across multiple sessions without repeatedly explaining module relationships, naming conventions, and historical decisions
Best for:Software Developers
Review tool call logs and observation results from previous sessions to quickly locate pitfalls encountered before
Best for:Programmers
Continue the same writing or project planning across different sessions, automatically carrying over user preferences, background, and constraints
Best for:Content Creators
After completing tasks in disposable cloud containers, automatically load memory from the last work session when a new session or new Agent starts
Best for:AI Agent Users
We do not yet have reliable evidence that this product supports third-party keys, proxies, custom providers, or a custom base URL, so we do not show speculative setup steps or config values.
Discussion summary
Users generally understand claude-mem as a cross-session memory plugin for Claude AI that can compress historical conversations and inject key context, allowing the Agent to retain project structure, decisions, and preferences during long-term tasks. Discussion focuses on how to use it for coding collaboration, project maintenance, and planning or writing scenarios to reduce repeated explanations of context. Users also frequently discuss how to combine it with other memory tools, as well as its impact on usage volume and performance.
Users discuss how to configure it to remember code architecture, module relationships, and historical decisions so they do not need to re-explain the project background in every new session.
Users share practices for combining claude-mem with basic memory systems or knowledge graph tools to build a more durable Agent memory layer.
Users discuss whether compressing context increases token consumption and how to optimize it to avoid affecting overall usage efficiency.
Users explore how to make it remember personal preferences, constraints, and background information so long-term collaborative conversations remain more coherent.
We currently classify it under "Personal Agent / Productivity," and the page description is based on public information from the official website and sources such as OpenRouter.
The enhanced page for claude-mem prioritizes displaying the core tasks and use cases that have already been collected, helping you quickly judge whether it matches your current needs.
There is currently no reliable source confirming that the product supports third-party keys or custom compatible endpoints, so the page status is shown as pending verification.
Also in the Personal Agent / Productivity category, suitable for side-by-side comparison of different task entry points and product formats.
Also in the Personal Agent / Productivity category, suitable for side-by-side comparison of different task entry points and product formats.
Also in the Personal Agent / Productivity category, suitable for side-by-side comparison of different task entry points and product formats.
Sources:Official websiteGitHub
Last verified: 2026-08-30 · Report a correction