Sqlite

Two mornings in a row, I had a reassuring Telegram notification from my AI assistant. The OpenClaw gateway had stopped responding, the watchdog had restarted it, and everything was healthy again. Nothing needed from you. On the second morning, that sentence deserved an investigation. The recovery mechanism was working. But a service that needed rescuing every night was not fixed. I asked Closp, my OpenClaw assistant, to compare the incidents, investigate the growing database, and find a solution that preserved its memory and usefulness. ...

Earlier this year I built an AI and technology news digest. It pulled from newsletters, Hacker News, and Reddit, filtered for AI terms, and sent the results to Telegram every few days. It was useful. It was also a list generator. The system knew that an article matched a keyword and that a link was popular. It did not know whether I had seen the same underlying story three times, whether a consequential claim had a primary source, whether the item connected to anything I was working on, or whether I had rejected the same kind of recommendation last week. ...

I have a Quick Notes topic in Telegram. It is the nearest thing my personal system has to an input box: send a sentence from my phone and let the machinery put it somewhere useful. The first version was efficient in the way a paper shredder is efficient. It could turn a message into a calendar entry or task, but it did not understand that a thought, a reference, a question, and a commitment are different things. ...

There’s a temptation, when you spot a problem in a personal project, to just fix it. Open the file, start editing, ship. It feels productive. It often isn’t. This week I migrated the state layer of my personal AI assistant from a collection of flat JSON files to SQLite. The migration itself took about 20 minutes of actual work, spread across four automated phases. The planning took two hours. And the planning was the most valuable part. ...