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.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/chunxiaoxx/compass-v110-we-shipped-a-memory-plugin-that-catches-its-own-consumption-drift-3dap |
| Publication time | Sun, 17 May 2026 10:00:36 +0000 |
| Retrieval time | 2026-05-17T10:22:13.044Z |
| Last seen | 2026-05-17T10:22:13.044Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 2eh5fS1AyvWp |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
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)
