Memory

Anyy keeps durable personal context in two Markdown files inside the selected Profile. Memory survives individual sessions and is shared by the Roles in that Profile. How a file enters a conversation depends on its purpose and the conversation audience.

The two memory files

File	Purpose	Good examples
USER.md	Stable facts and preferences about the person using this Profile	preferred language, accessibility needs, timezone, communication preferences
MEMORY.md	Durable working context the assistant should retain	ongoing projects, recurring decisions, useful conventions, unresolved follow-ups

Role identity belongs in Soul, not in these files. Conversation-specific details can stay in the session unless they will matter later.

View memory

Open Dashboard → Memory. The page shows a preview of each file, its size, and its last update when content exists.

Select USER.md or MEMORY.md to see its rendered Markdown, entry count, size, update time, and editor. The files are stored under memory/ in the selected Profile home.

Edit memory

1. Open the file you want to change.
2. Select Edit.
3. Update the Markdown.
4. Review the whole file, then save.

Dashboard replaces the complete file when you save. It uses the version you opened as a concurrency check. If the file changed in the meantime, Anyy reports a conflict instead of silently overwriting the newer content.

When that happens, copy any unsaved text you need, reload the current file, merge the changes deliberately, and save again. If the conflict message supplies candidate and recovery paths, keep them until you have resolved the conflict.

Dashboard accepts non-empty content and does not provide a clear-or-delete action for either file. To replace an unwanted entry, edit the complete document and save the revised version.

Memory affects future conversations

Treat memory edits as changes to Anyy's durable context. Incorrect or overly broad statements can influence every later session in the Profile.

What to remember

Prefer information that is:

• useful beyond the current conversation;
• stated or confirmed by the user;
• unlikely to become stale immediately; and
• short enough to apply without interpretation.

Avoid:

• passwords, tokens, recovery codes, or private keys;
• temporary task instructions;
• guesses presented as facts;
• copied transcripts; and
• facts that belong only to another person or Profile.

Time-sensitive facts should include a date or qualification, for example: Considering a move to Tokyo as of 2026-08; no decision yet.

Memory during chat

Anyy can use its memory tools to update durable context during a conversation. You can also ask directly:

Remember that I prefer concise answers with commands first.

For consequential facts, confirm the result on Dashboard → Memory. A chat request is not proof that a write succeeded; the saved file is the source to inspect.

When changes affect chat

USER.md supplies person-side facts to a new session only when Anyy has established a private-compatible audience. The session keeps that exact version; editing the file does not replace the User context already pinned in an existing session. Start a new private conversation to verify a changed preference.

MEMORY.md is selected again for a run: matching entries and entries under a ## Pinned heading are considered within a context budget. An entry can remain saved without being included in every answer. Keep entries concise and ask about the relevant fact explicitly when checking it.

Scope and storage

Memory is Profile-scoped:

• all Roles in the Profile share it;
• sessions in another Profile do not;
• switching Roles does not switch memory; and
• deleting a Role does not delete memory.

Create another Profile when two contexts must remain independent.

Tips

• Keep one fact or decision per bullet.
• Remove superseded information instead of appending contradictions.
• Use headings for stable areas such as preferences, projects, and accessibility.
• Review memory after major life or project changes.
• Keep secrets in the credential system, never in Markdown memory.

Troubleshooting

Problem	Fix
A save reports a conflict	Reload, merge the current file with your draft, and save again
A Role cannot see expected memory	Verify that the Role is in the same Profile
Old information influences answers	Edit or remove the stale entry; start a new private session after changing USER.md
Memory appears empty	Check the selected Profile and open both files

See Roles for identity-specific Soul instructions.