Main
Treat memory as infrastructure: log durable actions and outcomes, not just chat transcripts, so you can replay decisions later.
Start by capturing one narrow signal (tool calls, file writes, or task outcomes), then expand once you can query and summarize it reliably.
When debugging agents, memory traces help you answer “what happened” with timestamps and artifacts instead of vibes.
Source-backed notes
- README tagline emphasizes memory from what agents do, not just what they say.
- README links both PyPI (
memori) and npm (@memorilabs/memori) packages. - Repo license file is Apache License 2.0.
FAQ
- Is it framework-specific?: No—README describes it as framework and datastore agnostic.
- Is there a hosted option?: Yes—README links to Memori Cloud documentation.
- Do I have to store private data?: No. You control what events are captured and where they are stored.