Memory is a feature that lets the Hatz remember helpful details about you and your conversations over time. Instead of starting fresh every chat, the AI can draw on what it has learned - your preferences, context, and past instructions - to give you more personalized and relevant responses.
What Memory does
Learns automatically. As you chat, the AI picks up on important details - like your role, preferences, or recurring topics - and saves them as short memories.
Personalizes responses. When a memory is relevant to your current conversation, the AI uses it to tailor its answers (without you having to repeat yourself).
Stays under your control. You can view, edit, add, or delete any memory at any time. Memory is never locked in - you decide what the AI keeps.
How to use Memory
In chat
When memory is enabled, a "Memory on" indicator appears at the bottom of the chat composer. The AI will automatically save relevant details from your conversations and recall them when useful.
You can turn memory off for a specific chat by clicking the memory indicator and selecting "Turn off for this chat". Your global preferences still apply to other chats.
You can turn memory back on in the same way.
AI Preferences
You can also toggle memory on or off globally from Workspace > AI Preferences. This controls whether the AI saves and uses memories across all new chats.
Memory on - the AI will save and recall memories in new conversations.
Memory off - the AI will not save or recall memories. Existing memories are preserved but unused.
Memories can be created in three ways:
1. Automatically, during chat
When memory is enabled, the AI passively extracts durable details from your conversations - preferences, your role, recurring topics, or instructions you give. Just chat naturally; the AI decides what's worth saving. It is selective and focuses on facts that would be useful across future conversations, not one-off remarks. - You can also instruct Hatz to create a memory with a simple prompt.
2. Manually, from the Memory page coming soon
Go to Workspace > Memory and click "Add memory" in the toolbar. A dialog lets you type a memory directly. Use this to:
Teach the AI something upfront without waiting for it to learn organically
Correct or supplement what it has already picked up
Seed context before starting a new project or workflow
3. Bulk import coming soon
To add many memories at once, click "Import" on the Memory page. It accepts a markdown list, and the AI drafts the import for you to review before anything is saved. This is ideal for migrating context from another tool or quickly onboarding the AI to a new domain.
Per-chat Memory controls
State | What it means |
Memory on | Memory is active for this chat. The AI may save and recall memories. |
Memory off (this chat) | Memory is disabled for this specific chat only. Other chats are unaffected. |
Memory off (global) | Memory is disabled across all chats. Enable it from AI Preferences or the chat indicator. |
Memory unavailable | Your organization has disabled memory. Contact your admin to change this policy. |
Organization controls (admins)
Admins can manage memory at the organization level:
Enable or disable memory for the entire organization via Organization Settings > Memory policy.
When memory is disabled by policy, individual users cannot override it - they will see "Memory unavailable" with a note that preferences are managed by their organization.
Limitations & troubleshooting
Memory Policy Management
Overview
Memory Policy Management allows administrators to control whether the AI memory feature is available across their organization. Memory enables the AI to recall information from past conversations to provide more personalized responses.
Administrators can disable memory at two levels: the MSP (parent organization) level or the individual tenant (company) level. When memory is disabled, the AI stops saving new memories and stops recalling existing ones.
How to disable memory (Primary Admin - MSP level)
Steps:
Navigate to Organization Settings at the MSP/global level.
Scroll to the Memory Policy card.
Toggle the Memory policy switch to off.
Click Save.
Expected results:
Memory is immediately locked for all tenants and all users under that MSP.
End users see: "Memory unavailable - Memory preferences are managed by your organization." They cannot override this setting.
Client Admins at the tenant level see: "Memory is locked because parent policy is disabled." Their toggle is grayed out and cannot be changed.
Existing memories are preserved but will not be recalled by the AI.
No new memories will be saved.
How to disable memory (Client Admin - tenant level)
Steps:
Navigate to Organization Settings at the tenant level.
Scroll to the Memory Policy card.
Toggle the Memory policy switch to off.
Click Save.
Expected results:
Memory is disabled for all users within your tenant.
MSP users see: "Memory unavailable - Memory preferences are managed by your organization."
Existing memories are preserved but will not be recalled by the AI.
No new memories will be saved.
Troubleshooting
Issue: Client Admin cannot enable memory for their tenant.
Solution: Check if the Primary Admin has disabled memory at the MSP level. The Client Admin's toggle will be grayed out with the message: "Memory is locked because parent policy is disabled." Contact your Primary Admin to re-enable memory at the MSP level first.
Issue: End users report they cannot turn memory on.
Solution: Memory has been disabled at the organization level (MSP or tenant). End users will see: "Memory unavailable - Memory preferences are managed by your organization." Check your organization's memory policy settings or contact your administrator.
Scope restrictions:
Client Admins cannot override MSP policy. If a Primary Admin disables memory at the MSP level, Client Admins cannot re-enable it for their tenant. The system explicitly prevents enabling tenant memory when the MSP memory policy is disabled.
Client Admins can only manage their own tenant.
Primary Admins control the entire chain. When the MSP disables memory, all tenants and users are immediately affected regardless of their individual settings.
Memory behavior when disabled:
Existing memories are preserved using a soft-delete model but are not recalled by the AI.
The AI stops saving new memories immediately.
Users cannot override organizational policy. Individual user preferences and chat-level toggles have no effect when memory is disabled at a higher level.
No selective re-enablement:
When memory is disabled at the MSP level, there is no way to enable it for specific "exception" tenants. It applies universally to all child organizations.
Common questions
"Why didn't the AI remember something I said?"
Memory extraction is selective - the AI saves durable, reusable details, not every statement. If something important was missed, add it manually on the Memory page.
"I turned off memory but the AI still seems personalized."
The AI may still use context from the current chat session. Memory controls affect long-term recall across conversations, not within a single conversation.
"Memory unavailable" and I can't turn it on.
Your organization has disabled memory via policy. Contact your admin.
Good to know
Memories are per-user - they are not shared with other people in your organization.
Deleting a memory removes it permanently. The AI will no longer recall it.
Download links and file outputs are not stored as memories - memory is for preferences, context, and facts.