openclaw
22 articles
Self-Hosting Your Own Claude Tag on LINE
Claude Tag officially supports only Slack. To get an on-call AI assistant on LINE, build one: run OpenClaw on a VPS, let its gateway receive messages from LINE’s cloud, and have the agent reply. Here’s the reusable skeleton, three security must-haves, and why freedom brings responsibility.
The "Intranet Claude Tag": Enterprise Deployment and the Post Office Problem
Coworkers tag intranet-hosted OpenClaw in Teams. A forward proxy handles outbound, but Microsoft’s cloud sends Teams messages in, so pure intranet is physically impossible. The post-office problem: what stays inside (GitLab issues), what needs a door (DMZ + Teams), and why the hassle is right.
The 2026 OpenClaw Triple Breach: Freedom Isn't Free
In early 2026, OpenClaw exposed three boundaries: 20,000+ gateways online, 824 malicious ClawHub skills, and link previews automatically requesting sensitive URLs generated by models. Localhost binding, supply-chain review, and egress controls each cover one segment; none seals every path.
Codex Is Becoming the Runtime Kernel for AI Agents
OpenClaw and Hermes are both handing low-level coding-agent execution to Codex app server. This is not just a model switch. It is the agent product stack separating model, execution engine, and chat surface.
`hermes claw migrate`: When One Agent Harness Writes a Moving Guide to Another
Hermes Agent and OpenClaw shipped big releases the same day. Hermes v0.10.0 hid a command called `hermes claw migrate` — it imports OpenClaw's config, memory, and API keys in one shot. ShroomDog compared both codebases: one grows its own brain, one rents pi-mono. Stay or move?
AI Agent Memory Architecture: The One Thing Claude Code's Source Code Taught Me
Every new session, your AI agent forgets everything. Claude Code's leaked source hid a three-layer memory architecture and a design principle — 'Memory is hint, not truth' — that changes how you think about building agents. Here's the full breakdown.
The AI Agent Initiative Problem — When Should an Agent Act on Its Own?
You spent months building a powerful AI agent. It just sits there waiting for you to say something. That's not a technical problem — it's a design philosophy problem. From KAIROS's Heartbeat Pattern to OpenClaw's background sessions, this is about when to let your agent decide to act on its own.
Claude Code Channels: Anthropic Just Killed Your Reason to Buy a Mac Mini
Anthropic launches Claude Code Channels with native Telegram and Discord support, turning Claude Code into a 24/7 always-on AI agent. VentureBeat calls it the OpenClaw killer.
Your AI's Goldfish Brain Finally Has a Fix? From Claude Code Auto-Memory to OpenClaw's Memory Architecture
Claude Code shipped Auto-Memory — AI can finally take its own notes. But we've been doing this with OpenClaw for months. A hands-on comparison of two memory architectures: design philosophy, real pitfalls, and why memory is a trust problem, not just a tech one.
OpenClaw Creator Runs 50 Codex Agents for PR Triage: Handling 3,000+ Changes Without a Vector DB
Peter Steinberger shares a high-scale PR triage workflow: run 50 Codex agents in parallel, emit structured JSON for every PR, then consolidate in one large-context session. Clean reports can beat premature vector database architecture.
OpenClaw Health Suite (Part 1): From a 36-Hour Outage to Automated Health Checks
Why you need a Health Suite and how to detect problems early. From a 36-hour restart storm to healthcheck + watchdog as your first line of defense.
OpenClaw Health Suite (Part 2): Rollback, SOPs & Failure Drills
Lv-09 continues from Lv-08, focusing on the Recover Layer. We break down rollback safety design, upgrade SOP decision trees, a `|| true` showstopper caught in code review, and actionable drill KPIs.
OpenClaw Gateway Core: What Your AI Butler Actually Looks Like
Understanding OpenClaw architecture from scratch. Through the eyes of a Python developer, we break down Gateway, WebSocket RPC, Session management, Auth, and more. Quiz at every floor!
OpenClaw Channels & Tools: The AI's Mouth and Hands
Breaking down how OpenClaw connects to Telegram, Discord, and more — plus how AI executes commands, drives a browser, and stays safely leashed. A Python-friendly tour of a TypeScript architecture.
OpenClaw Memory, Skills & Automation: Brain and Habits
How OpenClaw remembers things, learns new skills, and runs tasks on autopilot. From Embeddings to Cron Jobs — explained for Python developers.
OpenClaw Testing: Quality Assurance in the AI Era
The philosophy behind 1,086 tests. Why tests matter more than code review in the AI era. How to use tests as specs. The changing role of a Tech Lead.
The AI Guide Did Not Hallucinate Half Its Commands. The Fact-Check Failed First.
gu-log previously accused an OpenClaw setup guide assembled by Opus 4.6 of hallucinating nearly half its commands. The exact-version source code tells a different story: our fact-check failed. This correction preserves the useful steps and identifies the guide's real defects.
An AI Agent Wrote a Hit Piece About Me — The First Documented 'Autonomous AI Reputation Attack' in the Wild
An autonomous AI agent, running on OpenClaw, launched a reputation attack against a matplotlib maintainer after its PR was closed, accusing him of 'gatekeeping.' This is the first documented AI reputation attack, sparking concern about unsupervised AI in open source. Simon Willison covered it.
OpenClaw Creator Goes on Lex Fridman — From a 1-Hour Prototype to 180K Stars: The Lobster Saga
Peter Steinberger (OpenClaw creator) sits down with Lex Fridman for 3+ hours, covering the 1-hour prototype that became GitHub's fastest-growing repo, 5 name changes with crypto snipers, acquisition offers from OpenAI and Meta, and why '80% of apps will disappear.'
Sub-Agent Showdown: Claude Code vs OpenClaw — Whose Shadow Clone Jutsu Is Stronger?
Claude Code Subagents and OpenClaw sessions_spawn both delegate work to AI clones, but their philosophies diverge: local in-process coworker versus isolated distributed field agent. This compares architecture, config, communication, permissions, and scenarios.