Feature: Memory Timeline Visualization
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 34.3k
- Forks
- 4.3k
- PR merge metrics
- No merged PRs in 30d
Description
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_updatedevent with callback hook onMemoryManager - Frontend Memory Timeline page with store selector, chronological item list, and live mode
- Sidebar navigation entry and route registration
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing MemoryManager, the existing REST and WebSocket entry points, and the frontend route and sidebar registration. Map active and persisted memory stores before defining the timeline page and update event. Done means stores and items are available through the API, updates can trigger the WebSocket event, and the frontend provides selection, chronological display, and live mode.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, frontend, full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100