Bug Description
Environment:
- MemOS version: v2 (latest)
- Deployment: hermes-agent plugin mode
- Node.js process running normally
Problem:
Web UI shows Memory count: 500 but database has 1400+ traces. The number stays fixed at 500 regardless of actual trace count growth.
Expected behavior:
Memory count should reflect actual trace count in database (~1422), not a fixed cap of 500.
Steps to reproduce:
- Use hermes-agent with MemOS normally
- Observe Web UI number after extended use
- Number stops at 500 while database trace_count exceeds 1400
Initial analysis:
Suspect issue in metrics().total calculation logic, or frontend applying a hard cap on totalCount. Database query for trace count is accurate - problem is in presentation layer.
Impact:
Cannot accurately monitor memory system storage via Web UI.
Bug Description
Environment:
Problem:
Web UI shows Memory count: 500 but database has 1400+ traces. The number stays fixed at 500 regardless of actual trace count growth.
Expected behavior:
Memory count should reflect actual trace count in database (~1422), not a fixed cap of 500.
Steps to reproduce:
Initial analysis:
Suspect issue in metrics().total calculation logic, or frontend applying a hard cap on totalCount. Database query for trace count is accurate - problem is in presentation layer.
Impact:
Cannot accurately monitor memory system storage via Web UI.