<?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 korchasa@*ops</title><link>https://korchasa.dev/tags/orchestration/</link><description>Recent content in Orchestration on korchasa@*ops</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 28 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://korchasa.dev/tags/orchestration/index.xml" rel="self" type="application/rss+xml"/><item><title>Symphony — codex orchestrator from openai</title><link>https://korchasa.dev/posts/2026_04_28_symphony_orchestrator/</link><pubDate>Tue, 28 Apr 2026 00:00:00 +0000</pubDate><guid>https://korchasa.dev/posts/2026_04_28_symphony_orchestrator/</guid><description>&lt;p&gt;No worries, no worries. Soon they&amp;rsquo;ll add multi-agents and decouple from linear, just like in &lt;a href="https://github.com/korchasa/flowai-workflow" rel="nofollow noopener noreferrer external"&gt;flowai-workflow&lt;/a&gt; :) Although running different agents and ides for different stages still won&amp;rsquo;t work for them.&lt;/p&gt;
&lt;p&gt;Even isolated agents with self-checks can already close a fairly large percentage of tasks. Especially boring stuff like refactoring, documentation, tech-debt cleanup, and so on. The downside is the accumulation of unknowns in your own code, but that&amp;rsquo;s covered by:&lt;/p&gt;</description></item></channel></rss>