Memory Bank
Use Working Brief and Memory Packs for durable context
Memory in Claw is designed for continuity. It separates active working state from durable long-term context so you can keep sessions focused without losing important decisions.
Two memory layers
- Working Brief: live structured state for current work
- Memory Bank: durable memory packs with revision history
Use Working Brief for in-progress context. Save stable facts and decisions into Memory Bank.
What belongs in durable memory
Good candidates include:
- Project constraints and conventions
- Confirmed architecture decisions
- Stable API assumptions
- Team workflow preferences
Avoid dumping full transcripts when a concise summary captures the real value.
Memory Pack operations
You can:
- Create packs
- Rename and retag
- Search across packs
- Clone, archive, restore, and delete
- Import and export packs
- Browse revisions
Attachments and scope
Packs can be attached to multiple owners:
- Conversations
- Bots
- Playbooks
- Scheduled jobs
Archived packs must be restored before they can be attached.
Working Brief reconciliation
Claw continuously reconciles chat state into Working Brief. Use that as staging, then promote important context into Memory Bank.
Dedicated memory model
In Settings > Memory, you can set a dedicated model for memory workflows instead of using active chat model settings.
This is useful when you want:
- Lower cost memory operations
- More consistent summarization behavior
- Separate tuning for memory vs execution
Maintenance routine
- Keep titles specific and searchable
- Use focused tags
- Periodically prune stale packs
- Review revisions before major workflow changes