Memory Configuration
Configure how your WorkClaw Claw retains and recalls information across conversations. Set retention policies, manage memory entries, and control what your agent remembers.
What is Claw memory?
Claw memory is the system that lets an agent retain information across separate conversations. Without memory, each conversation starts from scratch. With memory enabled, a Claw can recall preferences, past decisions, project context, and any facts it has been asked to remember.
How do I enable memory?
Open the Claw's Settings > Memory panel. Toggle Long-Term Memory on. Once enabled, the Claw automatically extracts and stores key facts from conversations. You can also manually add memory entries from this panel by clicking Add Memory.
What does the Claw remember automatically?
When long-term memory is enabled, the Claw looks for information worth retaining — names, preferences, project details, decisions, and recurring requests. It does not store entire conversations verbatim. Instead, it distills facts into concise memory entries that it can retrieve when relevant.
You can influence what gets remembered by being explicit in conversation: "Remember that our fiscal year starts in April" or "Don't remember anything from this conversation."
How do I manage memory entries?
The Memory panel shows all stored entries with timestamps. From here you can:
- View any entry to see what was stored and when
- Edit an entry to correct or update information
- Delete an entry the Claw should no longer recall
- Search entries by keyword to find specific facts
What are retention policies?
Retention policies control how long memory entries are kept. You can set a global retention period (e.g., 90 days) after which entries are automatically deleted. You can also mark individual entries as permanent so they survive retention sweeps. Configure retention under Settings > Memory > Retention Policy.
Does memory affect performance?
A Claw with a large memory store may take slightly longer to respond as it searches for relevant entries. In practice, this overhead is minimal. If you notice slowdowns, review the memory panel and remove outdated or redundant entries. Keeping memory clean and relevant produces the best results.
Is memory shared across the team?
Each Claw has its own memory. Information remembered by one Claw is not automatically available to another. If you need shared knowledge across multiple Claws, document it in a workspace file or add it to the operating instructions so every Claw has access.