Compass v1.1.0 · we shipped a memory plugin that catches its own consumption drift
Compass released version 1.1.0 to address a critical issue where agents recalled memory files but failed to consume their content, leading to operational errors. The update introduces three core improvements: embedding file body content in recall results, enriching anti-drift alerts with past lesson details, and detecting when recalled files are not read. These changes aim to close the gap between memory recall and actual usage in agent workflows.
- ▪Compass v1.1.0 was released 12 hours after v1.0.0 to fix a recall-consumption disconnect observed in production.
- ▪The bug occurred when an agent recalled a memory file's title and description but did not read its body, causing it to skip critical steps in a publishing pipeline.
- ▪The fix includes embedding memory file bodies in top recall results, enriching drift alerts with actionable context, and adding a module to detect when recalled files are not consumed.
- ▪A new module, recall_consumption.py, checks for missing Read tool calls after recall events to identify consumption drift.
- ▪The update ensures agents have full context from memory files without requiring additional tool calls, reducing the risk of procedural errors.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3855870) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } chunxiaoxx Posted on May 17 Compass v1.1.0 · we shipped a memory plugin that catches its own consumption drift #llm #memory #mcp #agents Compass v1.1.0 · the recall consumption fix We shipped nautilus-compass v1.1.0 12 hours after v1.0.0. v1.0.0 was the public stable cut. v1.1.0 fixes a class of failure that v1.0.0 surfaces but does not catch · which we caught in our own usage 5 hours after launch.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
