Earlier quoted context omitted.
The 0.4/0.4/0.2 weights are just based of hand wavy trail an error, will look into other options. I could make them configurable?
I think that'd be cool, maybe just a simple config option in pyproject.toml or a .rekal/config.yml would cover most use cases: they could default to 0.4/0.4/0.2 but could be overriden.
Show HN: Rekal – Long-term memory for LLMs in a single SQLite file
11–18 of 18 posts
Re: Show HN: Rekal – Long-term memory for LLMs in a single SQLite file
#12Re: Show HN: Rekal – Long-term memory for LLMs in a single SQLite file
#13I’m going to try this out. Curious how effective it’s been for your own use, OP? Anything particularly interesting or where it still falls over and requires tuning that you’ve observed? I find these types of projects interesting in sort of an anthropological sort of way. So far, I’ve yet to try anything that hasn’t still required a great deal of intervention to keep agents using guardrails without scolding them to do…
Re: Show HN: Rekal – Long-term memory for LLMs in a single SQLite file
#14Re: Show HN: Rekal – Long-term memory for LLMs in a single SQLite file
#15Re: Show HN: Rekal – Long-term memory for LLMs in a single SQLite file
#16Earlier quoted context omitted.
I think that'd be cool, maybe just a simple config option in pyproject.toml or a .rekal/config.yml would cover most use cases: they could default to 0.4/0.4/0.2 but could be overriden.
Added a mcp command for it, but i might add it as a comfig as well? https://github.com/janbjorge/rekal/pull/14/changes