Claude on WholeTech network
home/products/memory
Persistent context

Memory shipping

Persistent, file-based context that lets Claude remember facts about you and your work across conversations.

01 — How it works

Just files.

Memory is a folder of human-readable Markdown notes under ~/.claude/projects/<dir>/memory/. An index file (MEMORY.md) is loaded into every conversation; individual memory files are pulled in when relevant. You can read, edit, and version-control everything by hand.

02 — Four kinds of memory

Save the right things.

User

Role, goals, responsibilities, expertise. "Senior Go engineer, new to React."

Feedback

How to approach work — corrections AND validations. "Don't mock the database in tests; we got burned."

Project

Active state — who's doing what, why, by when. Decays fast; refresh often.

Reference

Pointers to external systems. "Pipeline bugs are tracked in Linear project INGEST."

03 — What NOT to save

Memory ≠ documentation.

04 — Hygiene

Keep it from rotting.

Treat memory as a living scrapbook. Read it like a colleague's note: useful, but old notes have expired details.
05 — Memory in apps you build

Bring it to the SDK.

The Agent SDK exposes the same memory primitives. Hand it a memory directory; it reads on start, writes throughout the run. Useful for long-running agents that revisit the same projects across sessions.