Back to Vault
Agent Memory
Tier 3
Octopus_mem
Summary
An agent memory system built on a skill + memory index architecture following a radical-minimalism principle ('jsonl, md, at most sqlite'), with a dual-repo split: open framework, private data.
Key Takeaways
- A memory index file loaded every session is the core mechanism
- Minimal formats (jsonl/md/sqlite) keep memory inspectable
- Framework-public, data-private is a clean split
Reliability Note
Community project (original text in Chinese); the index-file pattern is the takeaway.
Flows informed by this source
2Memory & Context
Design a Memory Index Loaded Every Session
Build the pattern behind minimalist memory systems: a compact index file the agent always loads, pointing to detail files it loads on demand.
01Structure the index and details
02Wire loading: index always, details on demand
03Maintain the index as memory evolves
Best forbuilders who have shipped a basic app before
3 steps60-90 minutesIntermediate
Memory & Context
Add File-Based Persistent Memory
Give your agent durable memory with plain files - the radical-minimalism approach production practitioners keep converging on.
01Design the memory file structure
02Load memory at session start
03Build the guarded memory_update tool
+1 more steps to Done
Best foryour first pass at this - no prior setup assumed
4 steps45-75 minutesBeginner