[flagged]
Show HN: Engrim – A universal, local-first SQLite memory engine for AI CLIs
71–73 of 73 posts
Re: Show HN: Engrim – A universal, local-first SQLite memory engine for AI CLIs
#72Earlier quoted context omitted.
opencode export -h you can also work with the opencode sqlite database directly
I am not sure we are talking about the same thing. I am talking about a way to automatically create memories, for agentic use. This involves knowing when to create, amend, and delete memories. Are you handling these tasks? This is the core of agentic memory management. Your responses seem to indicate a different use case, like making backups.
yes, I decide these things because the agents are not up to the task, hence why I would not automate it in the background, instead using human in the loop automation to build evaluate, process, create more permanent markdown.
I use the exported sessions for a number of things, "backups" is another, though it is more about building a complete data set of all my sessions than making sure they are not lost
Re: Show HN: Engrim – A universal, local-first SQLite memory engine for AI CLIs
#73Earlier quoted context omitted.
you dont need to, export the sessions and render them to markdown, a nice thing is that OpenCode already understands project locality, so use a .sessions for in you repo and get project specific memories (probably want to summarize them down, do other massaging, but a script and skill is sufficient)
yeah. you don't even need to export. i wrote a cli tool to query the opencode sqlite database. it's not great, i would want to improve it more before announcing it, but: it works for me and my agents. it was easy to write/understand. https://tangled.org/jauntywunderkind.bsky.social/opencoattai... i also am working on bookmark features too! a skill and more cli, i'll add a tool too, but often i don't even use tools, j…
Can you please you capital letters as most people do, it's incredibly difficult to find sentence/thought boundaries, or at least put some newlines between them if the shift key is such a burden
I prefer json to sql, because I need the json version for various reasons. Sqlite text searching is leaving a lot on the table compared to a Typesense based setup imo