timgordontg

4 ms·

1.
by timgordontg 26d ago
A brief update from the creator. Version 1.4.0 live on GitHub and PyPI. I wanted to give a large loud shoutout to @mwpastore and @mannusilva for their very helpful contributions. I appreciate their efforts and also the warm welcome it recei
2.
by timgordontg 26d ago
Sure thing. If you find something related to an edge case, let me know specifically and I can try to work it into future improvements.
3.
by timgordontg 26d ago
You are super welcome
4.
by timgordontg 26d ago
Seriously, thank you so much.
5.
by timgordontg 26d ago
just pulled in engrim merge <OTHER.db> - check v1.3.1 (sorry for duplicate reply - had another that was basically same topic) Trying to reply to everyone - thank you.
6.
by timgordontg 26d ago
just pulled in engrim merge <OTHER.db> - check v1.3.1
7.
by timgordontg 26d ago
Updated in v1.3.1
8.
by timgordontg 26d ago
Yea of course, I love building things for fellow homies! Did you get a chance to check it out?
9.
by timgordontg 27d ago
understood, my apologies dang. typing by hand from here on out.
10.
by timgordontg 27d ago
it's just a standard sqlite file in ~/.engrim, so something like litestream or syncthing works fine. just have to make sure wal files get included if syncing live.
11.
by timgordontg 29d ago
I hit this in session 101 after a crash: boot hooks sweep the orphaned transcript into a [RECENT] tail, and separating settled decision records from WIP state tells the new agent what was finished vs what died mid-flight. Good call to be th
12.
by timgordontg 29d ago
Permanent docs definitely belong in git. This is just the desk scratchpad for messy session context so you can /clear freely without cluttering commit history or burning tool calls on grep. Anti Gravity has a large enough context windo
13.
by timgordontg 29d ago
[flagged]
14.
by timgordontg 29d ago
Thanks! And I totally agree with your workflow, fresh sessions are the best way to avoid context degradation. Just to clarify on the decision summaries - I actually don't let agents commit autonomously either! The summaries exist so th
15.
by timgordontg 29d ago
Oh, thanks mom! I will make sure to put on my rain coat before going out to play.
16.
by timgordontg 29d ago
Appreciate it! Plumbers are very important people. Thank you for the collaboration.
17.
by timgordontg 29d ago
Yes! Because the Codex CLI supports the Model Context Protocol (MCP) and lifecycle hooks, it actually worksperfectly out of the box. In fact, your comment just inspired me to push a quick update a few minutes ago: if you pull the latest ver
18.
by timgordontg 29d ago
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 p
19.
by timgordontg 29d ago
Great question, and I just updated the README to clarify this! It's a mix. If you're using connected agents (Antigravity, Claude Code, Cursor) via MCP, they have the engrim_add tool and will automatically log major architectural d
20.
by timgordontg 29d ago
gbrain is an awesome project, but yeah, that was exactly the itch I was trying to scratch! I wanted something that felt as fast, portable, and bulletproof as a single .db file. Zero background daemons or cloud dependencies—just fast, hybrid
21.
by timgordontg 29d ago
Thanks! Exactly. We have M-series chips and massive NVMe drives sitting mostly idle while we pay a 'cloud tax' to store string data. Local SQLite is practically zero-latency, keeps your IP entirely private, and means the memory en
22.
by timgordontg 29d ago
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!
23.
by timgordontg 29d ago
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
24.
Show HN: Engrim – A universal, local-first SQLite memory engine for AI CLIs(github.com)
93 points by timgordontg 29d ago|65 comments