1 comments

  • mthines1 hour ago
    A couple of weeks ago I built an open source system for handling memory for agents, and it&#x27;s called LoreKit.<p>It supports local and remote (so you can share with colleagues for instance) memory, it&#x27;s free, open source and REALLY easy to set up.<p>Local memories requires no sign up, but remote does obviously - but sign up is just OAuth.<p>It&#x27;s retrieving memories lexically - so no embedding (for now), but using scopes and labels to make sure the memories you retrieve are relevant automatically. And it scales from 6 - 60.000 memories (load tested).<p>I&#x27;ve also built a website which reads usage statistics for you to help you understand and optimize your workflowz and 3 agent skills to ease the installation and integration into your existing skills. <a href="https:&#x2F;&#x2F;lorekit.io" rel="nofollow">https:&#x2F;&#x2F;lorekit.io</a><p>I&#x27;ve written a blog post on how to get started and some of the problems it tackles, but I would like to hear your thoughts on it, like:<p>- what&#x27;s currently holding you back from using memory which persists between sessions? - do you prefer local, local (but committed) or fully remote?<p>See repo: <a href="https:&#x2F;&#x2F;github.com&#x2F;mthines&#x2F;lorekit" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;mthines&#x2F;lorekit</a>