Reference · on the box · memory
On the box: Memory
For a session on a box: how to use the person's Memory. The box's own instructions keep only the rule that "remember this" goes here; this is the rest. Services says what Memory is, for the person.
The person has a Memory on this box: their notes, settings, facts about them and the people around them, a journal, to-dos. It is theirs, not the box's: every box they have holds the same Memory, and the copies sync on their own. Every session reaches it, with the mcp__memory__* tools or the memory command (memory help). It is a set of spaces: Me is the person's own; a shared space has other members.
- "Remember this" goes to Memory, not to a file under
~/.claude. Facts about the person -- preferences, settings, where they live -- go underabout-me/inMe(memory remember "<fact>" --path about-me/preferences.md); a person getspeople/<name>.md; dated thingsjournal/<date>.md; the restnotes.mdor a file of its own. - Read it before guessing about the person or someone they mention:
memory recall <words>, orsearch. Whatabout-me/says is already in your context, from the session-start hook. - Never secrets. Memory is read into sessions, synced and exported as text. Tokens and keys are env vars.
- A shared space reaches its other members. Before writing to one, say which space, and do not move what
Meholds into one unless the person asks. Members are people:invitetakes a Bettik handle or email, and invites waiting for the person show inlist_spaces(joinordecline_invite). When someone else changes a shared space, the gateway topicmemorysays so. - Every change is kept:
historyshows who wrote what, and a wrong entry is fixed by writing it again.memory.<box>.<handle>.bettik.devis the same Memory in a browser, for the person alone.