Live data from Hacker News

Show HN: Engrim – A universal, local-first SQLite memory engine for AI CLIs

github.com

31–40 of 70 posts

Re: Show HN: Engrim – A universal, local-first SQLite memory engine for AI CLIs

#31
post #13

> Run engrim setup without arguments. It automatically detects installed environments on your machine and configures them all Does it come with an uninstall script?

It does now! Good call. I actually just pushed an update based on your comment that adds engrim uninstall to cleanly unwire the hooks, MCP servers, and skills across all environments. Thanks for keeping me honest!

Thanks and no problem.

Everyone should start calling me a plunger because I often hear that i was right to push back.

Congrats on the launch!

Re: Show HN: Engrim – A universal, local-first SQLite memory engine for AI CLIs

#34
post #28

OP appears to be an LLM. Project looks very interesting though. I especially like the provenance idea.

No, I am not an LLM. I do use LLMs to help draft replies as I am a busy person living in the real world. Really glad you like the provenance feature tracking which agent (or human) made which decision ended up being one of the most useful parts of the whole system for me.

Other busy people in real world are then subjected to your generated content. Why bother generating then. Just write down the same thing you prompted llm with

Re: Show HN: Engrim – A universal, local-first SQLite memory engine for AI CLIs

#35

Hi HN, I built engrim to establish a local-first, open standard for cross-model AI agent memory. As context windows scale past 1M+ tokens, developers face rapid attention dilution: reasoning degrades, and token costs multiply exponentially with every turn. But if you clear your agent's session (/clear) to save money and speed things up, the agent suffers total episodic amnesia, forgetting architectural rules, past de…

I hope you don't mind me asking you some ELI5 questions because I'd like to understand how this fits in with everything else.

I generally discourage my agents from storing memories locally because they don't travel; I'd much rather have a small in-repo document—whether it's an architectural decision or TODO or session log entry or runbook or environmental quirk or something else—that the prompt/CLAUDE.md/whatever can guide agents to grep and sed. Then I can dispatch work to a local agent, or a local agent running in a sandbox, or an agent running in a provider's cloud environment, or a GitHub agentic workflow running a headless harness, etc. and they all have access to it. Another benefit is that memory updates get PRs and reviews like everything else.

So what am I missing by not using something like engrim or gbrain?

Re: Show HN: Engrim – A universal, local-first SQLite memory engine for AI CLIs

#36

OpenCode?

already has a full sqlite based memory store of everything. :)

But it is not in a format optimised for the task. What kind of a query would you execute, LIKE across all your sessions?

Re: Show HN: Engrim – A universal, local-first SQLite memory engine for AI CLIs

#37
Tim, could you expand on this part?

> Empirical Proof (The 105-Session Case Study)

Is this something you can benchmark against competitors? Lots of these memory plugins are cropping up and nobody knows how they compare.

It seems the meat of your work is in https://github.com/timgordontg/engrim/blob/main/src/engrim/m...

There is no lifecycle management or conflict resolution yet, and the models do the work of deciding when to use it.

Re: Show HN: Engrim – A universal, local-first SQLite memory engine for AI CLIs

#38
post #31

Earlier quoted context omitted.

It does now! Good call. I actually just pushed an update based on your comment that adds engrim uninstall to cleanly unwire the hooks, MCP servers, and skills across all environments. Thanks for keeping me honest!

Thanks and no problem. Everyone should start calling me a plunger because I often hear that i was right to push back. Congrats on the launch!

Appreciate it! Plumbers are very important people. Thank you for the collaboration.

Re: Show HN: Engrim – A universal, local-first SQLite memory engine for AI CLIs

#39
post #34

Earlier quoted context omitted.

No, I am not an LLM. I do use LLMs to help draft replies as I am a busy person living in the real world. Really glad you like the provenance feature tracking which agent (or human) made which decision ended up being one of the most useful parts of the whole system for me.

Other busy people in real world are then subjected to your generated content. Why bother generating then. Just write down the same thing you prompted llm with

Oh, thanks mom! I will make sure to put on my rain coat before going out to play.

Re: Show HN: Engrim – A universal, local-first SQLite memory engine for AI CLIs

#40
post #33
post #32

Does agent memory actually work as a concept yet? I've only seen LLMs commit garbage to memory and recall in irrelevant contexts.

You need "dreaming" phase;large context high quality llm to prune and condense the memory.

[dead]
Post reply on HN