Analysis updated 2026-05-18
Monitor an AI agent's memory for stale or contradictory facts.
Compare a baseline run against a candidate run to catch memory regressions.
Replay an agent session step by step to find where a memory error was introduced.
| kedarvartak/memops | 0xhassaan/nn-from-scratch | 3ks/embedoc | |
|---|---|---|---|
| Stars | 0 | 0 | — |
| Language | Python | Python | Python |
| Last pushed | — | — | 2023-06-08 |
| Maintenance | — | — | Dormant |
| Setup difficulty | moderate | moderate | hard |
| Complexity | 3/5 | 4/5 | 1/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Currently built primarily around the Letta agent framework.
MemOps is a monitoring and debugging toolkit for AI agents that use persistent memory, the kind of memory that lets an AI remember facts across multiple conversations or sessions. The problem it addresses is that persistent-memory agents can degrade in subtle ways that ordinary infrastructure dashboards do not catch: the agent might return stale or contradictory facts, repeatedly store near-identical memories, or slow down as the memory layer grows. MemOps captures a stream of memory events from an agent, including writes, reads, and rewrites, stores them in a local SQLite database, and computes health metrics from those events. Metrics include churn rate, or how often memories are rewritten, duplicate rate, contradiction score, stale recall rate, empty retrieval rate, and average retrieval latency. These turn invisible memory failures into numbers you can inspect and threshold. The regression analysis feature lets you compare two runs, a known good baseline against a candidate run after a code or policy change, and get a delta report showing which metrics worsened. The tool can return a non-zero exit code, making it usable inside automated test pipelines and continuous integration workflows. Sessions can be replayed step by step to pinpoint exactly which turn introduced a contradiction or loaded a stale memory. A local dashboard surfaces session timelines and root cause hints. The project is currently command-line first and built primarily around the Letta agent framework, though its internal event architecture is designed to support other frameworks through adapters. It is written in Python 3.11 or later.
A monitoring and debugging toolkit that tracks health metrics for AI agents with persistent memory.
Mainly Python. The stack also includes Python, SQLite, Letta.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.