Live data from Hacker News

Open source memory layer so any AI agent can do what Claude.ai and ChatGPT do

alash3al.github.io

81–87 of 87 posts

Re: Open source memory layer so any AI agent can do what Claude.ai and ChatGPT do

#81
post #80

Earlier quoted context omitted.

Fair enough, we all have our preferences and opinions. What signals would you be looking for to make your judgement call? > it doesn’t cover people who would have produced rubbish anyway How do you determine this though? If it becomes common for people to include an AI usage profile, what does that really do? I can say I followed best practices, steered design, supervised the LLM, reviewed the code, etc... but those…

If you keep saying things that don't hold up, that tends to harm your reputation. Do I really need to explain basic social dynamics? Sure, maybe I'm wrong and this totally wouldn't work. Maybe (probably) not enough people think it's a good idea and it never happens. Maybe everyone just decides to lie through their teeth. Maybe there's no significant relationship between how carefully you use an LLM and the quality of…

I get the social dynamics, and I agree that we need more signals to build trust, even if I disagree on this particular signal.

I think enhancing SDLC visibility could be valuable, which is somewhat related to your original suggestion, though I'm not sure how to validate something like that since workflows and tests tend to be unique. I suppose we have badges like 'build:passing' that aren't standard, but are somewhat adopted and show that some extra effort went into setting that up. It would be nice to have something a bit more standardized and verifiable though.

Anyway, I appreciate your engaged responses, and even if we don't see eye to eye on the LLM signal, I think we both want the same thing, which is increased trust in third-party software. I hope we get there someday, even if it seems we're moving in the opposite direction right now.

Re: Open source memory layer so any AI agent can do what Claude.ai and ChatGPT do

#82

I clicked this thinking “oh, cool, someone finally made a portable version of the Claude.ai* memory system!” Spoiler, no, it’s not it at all, it’s just a “store”/“remember” memory system… as opposed to the Claude.ai memory system, where it doesn’t make the model actively have to write memories on its own, but rather has a model in the background go through your chat history and generate a summary from it. I’ve found…

Shameless drop: My own agentic environment is also using a summarizer to sum up agent histories when they overflow in their context windows. Additionally, all short lived agents are based on requirements (WIP) as a centralized point for code, unit tests, and architecture.

(Everything is tailored to Go as a language)

Works pretty good so far, the user only interacts with the planner. I'm working atm on the requirements to have a spec driven workflow. Web UI is the most polished atm because of ability to have agent tabs on the side for better overview.

In case anyone is interested in this attempt:

[1] https://github.com/cookiengineer/exocomp

Post reply on HN