Funny how the building didn’t collapse into its own foot print like with 911. Strange how this type of physics doesn’t work anywhere else or during any of time. 🤔
I solved this by implementing @automem_ai with hooks and MEMORY dot md. Here's how my openclaw (Clive) explains the setup:
AutoMem hook (~/.openclaw/hooks/automem-memory/) handles everything automatically:
• Auto-saves sessions before /new or /reset (extracts last 15 messages, generates summary with smart importance scoring)
• Auto-recalls 10 most relevant memories on session start
• Runs on gateway startup for warm context
Service: Railway-hosted AutoMem (graph-vector memory)
Interface: MCP server via mcporter
Result: 312 memories, zero manual calls, survives restarts
Hook config persists in openclaw.json. AutoMem handles smart search; MEMORY dot md holds narrative context. Together = nothing gets lost.
---
This is also the same memory tool I use in Claude, so my memories persist across all my AI tools (any tool capable of running MCP)
GMGM $CRCA!
I know I said I'd release the webUI for CR-CA by Valentine's, & unfortunately I wasn't able to. However the design is complete, all that's left for now is API setups.
After that's done I'll be releasing the webUI as a short 1-week Public Testing beta. In which any fees will be covered for by me. After the testing period is over, feedback has been received, development will continue until it is ready to be released as a prod-ready beta.
I believe I'll be able to release LUAF much sooner, I already have a roadmap ready for it, & some updates.
That's all for this hour.
Hey guys,
Long time no see—life got a bit busy for a moment. Behind the scenes, I’ve been developing my agent, Chira, powered by $AUTOMEM.
Here is the current architecture to give you a better idea of how it works:
THREAD🧵
Progress report!
The webUI for $CRCA is essentially complete, all thats left is figuring out what to use for the db, was thinking big with Supabase & Redis, however I do NOT wanna suffer with either of those, so for DB it'll probably be mySQL or MariaDB, or something simple of the sort.
A big milestone for me since September was being able to call @autojack_bot and dispatch #agents via voice from the Watch action button.
Unlocked 🔓
Agent status is visible in real-time across every node. Questions / status come through as push notifications or Slack DMs 😎
ok folks the weekend is coming and you know what that means— all the customers, clients, (and actual money) goes quiet and i can get back to cooking some sweet @automem_ai goodness 🧙♂️🔮
🧵 The Core Problem $Automem Solves
Dev @jjack_arturo
1/
Most people think AI Memory is about:
• remembering your name
• saving chat history
• bigger context windows
That’s not the problem.
The real problem is:
Every LLM interaction starts from zero.
You’re constantly re-teaching, re-explaining, re-contextualizing.
Your AI never learns, never connects, never builds on past work.
Just released v0.11.0 of the AutoMem MCP 🔥
This update includes better error handling, more comprehensive automated tests, updated prompt/template files for Cursor, Claude Code, and Codex, as well as a Claude Desktop plugin so you can one-click install AutoMem without having to edit the JSON configuration files 😎
Install/upgrade:
npm i @verygoodplugins/mcp-automem
Full changelog: github.com/verygoodplugins/m…
First feature complete: The "Ears" and "Voice" are active. ✅
I’ve built a dynamic "Smart Router" system:
👂 Local Whisper (Hearing)
⚡ Gemini 3.0 Flash handles speed, routing & daily chat
🔬 Gemini 3.0 Pro handles heavy reasoning & coding
🗣️ Neural TTS (The Voice)
Today marks the day when i start creating an ai assistant from scratch.
It will be voice activated, it will automate my tasks and will have a persistent memory with $AUTOMEM.
It will be accessible on my computer and mobile.
I will experiment alot during this journey.