Top
Best
New

Posted by mthines 7 hours ago

Agent memory needs its OpenTelemetry moment(www.lorekit.io)
101 points | 78 commentspage 2
eladlev 4 hours ago|
How does this handle parallel sessions writing the same memory? From a quick look at the repo, it seems that one session can silently overwrite another. Anthropic's recent memory post shows how severe this can be (https://www.anthropic.com/research/components-of-agent-memor...). Should the spec cover this?
Muromec 4 hours ago|
Maybe don't give all your agents the same memory. Shared stuff can be in the repo they work on as files.
mohsen1 2 hours ago||
Working with LLM agents comes with a hard pill to swallow: they are already remarkably good at figuring out what to do on their own. In fact, the more rigid structures we impose on a system, the less efficient these agents become.

While there have been many attempts to structure how agents operate, a recent Anthropic article showed that when they didn't tell Claude how to use memory, it actually used its memory better. Ultimately, we have to come to terms with how little is required from us when LLMs are this intelligent. often doing things better in ways that we sometimes cannot comprehend.

mceachen 47 minutes ago|
I don't buy it. You can steer them gently to at least write human-accessible project plans—and then session compaction, agent switching, and review is much more doable. I've been iterating on this for over a year: https://photostructure.com/coding/claude-code-tpp/
jonstewart 15 minutes ago||
Hacker News needs its slop-rejection moment.
hemkeshr 5 hours ago||
I agree this is very much needed but I doubt the other ai companies would a-comply with this as they need users and mainly paid users otherwise they'll lose themselves. What I think is that with 20$ subs of 2-3 ai can give you more usage compared to their 100$ subs if you do it that way. I don't know will these companies work together to form a standardized memory system. I highly doubt that.
rickdg 4 hours ago||
I'm ready for the conversation to just assume a linux file system with mostly markdown. And you schedule some time every day for an agent to make it not suck as much as a living archive.

What are some real issues now? Auth? You want to retroactively implement boundaries? Is version control the problem?

totetsu 5 hours ago||
I think It needs to be as diverse as people .. If agents are to become our constant "muse" like companions, I want the wiring of the brain of mine to be as wired as possible.. Why not juggling chain saws in orbit.. https://www.youtube.com/watch?v=JcJSW7Rprio&t=17s
jaynate 5 hours ago||
This seems like local memory for one user. The need for corporate agent memory that works across users and company processes is acute.
kohlerm 5 hours ago|
Yes, also I doubt that we already know how to best implement memory for plans. Is it really only files? Maybe some db approach with queries is needed?
cryptoboy2283 4 hours ago||
Do you mean another overcomplicated enteprise standard teeming with constant CVEs to increase surveillance and control?
slopinthebag 6 hours ago||
at this point i'm pretty convinced agent memory is strictly harmful. it remembers the wrong things, and then turns them into an inane focus for each task. i disable it universally on every harness. if i want memory, i specifically instruct the agent to record findings into a file.
SwellJoe 6 hours ago||
Same. Everybody builds one, and then eventually realizes it makes the model stupid and confused. The right solution is pretty much always developer documentation in the repo, in roughly the same shape you'd make developer docs for humans that you want to be able to get up to speed about your codebase really quickly.

This has the benefit of being something you can easily read over every now and then to make sure the model hasn't baked in some random comment you made about a specific circumstance a month ago and made a weird religion out of it.

Kwpolska 4 hours ago|||
Agreed. Claude Code often tries to write one-off decisions and transient problems into memory. And when such things appear in the context, Claude will start doing questionable actions, because it saw something unrelated and wrong somewhere in its context
nonethewiser 5 hours ago|||
Also introduces massive confirmation bias. Majorly gimps the model. I remember I was exploring hexagonal architecture on chatgpt and then future conversations with open ended architecture questions just gave me those same patterns.

“Oh damn look its recommending something that looks like hexagonal architecture. I guess hexagonal is a really good - hey wait a second …”

nonethewiser 5 hours ago|||
I strongly agree. This is becoming a general principle along the lines of “code comments that describe what the code does are bad.”

Memory just ensures there is a fairly high level of drift and inaccuracy in your context. Unless YOU are manually curating it.

Its similar to wiki systems where your agent produces tons of documentation and decision records, etc. Its a bunch of assertions about your codebase that you aren’t vetting and which is at most 90% correct. Thats good enough for a feature or bug fix that you can validate with tests but for the love of god throw the details away. You don’t want to codify that. It’s polluting the context and gimping the model.

bluescorpio 3 hours ago||
[flagged]
te_chris 6 hours ago|
So we need another complicated format to store information so that the machines which read unstructured text can work with it?
More comments...