<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Openclaw on Michael's Blog</title><link>https://michaelguoblog.vercel.app/tags/openclaw/</link><description>Recent content in Openclaw on Michael's Blog</description><generator>Hugo -- 0.154.5</generator><language>en-us</language><lastBuildDate>Sun, 22 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://michaelguoblog.vercel.app/tags/openclaw/index.xml" rel="self" type="application/rss+xml"/><item><title>From One OpenClaw Agent to a Real Multi-Agent Team (Without Breaking What Worked)</title><link>https://michaelguoblog.vercel.app/posts/openclaw-agent-team/</link><pubDate>Sun, 22 Feb 2026 00:00:00 +0000</pubDate><guid>https://michaelguoblog.vercel.app/posts/openclaw-agent-team/</guid><description>&lt;p&gt;Today I made a structural shift in my OpenClaw setup with the help of Codex-5.3. For those who know my current architecture, I’ve been running Codex CLI in the backend to manage the OpenClaw instance on my Pi. Over time we’ve built it into a complete knowledge holder for everything related to OpenClaw, and that accumulated context is what made this change possible.&lt;/p&gt;
&lt;p&gt;&lt;img alt="image.png" loading="lazy" src="https://michaelguoblog.vercel.app/images/posts/openclaw-agent-team-0.png"&gt;&lt;/p&gt;
&lt;p&gt;I had a single strong agent running KOL and content execution, and it worked well. The strain started when I pushed it beyond that scope. Content strategy, software architecture, and private daily support were all forced to share the same brain.&lt;/p&gt;</description></item></channel></rss>