Skip to content

Claude-Mem in production

70 days of work. One searchable memory.

Alessandro ran Claude-Mem across three machines. As he built, debugged and shipped, his agents captured 22,718 observations. A fresh session could look up what the last one learned.

Claude-Mem’s mascot files a project note in a shared card catalogue connected to three computers.
Alessandro’s field studyMarch–May 2026
Observations captured
22,718
Bug fixes recorded
1,262
Decisions saved
757
Machines in the fleet
3

Inside the deployment

What it takes to remember the work.

Follow a coding decision from the session where it happened to the machine where another agent needs it.

From the incident log

Ask a question a commit can’t answer.

Alessandro published the investigation behind a broken search adapter. It’s the kind of decision a future agent can put straight back to work.

Why did search go quiet after the migration?

The worker was still calling the old Chroma method after the fleet moved to Qdrant. New observations kept saving. The searches returned empty.

What did the operator change?

He repaired the adapter, translated filters for the new backend and gave the embedding service enough time to start. The fleet later completed its full reindex with zero reported errors.

Read the reliability chapter

Claude-Mem

Give your next session a head start.

We capture the decisions and fixes while you build. CMEM Pro puts that memory within reach of your connected tools.