Problem Statement
The platform has a mature memory subsystem (SimpleMemory, FileMemory, BlackboardMemory) with embedding-based retrieval (FAISS + cosine similarity), chunked embeddings, and JSON persistence via memory_path. However, there is zero visibility into memory state from the frontend.
What Changes
- REST API endpoints to list memory stores and items (from active sessions and persisted files)
- WebSocket
memory_updated event with callback hook on MemoryManager
- Frontend Memory Timeline page with store selector, chronological item list, and live mode
- Sidebar navigation entry and route registration
Problem Statement
The platform has a mature memory subsystem (
SimpleMemory,FileMemory,BlackboardMemory) with embedding-based retrieval (FAISS + cosine similarity), chunked embeddings, and JSON persistence viamemory_path. However, there is zero visibility into memory state from the frontend.What Changes
memory_updatedevent with callback hook onMemoryManager