Agent Plugins · Community project

Claude-Mem

A hook-based memory plugin that records coding sessions and recalls relevant context through a local worker, database, and search interface.

91.1k StarsApache-2.0JavaScriptUpdated today
01

Project overview

Claude-Mem is a agent plugin built around a hook-based memory plugin that records coding sessions and recalls relevant context through a local worker, database, and search interface. Its value is practical: store coding sessions and retrieve past context are available from one documented project, while the repository remains inspectable before it is added to an agent workflow.

02

Core capabilities

01

Store coding sessions

Store coding sessions is documented in the repository README or its component instructions. Review the linked source for current behavior and requirements.

02

Retrieve past context

Retrieve past context is documented in the repository README or its component instructions. Review the linked source for current behavior and requirements.

03

Restore project memory across tasks

Restore project memory across tasks is documented in the repository README or its component instructions. Review the linked source for current behavior and requirements.

04

Browse memories locally

Browse memories locally is documented in the repository README or its component instructions. Review the linked source for current behavior and requirements.

03

Installation and usage

Set up Claude-Mem from its public GitHub instructions, keep the initial permission scope small, and verify it with a low-risk task before regular use.

AI AGENT INSTALL

Let an AI Agent install it

Send this prompt to Codex, Claude Code, or another AI agent that can work with your local environment.

Help me set up Claude-Mem.
Project URL: https://github.com/thedotmack/claude-mem

Read the repository README and license first. Confirm the current host, prerequisites, destination paths, and permissions. Follow the repository's documented method, keep credentials out of files and logs, and start with the least-privilege or read-only option where available. Afterward, run a small verification and report the exact changes, commands, configuration path, and result. Ask before overwriting files or requesting broader access.
01Before you start
  • Node.js and npx are installed
  • Review the storage scope of the local database and settings directory
02Copy the install command or configuration
npx claude-mem install
03Complete the setup steps
  1. 1
    Review prerequisites and scope

    Read the README, confirm the target host, and prepare these prerequisites: Node.js and npx are installed; Review the storage scope of the local database and settings directory. Check destination paths and permissions before making changes.

  2. 2
    Apply the documented setup

    Run the documented command: npx claude-mem install

  3. 3
    Verify with a small task

    Restart or reload the target agent, confirm that Claude-Mem appears in its installed extensions or skills, and run the smallest documented example before using it on important work.

How to verify the setup

Restart or reload the target agent, confirm that Claude-Mem appears in its installed extensions or skills, and run the smallest documented example before using it on important work.

Before using it
  • Session data enters a local database and needs retention and backup rules
  • A global npm package install provides the SDK but not the full plugin setup
04

Use cases

SCENARIO 01

Maintain the same codebase over time

Maintain the same codebase over time is a practical fit when the repository's documented prerequisites and permission model match the current environment.

SCENARIO 02

Recover decisions from earlier sessions

Recover decisions from earlier sessions is a practical fit when the repository's documented prerequisites and permission model match the current environment.

SCENARIO 03

Reduce repeated project explanations

Reduce repeated project explanations is a practical fit when the repository's documented prerequisites and permission model match the current environment.

05

Assessment

This assessment is based on the repository README, component documentation, license, and maintenance metadata. Capture, retrieval, and browsing form a complete local memory workflow; The installer configures the required hooks. The main trade-offs are also clear: Session data enters a local database and needs retention and backup rules; A global npm package install provides the SDK but not the full plugin setup. No local installation or functional test was claimed during cataloging.

Why it may be useful

  • Capture, retrieval, and browsing form a complete local memory workflow
  • The installer configures the required hooks

What to know first

  • Session data enters a local database and needs retention and backup rules
  • A global npm package install provides the SDK but not the full plugin setup
06

README

Claude-Mem


Overview

A hook-based memory plugin that records coding sessions and recalls relevant context through a local worker, database, and search interface. A hook-based memory plugin that records coding sessions and recalls relevant context through a local worker, database, and search interface.

Getting started

  • Set up Claude-Mem from its public GitHub instructions, keep the initial permission scope small, and verify it with a low-risk task before regular use.
  • The repository describes Claude-Mem as a hook-based memory plugin that records coding sessions and recalls relevant context through a local worker, database, and search interface.
  • Its main capabilities include store coding sessions, retrieve past context, restore project memory across tasks, browse memories locally. The documented facts include automatic session capture, local worker and database, search interface, claude code plugin installation.
  • Restart or reload the target agent, confirm that Claude-Mem appears in its installed extensions or skills, and run the smallest documented example before using it on important work.

Configuration

npx claude-mem install
Read the complete README on GitHub