Persistent Memory
Anyy separates durable personal context from conversation history. This lets it remember stable preferences and commitments without treating every chat message as permanent truth.
What Belongs in Memory
Good memory candidates are facts that should change future answers:
- preferred language, tone, units, or working style;
- durable personal preferences and corrections;
- ongoing relationships, commitments, and decisions; and
- stable context that applies across sessions.
Temporary task progress, copied reference material, secrets, and one-off instructions do not belong in persistent memory.
“Remember that I prefer release notes as a short checklist” is more useful than an isolated fragment. A clear, durable statement is easier to apply and later correct.
Two Memory Targets
Anyy maintains two editable sources:
| Target | Purpose |
|---|---|
user | User profile facts and preferences (USER.md) |
memory | Durable facts, decisions, relationships, and commitments (MEMORY.md) |
These are ordinary Markdown files in the Profile home’s memory/ directory and are the canonical memory. There is no separate vector-memory store or automatic consolidation process.
The assistant can add, replace, or remove a Markdown block. When adding, it skips exact duplicate entries. Replacement and removal require a short unique match so Anyy does not silently alter the wrong fact.
Teach Anyy from Chat
Use ordinary language:
Remember that I prefer temperatures in Celsius.
Replace my old weekly review time with Friday at 16:00.
Forget the note that I am evaluating Provider A.
Ask Anyy to confirm what changed when the distinction matters. Memory writes are audited, and unsafe generated content is blocked or redacted before persistence.
Review and Edit
Open Dashboard → Memory to inspect the current User and Memory sources. Use the Dashboard editor for deliberate maintenance, or ask Anyy to correct a specific entry in chat.
See Dashboard Memory for the visual workflow.
How memory enters a conversation
USER.md holds person-side context. Anyy includes its exact contents when creating a session with a private-compatible audience and pins that version for the session. It omits User context when the audience is not suitable. After editing USER.md, start a new private session to check the change; continuing the old one keeps its original version.
MEMORY.md is selected for each run. Anyy considers blocks under a level-two ## Pinned heading first, then ordinary blocks that match the current question, within the memory context budget. A new level-one or level-two heading ends the pinned section. Blocks are included whole or omitted; saving a fact does not guarantee it appears in every model request.
For example, a short convention you need across topics can be placed under:
## Pinned
Release notes should be a short checklist.
## Projects
The travel plan is still provisional.
Keep pinned content small. Budget limits still apply, and ordinary unselected blocks remain in the saved file. Durable session history and Pi’s execution storage are conversation records, not substitutes for these memory files.
Memory vs. Session Search
Memory is curated durable context. Session Search looks through earlier conversations. If you want to recall what was discussed, search sessions; if you want a stable fact applied in future sessions, save it to memory.
Privacy Guidance
- Do not store passwords, API keys, recovery codes, or private keys.
- Remove facts that are no longer correct instead of appending conflicting versions.
- Keep collected documents in the Workspace, not in the user profile memory.
- Review memory after sharing an account or restoring a backup.
Troubleshooting
| Problem | What to check |
|---|---|
| Anyy does not use a preference | Confirm the entry in Dashboard → Memory; start a new private session for a changed USER.md preference, or ask specifically about a MEMORY.md fact |
| A correction creates a conflict | Replace or remove the older entry instead of adding another version |
| A request is rejected | Remove secret-like or unsafe generated content and retry with a durable fact only |
| You need a past discussion | Use session search rather than adding the transcript to memory |