Persistent Memory

Anyy separates durable personal context from conversation history. Memory survives individual sessions and is shared by every Role in the selected Profile.

The Two Memory Files

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

Role identity belongs in Soul. Conversation-specific material can remain in its session unless it should affect future sessions.

What Belongs in Memory

Good candidates are:

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

Avoid secrets, temporary task instructions, copied transcripts, unconfirmed guesses, and facts that belong only to another person or Profile. Qualify time-sensitive context, for example: Considering a move to Tokyo as of 2026-08; no decision yet.

Say why the fact matters

“Remember that I prefer release notes as a short checklist” is more useful than an isolated fragment. A complete statement is easier to apply and later correct.

How Proactive Saving Works

Anyy does not wait only for the exact word “remember.” During an ordinary foreground model run, it can choose the memory tool when the conversation contains a clear, confirmed fact or preference that should remain useful in later sessions.

The model selects the target by meaning:

• target=user writes to USER.md for stable information about the person, such as language, timezone, accessibility needs, or communication preferences;
• target=memory writes to MEMORY.md for durable facts, decisions, relationships, projects, and commitments that should inform later work.

This is selective, not a transcript recorder. Mentioning personal information does not guarantee it will be saved, and temporary instructions, guesses, secrets, or copied documents should not become memory. Collected resource or document content is rejected from USER.md.

The write happens inside the foreground run; Anyy does not launch a separate scheduled memory pass after every fixed number of turns. A successful write is audited but does not show a separate approval prompt. Review consequential facts in Dashboard and correct or remove them there or through Chat.

A request can change behavior without changing memory

A current instruction may override a stored preference for that request. It does not update the saved files unless the memory tool actually succeeds or you save an edit in Dashboard.

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.

Anyy can add, replace, or remove an entry, whether you asked explicitly or it proactively identified a durable fact. Exact duplicates are skipped when adding. Replacement and removal require a short unique match so the wrong fact is not silently changed.

Ask Anyy to confirm the result when the distinction matters. Memory writes are audited, and unsafe generated content is blocked or redacted before persistence.

For consequential facts, verify the saved file in Dashboard. A request to “remember” is not proof that persistence succeeded.

Review Memory in Dashboard

Open Dashboard → Memory. The page previews each file and shows its size and last update when content exists.

Select USER.md or MEMORY.md to inspect:

• rendered Markdown;
• entry count;
• file path; and
• the complete editable source.

Use Dashboard for deliberate maintenance, and Chat for specific corrections in context.

Edit a Memory File

1. Open the file.
2. Select Edit.
3. Update the Markdown.
4. Review the complete document.
5. Save.

Dashboard replaces the complete file. It uses the version you opened as a concurrency check; if the file changed meanwhile, Anyy reports a conflict instead of overwriting newer content.

When a conflict occurs, preserve any unsaved text you need, reload the current file, merge deliberately, and save again.

Dashboard accepts non-empty content and does not provide a clear-or-delete action for either memory file. Remove an unwanted entry by saving a revised complete document.

Memory affects future conversations

Incorrect or overly broad statements can influence every later session in the Profile. Review consequential edits and remove superseded facts instead of appending contradictions.

Scope

• Every Role in one Profile shares its memory.
• Sessions in another Profile do not.
• Switching Roles does not switch memory.
• Archiving a Role does not delete memory.

Create another Profile when two personal contexts must stay independent.

Memory versus Session Search

Memory is curated durable context. Session Search looks through earlier conversations. Search sessions to recall what was discussed; save a fact to memory when it should shape future conversations.

Privacy Guidance

• Never store passwords, API keys, recovery codes, or private keys.
• Keep collected documents in the Workspace, not in personal memory.
• Remove stale information instead of adding a conflicting version.
• Review memory after sharing an account or restoring a backup.

Maintenance Tips

• Keep one fact or decision per bullet so it can be corrected precisely.
• Use headings for stable areas such as preferences, projects, and accessibility.
• Review both files after a major life or project change.
• Remove superseded information instead of accumulating contradictory history.

Troubleshooting

Problem	Fix
Anyy does not use a preference	Confirm that the correct Profile and file contain an unambiguous entry
A save reports a conflict	Preserve your draft, reload, merge with the current file, and save again
A correction creates a contradiction	Replace or remove the older entry instead of adding another version
A Role cannot see expected memory	Verify that the Role belongs to the same Profile
Old information still affects answers	Remove the stale entry, then start a new session
You need a past discussion	Use Session Search instead of copying the transcript into memory
Memory appears empty	Confirm the selected Profile, then open both USER.md and MEMORY.md
Personal information was not saved	State that it should be remembered and why it remains useful, then verify the correct file
Something was saved that should not persist	Ask Anyy to remove the unique entry or edit the complete file in Dashboard