<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Orchestration on homeio.org</title><link>https://homeio.org/tags/orchestration/</link><description>Recent content in Orchestration on homeio.org</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 27 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://homeio.org/tags/orchestration/feed.xml" rel="self" type="application/rss+xml"/><item><title>Claude orchestrating a swarm of Kimi workers: a day of autonomous refactoring</title><link>https://homeio.org/posts/2026/2026-05-27-claude-orchestrates-kimi-workers/</link><pubDate>Wed, 27 May 2026 00:00:00 +0000</pubDate><guid>https://homeio.org/posts/2026/2026-05-27-claude-orchestrates-kimi-workers/</guid><description>&lt;p&gt;For about a year I have been running Claude in the loop on a legacy C++ codebase — a port of an old strategy game to macOS Apple Silicon. The work is the kind that is not particularly hard but is &lt;em&gt;very tedious&lt;/em&gt;: untangling layered dependencies, ratcheting include counts down, deleting dead modules that nobody has compiled in twenty years. Claude is excellent at it, but Claude&amp;rsquo;s time is expensive, and a lot of the edits look more like substitutions than decisions.&lt;/p&gt;</description></item></channel></rss>