<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>实践思考 on Miao Kong</title><link>https://miaok.ong/en/categories/%E5%AE%9E%E8%B7%B5%E6%80%9D%E8%80%83/</link><description>Recent content in 实践思考 on Miao Kong</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 10 Apr 2026 23:30:00 +0800</lastBuildDate><atom:link href="https://miaok.ong/en/categories/%E5%AE%9E%E8%B7%B5%E6%80%9D%E8%80%83/index.xml" rel="self" type="application/rss+xml"/><item><title>After building a long-term AI assistant, over the last three months, I've also turned OpenClaw into a Multi-Agent OS.</title><link>https://miaok.ong/en/posts/openclaw-3months-report/</link><pubDate>Fri, 10 Apr 2026 23:30:00 +0800</pubDate><guid>https://miaok.ong/en/posts/openclaw-3months-report/</guid><description>&lt;p&gt;Around the Chinese New Year, I wrote an article titled &amp;ldquo;Building a Long-Lasting AI Assistant: My OpenClaw Cloud Practices and Architectural Reflections.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;That article primarily addressed &amp;ldquo;how to survive.&amp;rdquo;
It wasn&amp;rsquo;t about how an AI assistant first amazed me, but rather how it stays online, doesn&amp;rsquo;t lose memory, and doesn&amp;rsquo;t pretend to understand during long-term use—how it gradually transforms from a conversational tool into a system that can truly operate for extended periods.&lt;/p&gt;</description></item></channel></rss>