Yes, but not every chat is permanently saved as a "memory." By default, WorkBuddy extracts preferences, facts, relationships, and pending items from the conversation history, organizing them into a memory summary every night, with subsequent tasks only referencing content related to the current request. Users can view, edit, delete, or close memories, and this compilation does not consume additional points.
Memories and chat records are not the same thing
Chat records preserve specific conversations, while memory is reusable information summarized from history by the model, such as common writing styles, job roles, or ongoing follow-up matters. Because it is automatic generalization, it may omit conditions or confuse timeliness. When it involves contracts, amounts, contacts, or project status, it cannot be directly used as a factual basis and should be verified back to the original data.
How to correct it if you find a mistake
- From the avatar, go to "Settings — Memory" and open the current memory summary.
- Click Edit and tell WorkBuddy through conversation which items need correction, addition, or forgetting of them.
- If a certain content should not be kept, use the delete entry to clear it; You can also disable the memory function with one click.
You can also paste usage habits organized from other AIs into the import portal, but before importing, account credentials, customer privacy, and invalid personal information should be deleted.
What will happen to the previous content after it is closed?
Closing memories will stop retrieving from new sessions; Deleted entries will no longer be used for subsequent tasks. However, responses that have already been generated will not be automatically reverted when closed or deleted. If an old conversation contains sensitive information, you must separately check the conversation history and the exported file; you cannot only process the memory summary.
Which content is not suitable for memory
Passwords, API Keys, IDs, unauthorized customer personal information, constantly changing quotes, and one-time verification codes should not be stored as long-term preferences. After using on a shared computer, exit the account; Obtain authorization first when the session involves information about others. A safer approach is to keep only the memory of stable preferences, place important business facts in a controlled knowledge base or project file, and reconfirm before critical decisions.
