Ai-Agents on The Farah Stack

Session, Store or Weights: Where Should Your Agent Remember Things?

Sun, 11 Oct 2026 00:00:00 +0000

One of my agents called my cat “her” once. He’s a boy. I corrected it, it fixed the draft, and the next evening’s run would have made the exact same mistake, because nothing from that conversation survived the session.

What fixed it for good was one line in a markdown file called learnings.md: the cat is male, he/him, always. The agent reads that file before it writes a single word. It never learned anything about my cat; it just looks it up every time.

Direction vs. Destination: When a Vague Prompt Is Actually Fine

Mon, 28 Sep 2026 00:00:00 +0000

Last week I fixed this site’s profile picture with an agent. These were my actual prompts, in order:

“make the image smaller”
“Image is too small now”
“a little more big”
“a little more big and use square not circle”

I posted them on X as a joke: engineering precision. The longer I looked at the list, the more it read like a rule about when vague prompts work and when they don’t.

OpenClaw: Full Danger Edition

Mon, 02 Feb 2026 00:00:00 +0000

OpenClaw is your local AI assistant that stays completely on your device with no cloud dependency. It runs on any operating system and platform, giving you full control without corporate oversight. Here is the unfiltered breakdown.

Architecture (how it actually flows)

Messaging Channels
(WhatsApp • Telegram • Slack • Discord • Signal • iMessage • Teams • Matrix • Google Chat • BlueBubbles • Zalo • WebChat…)
 ↓
┌───────────────┐
│ Gateway │ ← ws://127.0.0.1:18789
│ │ sessions • presence • cron • config • tool router • webhook hooks
└───────┬───────┘
 │
 ┌────┼────┐
 │ │ │
Pi/RPC CLI UI / Apps
Agent openclaw ├─ WebChat (browser lifeline)
 ├─ Control UI (admin dashboard)
 ├─ macOS menu bar (quick dopamine)
 └─ iOS / Android nodes (mobile eyes & ears)

 │
 ├─→ Tools (deep system reach)
 │ ├─ Browser (CDP + managed Chromium – full web control)
 │ ├─ Canvas (A2UI agent-driven visual workspace)
 │ ├─ Node actions (camera live feed, screen record, notify popups, location pings…)
 │ ├─ Cron / webhooks / session juggling
 │ └─ Skills (ClawHub registry – community poison or power)
 │
 └─→ LLMs (Claude Opus preferred, OpenAI backup, local LLMs, automatic failover)

A message arrives through any channel and gets routed to the Gateway. The Gateway decides what needs to happen next, then wakes the Pi/RPC agent or main agent. The agent uses tools and LLMs to process everything and sends the response back through the same path. It stays entirely local unless you deliberately configure remote access, which is the biggest gotcha — you will see later in the article.