Memory Loop

English | 简体中文

*The agent forgets. The repo doesn't.*

Installation

Run these two commands in Claude Code:

Select Install for you (user scope), then restart Claude Code.

Background

Loop Engineering by Addy Osmani describes a shift in how we work with coding agents:
*"You shouldn't be prompting coding agents anymore. You should be designing loops that prompt your agents."*

A loop needs five building blocks — automations, worktrees, skills, connectors, and sub-agents — plus one place to remember stuff:
*"A markdown file, or a Linear board, anything that lives outside the single conversation and holds what's done and what is next... the model forgets everything between runs so the memory has to be on disk and not in the context. The agent forgets, the repo doesn't."*

memory-loop is that sixth piece, built as a Claude Code plugin. Install it once, and every project you open gets a persistent, structured memory that loads automatically at session start and updates as you work.

How it works

Files created in your project
Tip: Commit these files to share memory with your team, or add .claude/memory/ to .gitignore to keep them local.

Installation

One command. Works across all your projects.

That's it. The plugin activates on the next Claude Code session.

Scope options

Quickstart: what happens after installation

Step 1 — Open any project in Claude Code

The plugin fires automatically on session start. No manual setup needed.

Step 2 — Work normally. When you finish a task, save.

The agent reviews what happened in the session and writes structured entries:

Step 3 — Next session, memory is already there

Open the project again. The session start hook automatically injects everything the agent learned last time. No prompting needed.

Step 4 — Check health, compress…