Elliotoh-jin

Claude Memory Loop — Development skill for Claude Code

Development community

Claude forgets everything between sessions.

How to install Claude Memory Loop

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Elliotoh-jin/claude-memory-loop and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Claude Memory Loop does

Claude forgets everything between sessions. This skill installs the fix: a memory loop for Claude Code — one small BRIEF.md every session reads first, fed by a battle-tested capture discipline.

Alternatives in Development

Battle — Head-to-head graded battle card between two sites — eight dimensions, bar-by-bar, verdict line 3.6k ★
Axiom — Battle-tested Claude Code skills for modern xOS (iOS, iPadOS, watchOS, tvOS) development with 13 production-re 2.6k ★
Portaljs Add Chart — Add a chart (line, bar, area, pie, or scatter) to a dataset's showcase in a PortalJS portal 2.3k ★

README

claude-memory-loop

**A memory loop for Claude Code: one small file that every session reads first, on every surface — fed by a capture discipline whose every rule was paid for by a real failure.**

The problem

Every Claude session starts empty. Your chat sessions, CLI sessions, cloud sandboxes, and other agents don't share what they learned. Your notes vault is too big to re-read at session start — and an AI that "just reads everything" quietly trusts stale dates and re-does investigations a previous session already closed.

Bigger context windows don't fix this. What fixes it is the same thing that fixes it in hardware: **memory tiering**.

Tier	In hardware	Here	Property
Hot	HBM	Session context	Fast, rich, gone when the session ends
Warm	flash cache	`BRIEF.md`	Small, capped, always read first, shared by every surface
Cold	SSD	Your full repo/vault	Big, canonical, read on demand via pointers

The git repo is the only storage that crosses every surface boundary — local CLI, cloud sessions, chat (read-only via the GitHub MCP connector), and any other agent you run. So the warm layer lives in the repo.

The loop

  capture (6 types, 1 line each)          open decisions & deadlines
  memory/capture-log.md          ◀──────▶ open-loops.md
            │                                   │
            ▼                                   ▼
        BRIEF.md  ◀── tools/build_brief.py (caps + expiry + budget)
            │
            ▼
  every session reads it FIRST (SessionStart hook)
            │
            ▼
  human judges → promotions to your canon (human gate)
            │
            └── new judgments become new captures — the loop closes

Plus a **Stop hook**: on days a session produced real output, it asks for a short *session card* — what was done, **what was ruled out and why**, what assumptions it stands on. That's the part that normally evaporates, and it's what saves the next