Live data from Hacker News

Agent memory as a file format

calpaterson.com

111–115 of 115 posts

Re: Agent memory as a file format

#112

Earlier quoted context omitted.

"text based index" is just another way of saying "database".

No it isn’t? There is no database and no querying for specific words. An llm reads a big ass block of text and determines if any of those lines are applicable, that is nothing like a database being queried

i think you are confusing database with something like mysql

Re: Agent memory as a file format

#113

Earlier quoted context omitted.

I have memory disabled in all my Chat UIs (even though it tends to creep in, looking at you ChatGPT). It’s very helpful until it scales with time, at which point it becomes useless due to staleness or mis-application across contexts. That being said, in coding over a longer time horizon, having the agent continually re-derive decisions/laws/facts/etc from your code is wasteful of tokens and time, and if your code doe…

I like a lightweight ADR system. e.g. docs/decisions/README.md (index with a blurb about each decision), docs/decisions/01-some-lesson.md (some architectural decision/pattern that you or the agents discovered). ADR files have important sections like "rejected solutions" and "acceptable risks", and they're live files that can be refined and pivoted over time or retired to docs/decisions/archive/. It's also nice to giv…

[flagged]

Re: Agent memory as a file format

#114

What the author suggests is remarkably close to the proposition of OpenViking. I've been testing a few memory solutions and OpenViking is one of my favorites so far.

I'm looking in the same space: have you found anything else you're considering beyond OpenViking?

Re: Agent memory as a file format

#115

Instead of having to regenerate a zip file everytime you add/delete a memory... could we just use a git repo of markdown pages? This buys you incremental writes, commit hash pinning and diffs for free. In addition to having a git archive outputting a zip export as well? Main wrinkle is you would need to gitignore the sqlite database as it doesn't store very well in git (binary, changes lots per insert). But it's easy…

You don't have to regenerate a zipfile each time you do something - the zipfile is just to give a single file for distribution. It's just a zip of the directory. Git is supported in the spec, though the tool doesn't yet handle it (soon! git is nice as you get a log "for free" which helps agents understand more about the memories). As for sqlite in git: yes you can gitignore it, you could use git-lfs, you could use an…

Ah good to hear!

Well regarding how CSV didn't quite work for you. Have you checked out recutils?

Its a GNU Project and at least does basic relational database operations on plain text files. You can easily install it in most linux package managers.

https://en.wikipedia.org/wiki/Recutils

Post reply on HN