<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Huanxi OS on Miao Kong</title><link>https://miaok.ong/en/tags/huanxi-os/</link><description>Recent content in Huanxi OS on Miao Kong</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 30 Jun 2026 17:21:00 +0800</lastBuildDate><atom:link href="https://miaok.ong/en/tags/huanxi-os/index.xml" rel="self" type="application/rss+xml"/><item><title>From Loops to Teams: How My AI Assistant Became a Digital Workforce</title><link>https://miaok.ong/en/posts/huanxi-os-3-role-driven-loop-en/</link><pubDate>Tue, 30 Jun 2026 17:21:00 +0800</pubDate><guid>https://miaok.ong/en/posts/huanxi-os-3-role-driven-loop-en/</guid><description>&lt;p&gt;The first three OpenClaw essays already covered one full stage of the journey.&lt;/p&gt;
&lt;p&gt;The first one, &lt;em&gt;To Build a Long-Lived AI Assistant, I Built Wheels for OpenClaw and Assembled a Coding Crew&lt;/em&gt;, was about survival: how to make an AI assistant stay alive over time — reset, recover, self-check, and use real tools.&lt;/p&gt;
&lt;p&gt;The second one, &lt;em&gt;When My AI Assistant Started Passing the Buck: The Brutal Truth of Multi-Agent Collaboration&lt;/em&gt;, was about the first layer of multi-agent pain: having multiple agents does not mean having a team. Without task briefs, isolation, verification, and boundaries, they simply break things together.&lt;/p&gt;</description></item></channel></rss>