Blog
Thoughts on tech projects, cybersecurity, infrastructure, and things I'm learning.
Browse by Topic
Weekly Digest
Get a weekly email with what I learned, summaries of new posts, and direct links. No spam, unsubscribe anytime.
Thoughts on tech projects, cybersecurity, infrastructure, and things I'm learning.
Get a weekly email with what I learned, summaries of new posts, and direct links. No spam, unsubscribe anytime.
A pairing/admin-approval privilege escalation CVE hit OpenClaw. My security agent ran a threat hunt, my builder agent implemented a Security Panel on the Mission Control dashboard, and 15 files later the system can see itself. Here is the full story.
I tried to schedule my gmail-assistant agent via Dispatch, then discovered Channels and Remote Control solve the problem differently. Here's how all three compare for mobile-triggered local automation.
Building a pixel-art retro dashboard to command 7 AI agents on an M4 Mac Mini: System Health, Agent Fleet, Team org chart with role card modals, Telegram monitoring, cron jobs, and more.
Running OpenClaw locally on a headless Mac Mini sounds simple until your bots go silent at 2am. Here are the pmset settings, watchdog cron, and daily log setup that actually keep it running.
A deep dive into OpenClaw's three-tier memory system: hybrid search with nomic-embed-text embeddings, temporal decay, sqlite-vec vector storage, and the full configuration that makes agents remember across sessions.
After Part 1's fortress locked itself out, I rebuilt OpenClaw incrementally: one security control at a time, with 7 agents, 6 Telegram bots, and verification after every step.
I used a team of 5 AI security agents to build a hardened OpenClaw deployment on my M4 Mac Mini. After implementing every security control imaginable, nothing worked. Here is what happened, why I did not quit, and what I planned instead.