| ▲ | mmasu a day ago | ||||||||||||||||||||||||||||
I am curious about what people do these days and how do they tackle this problem. At repo level you can alter by with AGENTS.md and perhaps a curated set of additional docs with the project history, but as soon as you get out of it and want to have additional context the solutions available are too many - Hindsight, Graphiti, and many others; or simply roll out your own? I would like something I can spin up with Postgres or with an S3 bucket and that writes me .md files while retaining some sort of relationship among different entities - however it looks like there is no “simple” solution out there yet, with many of the existing implementations being way too elaborate and/or requiring exotic DB solutions. Would be very interesting to hear if someone knows of a bare bones solution I can plug into any agent. | |||||||||||||||||||||||||||||
| ▲ | everforward a day ago | parent [-] | ||||||||||||||||||||||||||||
The simplest I’ve found is to add instructions to the AGENTS.md telling it to keep a knowledge base in a directory and refer to it. You could add a hook or something to use the AWS CLI to sync the dir to S3. The agent actually did pretty well managing and searching it with grep. A lot of these memory systems are reaching for the stars and I sort of suspect we’re way past the Pareto point for coding there. | |||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||