how-it-works

Explain how claude-mem captures observations and injects memory across sessions.

1|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/dwaynimay/IoTProject --skill how-it-works-dwaynimay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: how-it-works
Source: https://github.com/dwaynimay/IoTProject/tree/main/.agents/skills/how-it-works
Command: npx skills add https://github.com/dwaynimay/IoTProject --skill how-it-works-dwaynimay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly understand what claude-mem is doing behind the scenes, when it starts adding saved context to your prompts, and where that memory is stored.

Core Features & Use Cases

  • Observation capture from actions: Turns every Read, Edit, and Bash you run into compressed observations that are summarized at session end.
  • Context-aware memory injection: Automatically injects relevant past observations into future prompts so you don’t have to re-explain prior work.
  • Local-only storage: Keeps the SQLite database, vector index, logs, and settings in a local directory on your machine.

Quick Start

Ask: “How does claude-mem work, when does memory injection start, and where is the data stored?”

Frequently Asked Questions about how-it-works

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does memory injection work across coding sessions?

Memory injection works by capturing user actions like Read, Edit, and Bash as observations during a session. At session end, these are summarized and automatically injected into future prompts so you don't have to re-explain prior work.

When does context injection start when using claude-mem?

Context injection starts during your second session. The tool summarizes observations captured in the first session and automatically injects that relevant past context into your new prompts.

How are user actions turned into reusable session context?

User actions are turned into reusable context by capturing every Read, Edit, and Bash command, compressing them into observations, and then summarizing these observations at the end of the session for reuse.

Where is the local memory and session data stored on my machine?

Local memory and session data are stored in a local directory on your machine. This includes the SQLite database, vector index, logs, and settings used for context injection.

Does session summarization require cloud storage or external databases?

Session summarization does not require cloud storage. It keeps the SQLite database, vector index, logs, and settings entirely in a local-only storage directory on your machine.