RecallOps: open-source incident-response agent uses persistent memory to recall failed fixes
suhas2228 · reddit · 2026-09-28
The author open-sourced RecallOps (MIT license) to solve a concrete pain point in LLM-based incident response: without persistent memory, a model can reason about symptoms but not know which fixes worked or failed in similar past incidents.
- Architecture: Hindsight serves as the memory layer; the flow is receive context → recall relevant historical incidents (combining semantic, keyword, graph, and temporal retrieval) → synthesize via Hindsight reflection → separate facts from hypotheses → flag historically failed remediations → require human approval before production changes → retain verified outcomes for future use.
- Example: a Payment Service incident with HTTP 503s, Hikari pool exhaustion, high PostgreSQL CPU, and downstream FraudCheck latency. One historical fix (larger connection pool) worked; a similar one failed when downstream latency was the real bottleneck — raising the key question of how an agent should remember the conditions under which a remediation succeeded or failed.
- Author seeks feedback on representing failed fixes as memory, contradictory evidence, fact/hypothesis separation, retention policy, and mandatory human-approval points.
More from coding & agent
- Google Research open-sources PaperOrchestra, a multi-agent framework for writing AI papers — google-research · 2026-11-16
- ffmpeg-skill gives coding agents local video editing via 42 FFmpeg tools and MCP — kajisho5 · 2026-11-16
- Agents Now Reply to Slack Messages on Their Own, Resolving a Prod Incident Ghost-to-Ghost — iamrobotbear · 2026-11-16
- Engineer's Interview Prep Method: Use Claude to Find Which Answers Undersell Your AI Work — brandon_galang · 2026-11-16
- DeepSeek open-sources its app frontend "chat-demo", already at 3.9k stars — NielsRogge · 2026-11-16
- lemire: AI's real impact on coding is expanding the engineer's 'cognitive radius', not speed — lemire · 2026-11-16