Skip to lesson content
Claude-Mem/learn
Lesson 03 / 4 minute read

Let the builder build.

Imagine a workshop. One person repairs a chair. Another watches the useful steps and keeps field notes. Asking the builder to stop and write an essay after every movement would slow the repair down.

Source book by 递归客 (diguike) · Full attribution

A winding stream of paper is distilled into a neat stack of orange cards.
Meet the quiet note-taker working beside the main agent.

Notice the event, then keep moving

A hook is a small action triggered at a particular moment: a session begins, a prompt arrives, or a supported tool finishes its work. In the book’s Claude-Mem architecture, hooks connect the agent’s activity to the memory system.

The fast part captures the event and hands it off. The slower part happens in a background worker, a separate service that organizes pending work and asks an observer model to extract useful observations. Like a notebook beside the workbench, it supports the main task without asking the main agent to narrate every detail.

Try the idea

Follow one event into memory

  1. 1CaptureNotice the work
  2. 2DistillKeep its meaning
  3. 3StorePut it away
  4. 4RecallBring it back
The notebook is empty. Begin with one useful event.

Fictional example. This experiment runs locally and does not call an AI or access your memory.

The queue is a tray, not the archive

A queue holds activity waiting to be processed. An item in that tray is not yet a finished memory. Processing can fail, be delayed, or produce no useful observation. A dependable system needs to track that difference and recover unfinished work.

Several events can describe one discovery. Seeing their surrounding context helps the note-taker understand why a change happened. The observer still needs to avoid inventing reasons that the evidence does not support.

Keep the workshop usable

The book emphasizes separating memory work from the primary workflow. A broken memory service should not make the builder’s tools unusable. Fast handoffs, health checks, and orderly shutdowns all serve that practical goal.

This is a description of the book’s design, which examines Claude-Mem v12.6.2. Exact hooks, providers, and implementation details evolve. Follow the source links for that version’s machinery rather than treating this toy demonstration as a live capture service.

Go deeper with the author

Behind this lesson

Related chapters in 递归客’s original book:

The source examines Claude-Mem v12.6.2. Links are pinned to the book revision used for this course; current implementation details may differ.