<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>自动化运维 on Margrop Blog</title>
    <link>https://blog.margrop.net/en/tag/%E8%87%AA%E5%8A%A8%E5%8C%96%E8%BF%90%E7%BB%B4/</link>
    <description>Recent content in 自动化运维 on Margrop Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Thu, 19 Mar 2026 10:30:00 +0800</lastBuildDate>
    <atom:link href="https://blog.margrop.net/en/tag/%E8%87%AA%E5%8A%A8%E5%8C%96%E8%BF%90%E7%BB%B4/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>One Month with OpenClaw on MiniMax: Stable, Fast Enough, and Valuable Because It Lasts</title>
      <link>https://blog.margrop.net/en/post/minimax-openclaw-one-month-review/</link>
      <pubDate>Thu, 19 Mar 2026 10:30:00 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/minimax-openclaw-one-month-review/</guid>
      <description>&lt;p&gt;Over the past month, I have kept MiniMax as the primary model behind OpenClaw and used it across a full set of automation tasks: routine inspections, connectivity troubleshooting, health checks, security hardening, scheduled-task cleanup, and even blog writing support. Looking back, the biggest gain was not &amp;ldquo;how much work AI can replace,&amp;rdquo; but a more practical conclusion: for a system like OpenClaw that needs to run continuously, cooperate with tools, and handle a large amount of Chinese context, the most important thing is not raw benchmark strength. It is the balance between stability, response speed, integration cost, and long-term maintainability.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
