Hacker News
points by baalimago 8 hours ago | 0 comments
Do we really need this..? What LLMs do well is interpret natural language. So it's a sponge for whatever format is used in a specific project: a predefined format is not really needed.

Besides, do we really want memory of user A's agents to co-exist with memory of user B? Not really. So the argument for collaboration and sharing is quite slim, at least for coding agents. The repository specific context can be encoded into a docs/ or architecture/ directory, just like it's been done pre-agent times as well.

For monitoring deployed agents: maybe. For this I built (yet another) memory management tool slivingdoc.dev, with this it's possible to pull down the durable context of all agents. But here the problem is a distributed system one, not format of the memories.

[–] verdverm 5 hours ago
Structured metadata like this is for the non-LLM tooling layer, primarily your harness, so (eg.) it can interpret multiple formats without needing to burn tokens every time.
Hacker News