{
  "source_file": "0930",
  "source_platform": "Dev.to",
  "author": "Edward Izgorodin",
  "title_listed": "The Feedback Dilemma: Your Agent's Memory Learns Most From a Signal It Almost Never Sends",
  "keywords": "",
  "domain": "大模型算法",
  "content_type": "深度技术解析",
  "is_paid_flag": "否",
  "url": "https://dev.to/izgorodin/the-feedback-dilemma-your-agents-memory-learns-most-from-a-signal-it-almost-never-sends-4akk",
  "publish_date": "2026-08-21",
  "corpus_stage": "",
  "notes": "",
  "id": "d768c08c0b62",
  "collected_at": "2026-10-02T14:03:34",
  "title": "The Feedback Dilemma: Your Agent's Memory Learns Most From a Signal It Almost Never Sends - DEV Community",
  "body_markdown": "An AI agent with learning memory should get better the more you use it. That is the promise everyone in this category makes, including us.\nIn practice, the mechanism designed to do the heaviest lifting is almost entirely absent from production traffic. Agents read memories constantly. They almost never report back on whether those memories helped.\nWe measured how wide that gap is in our own production store, and the numbers were worse than I expected.\nThe signal that carries the most weight\nIn a reinforcement-aware memory engine, associations strengthen through three kinds of events.\nA\nwrite\ncreates co-occurrence evidence: storing a memory links the concepts inside it. There is no outcome yet.\nA\nread\ncreates weak co-activation between the query and what came back. This signal is deliberately faint, an exploration signal damped so that merely retrieving something does not entrench it.\nFeedback\nreports outcome. It is the only channel that carries a result, and the result gates how much the association strengthens. Positive outcome amplifies, negative suppresses. This is a three-factor learning rule: co-activity alone is not enough, a third factor such as reward or surprise has to gate durable change (Frémaux and Gerstner,\nDOI:10.3389/fncir.2015.00085\n).\nOne property of that design made a production audit possible. Only feedback carries an outcome, and the recorded outcome polarity survives weight decay. So an edge with nonzero outcome polarity is a durable fingerprint that says: explicit feedback touched this one.\nWhat we found in production\nOur August 2026 measurement covered one engine, one production store, 359,388 concept-graph edges, and 65 tenants with at least 100 concepts each.\nOne of those tenants came from benchmark campaigns, where our harness calls the feedback endpoint between queries by design. The rest were live traffic. Same engine, two completely different shapes of memory.\nEdges touched by feedback:\nTenant\nEdges touched by feedback\nBenchmark\n94.8%\nMixed account\n66.1%\nBest live tenant\n12.8%\nRead-heavy live tenant\n0.6%\nBulk-ingest tenant\n0.0%\nAnd what that did to the graph:\nMetric\nBenchmark\nLive tenants, n=57\nEdges per concept\n22.0\n7.5\nShare surviving after cutting weak edges\n0.539\n0.107\nBenchmark-grown memory was about three times denser and roughly five times more resistant to dissolution when weak edges were cut. On the benchmark tenant, edges touched by feedback had a p90 weight of 0.261 against 0.002 for untouched edges, more than a hundredfold difference. The benchmark median edge was reinforced ten times. The live median edge was reinforced once.\nOne tenant made the attribution unusually clean. It looked live, but 71.4% of its 60,872 edges were born in a single four-day benchmark window. Removing those edges dropped its density and resilience straight into the middle of the live distribution. The effect tracked the regime, not the account.\nThe honest limit.\nWe measured a structural difference. We did\nnot\nmeasure whether more feedback causally improves retrieval quality for live users. \"Agents that give feedback get better memory\" remains a hypothesis with a suggestive structural result behind it, not a finished quality claim. I would rather say that plainly than let the tables imply more than they show.\nThis is not one engine's problem\nFeedback scarcity is an old finding wearing new clothes. Hu, Koren and Volinsky framed the asymmetry for recommender systems back in 2008: implicit signals are abundant, explicit ratings are scarce (\nDOI:10.1109/ICDM.2008.22\n). Nielsen's participation inequality describes the same 90-9-1 shape across online contribution (\nNN/g, 2006\n). The entire RLHF line exists because human feedback is expensive to collect (\nChristiano et al., arXiv:1706.03741\n).\nThe agent-memory category shows the same tension in product shape. Reading vendor documentation on 2026-08-12:\nMem0\ndocuments a per-memory feedback API and advises customers to track their own feedback completion rates, while publishing none.\nZep\nassigned fact ratings automatically against developer instructions rather than by end users, and listed them in its February 2026 deprecation wave.\nLetta\nexposes feedback on agent steps, not on memories.\nLangMem\ndocuments no memory feedback or rating API at all.\nChatGPT memory\noffers remember, forget and delete. No grading.\nAnthropic's memory tool\ngives the model six file-like commands and no rating command.\nAcross every surface I could check,\nno vendor publishes data on how often their feedback channels are actually used\n. The pattern is not \"vendors ship ratings and users ignore them.\" It is that explicit memory ratings are quietly not becoming standard, and at least one vendor is walking away from them.\nWhat silent failure looks like without a quality signal is visible in the open: a production audit filed in Mem0's tracker reported that 97.8% of 10,134 memory entries were junk (\nissue #4573\n).\nTwo builders ran the same kind of check on their own systems this week, after a conversation under the previous piece.\nGiulio D'Erme\ncounted his corpus and found zero of 152 memos and zero of 59 documents carrying a validity window or a supersession edge: fields the engine could read, and nothing was writing them.\nKen Alger\ntook the argument to the interface in\nYour Memory API Is Lying to Your Agent\n, which is worth reading next to this one. Availability is not usage, and it does not appear to matter much whether the unexercised thing is a schema field, a rating channel, or a relationship the response has nowhere to put.\nThree ways to fix it, and two of them are traps\nForce it.\nGate reads on a feedback call. Your completion metric goes to 100%. But the value of explicit feedback comes precisely from someone deciding an outcome was worth reporting; coerce it and the label degrades toward noise, while every read pays a round trip. Forced completion protects a dashboard and damages the signal.\nAsk for it.\nThumbs up, thumbs down, \"was this useful?\" This helps when a real human chooses to answer, and it does nothing about participation inequality. In agentic systems it is often worse, because the agent finishes the task without ever surfacing a rating moment to a person.\nPrescribe it.\nThis is the one that fits how agents actually work today, and the industry has already converged on the pattern for a neighbouring problem. Anthropic's memory tool auto-injects a memory protocol instruction when enabled. Claude Code loads project instructions every session. The official MCP knowledge-graph memory server ships a suggested system prompt prescribing proactive memory behaviour.\nAGENTS.md\nexists as a standing-instruction format used by tens of thousands of projects.\nSo the practical lever is a few lines in\nAGENTS.md\n,\nCLAUDE.md\n, or your system prompt that tell the agent when to report an outcome. Something as plain as: after acting on a recalled memory, report whether it helped.\nTwo caveats I owe you. No official Anthropic document prescribes\nrating\nmemories, because their tool has no rating command, so this extends the documented instruction pattern rather than following an established norm. And our own MCP server prescribes exactly this in its instructions, which makes it our practice rather than independent evidence.\nWhy I wrote this about our own product\nThe uncomfortable version of these numbers is that our strongest learning mechanism is the one our users almost never trigger. We could have shipped the benchmark column and left the live column out. The benchmark column is genuinely ours and genuinely good.\nBut a memory engine that only performs in a feedback-rich regime, and never says so, is exactly the kind of thing this field has too much of already. So: the mechanism strengthens what it touches, the regime that exercises it is rare in production, and the cheapest thing you can do about it today has nothing to do with which vendor you pick. It is a standing instruction in a file your agent already reads.\nDisclosure: I work on\nMnemoverse\n, the engine these measurements came from. The full version, with the complete methodology note, the percolation definitions and every vendor citation, is in the\nMnemoverse library\n.",
  "metadata": {
    "title": "The Feedback Dilemma: Your Agent's Memory Learns Most From a Signal It Almost Never Sends - DEV Community",
    "description": "An AI agent with learning memory should get better the more you use it. That is the promise everyone... Tagged with ai, agents, machinelearning, llm.",
    "keywords": "ai, agents, machinelearning, llm, software, coding, development, engineering, inclusive, community",
    "author": null,
    "og:type": "article",
    "og:url": "https://dev.to/izgorodin/the-feedback-dilemma-your-agents-memory-learns-most-from-a-signal-it-almost-never-sends-4akk",
    "og:title": "The Feedback Dilemma: Your Agent's Memory Learns Most From a Signal It Almost Never Sends",
    "og:description": "An AI agent with learning memory should get better the more you use it. That is the promise everyone...",
    "og:site_name": "DEV Community",
    "og:image": "https://media2.dev.to/dynamic/image/width=1200,height=627,fit=cover,gravity=auto,format=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ffevnwq6iow6pu77yuhg9.png",
    "twitter:site": "@thepracticaldev",
    "twitter:creator": "@",
    "twitter:title": "The Feedback Dilemma: Your Agent's Memory Learns Most From a Signal It Almost Never Sends",
    "twitter:description": "An AI agent with learning memory should get better the more you use it. That is the promise everyone...",
    "twitter:card": "summary_large_image",
    "twitter:widgets:new-embed-design": "on",
    "twitter:image:src": "https://media2.dev.to/dynamic/image/width=1200,height=627,fit=cover,gravity=auto,format=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ffevnwq6iow6pu77yuhg9.png"
  },
  "paywall": {
    "listed_paid": false,
    "detected": false,
    "marker": "",
    "public_only": false,
    "policy": "付费/会员内容只保留页面公开可见部分，不绕过付费墙"
  },
  "crawl": {
    "success": true,
    "status_code": 200,
    "error": ""
  },
  "code_blocks": [],
  "images": [],
  "audio": [],
  "videos": [],
  "links": [
    {
      "href": "https://doi.org/10.3389/fncir.2015.00085",
      "label": "DOI:10.3389/fncir.2015.00085",
      "type": "a"
    },
    {
      "href": "https://doi.org/10.1109/ICDM.2008.22",
      "label": "DOI:10.1109/ICDM.2008.22",
      "type": "a"
    },
    {
      "href": "https://www.nngroup.com/articles/participation-inequality/",
      "label": "NN/g, 2006",
      "type": "a"
    },
    {
      "href": "https://arxiv.org/abs/1706.03741",
      "label": "Christiano et al., arXiv:1706.03741",
      "type": "a"
    },
    {
      "href": "https://github.com/mem0ai/mem0/issues/4573",
      "label": "issue #4573",
      "type": "a"
    },
    {
      "href": "https://dev.to/gde03",
      "label": "Giulio D'Erme",
      "type": "a"
    },
    {
      "href": "https://dev.to/kenwalger",
      "label": "Ken Alger",
      "type": "a"
    },
    {
      "href": "https://dev.to/kenwalger/your-memory-api-is-lying-to-your-agent-252h",
      "label": "Your Memory API Is Lying to Your Agent",
      "type": "a"
    },
    {
      "href": "https://mnemoverse.com/",
      "label": "Mnemoverse",
      "type": "a"
    },
    {
      "href": "https://mnemoverse.com/docs/library/agent-memory-feedback-dilemma",
      "label": "Mnemoverse library",
      "type": "a"
    }
  ],
  "repair_version": 2,
  "repaired_at": "2026-10-14T10:49:33Z",
  "source_url": "https://dev.to/izgorodin/the-feedback-dilemma-your-agents-memory-learns-most-from-a-signal-it-almost-never-sends-4akk",
  "papers": [
    {
      "status": "ok",
      "url": "https://arxiv.org/pdf/1706.03741",
      "bytes": 3218596,
      "reused": true,
      "local_path": "papers/repair/06487c88cb70eb4ab099.pdf"
    }
  ],
  "actual_video_files": [],
  "body_chars": 8201,
  "expected_body_images": 0,
  "discovery_status": "ok",
  "delivery_status": "ok",
  "missing_reason": "",
  "raw_html": "attachments/d768c08c0b62/pages/source.html",
  "local_html": "attachments/d768c08c0b62/pages/article.html",
  "body_base_path": "attachments/d768c08c0b62/pages/",
  "body_markdown_path": "attachments/d768c08c0b62/pages/article.md"
}