<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>Qoder - Tag - Daily Deep Think</title>
        <link>https://blog.baifan.site/en/tags/qoder/</link>
        <description>Qoder - Tag - Daily Deep Think</description>
        <generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>blog@baifan.site (ByF)</managingEditor>
            <webMaster>blog@baifan.site (ByF)</webMaster><lastBuildDate>Tue, 03 Mar 2026 14:00:00 &#43;0800</lastBuildDate><atom:link href="https://blog.baifan.site/en/tags/qoder/" rel="self" type="application/rss+xml" /><item>
    <title>Multi-Agent Collaboration: Triggers, Topology, and Merging</title>
    <link>https://blog.baifan.site/en/multi-agent-collaboration-engineering/</link>
    <pubDate>Tue, 03 Mar 2026 14:00:00 &#43;0800</pubDate><author>
                    <name>ByF</name>
                </author><guid>https://blog.baifan.site/en/multi-agent-collaboration-engineering/</guid>
    <description><![CDATA[<div class="featured-image">
                <img src="/pictures/posts/multi-agent-collaboration-topology.svg" referrerpolicy="no-referrer">
            </div><p>Conclusion first: multi-agent collaboration is not &ldquo;spinning up a few more model instances.&rdquo; It has to solve task scheduling, context isolation, permission control, state management, and result merging — every one of which is an engineering problem, not a prompt problem.</p>
<!-- more -->
<p>The multi-agent stories on TikTok and Xiaohongshu usually go like this: one agent researches, one agent writes code, one agent runs tests, one agent does review, and the main agent collects results like a project manager. The comments: &ldquo;Whoa, that&rsquo;s insane.&rdquo;</p>]]></description>
</item>
</channel>
</rss>
