Urgent.News

What's breaking now, across thousands of outlets.

AI

Giving an AI agent memory is easy. Keeping it true is the hard part.

Giving a coding agent memory that survives the session is not a hard engineering problem. A directory of markdown files outside any repo, one fact per file, an index that gets loaded at the start of every session. That is the whole mechanism, and it takes an afternoon. I have been running one for about four months across roughly forty projects. The mechanism has never been the problem. In a…

Memory in AI agents is simple to implement, but maintaining its accuracy is challenging. All that is required is a directory of markdown files containing one fact per file, along with an index that gets loaded at the start of each session. However, even the mechanism itself is not the issue. Despite running such a system for about four months across around forty projects, four separate memory entries were found to be confidently wrong, each steering decisions for weeks.

The problem lies in the inference drawn from the memory entries, which become conclusions without their reasoning left behind. Unlike typical notes, these entries were written carefully at the moment of work, with full context, recording judgments as facts. Once an entry is written, the reasoning is lost, and only the conclusion remains.

This becomes problematic as conclusions do not carry their own expiry date. The solution is to add a re-check command to each entry, making the claim falsifiable and allowing future sessions with no context to catch errors quickly. Additionally, it's crucial to distinguish between observed facts and inferred conclusions, as the latter can become outdated.

When memory and the filesystem disagree, the filesystem should be trusted. The risk with agent memory is not hallucination but decay, where entries become snapshots of moments that do not reflect the current world. Regular verification from outside the system that made the claim is essential, as relying solely on the system's opinion can lead to errors.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in AI

What I Learned Turning an AI News Crawler into a Working Product

Fetching an article is only the beginning of a news pipeline. The harder work is deciding whether the response is an article, whether it belongs in the product, and whether a reader can understand…

  • Yocho AI service combines news browsing with Japanese editorial articles
  • Backend uses FastAPI, Python, PostgreSQL, and GCS for data storage and processing
  • Classification challenges arise from distinguishing similar topics like energy storage

The AI Code Review Bottleneck: Why Our Merge Time Tripled

The pull request was 1,140 lines. The description was four bullet points. It had been opened eleven minutes after the ticket was assigned.

  • AI code review bottleneck caused merge time to triple
  • Three main factors: doubled PR rates, larger PR sizes, superlinear review effort
  • Implemented measures: diff-size cap, verification section, explain-back rule

More from Wednesday 9 September →