<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Multi-Agent on DevOpsTales</title>
    <link>https://devopstales.github.io/tags/multi-agent/</link>
    <description>Recent content in Multi-Agent on DevOpsTales</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Thu, 17 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://devopstales.github.io/tags/multi-agent/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Multi-Agent Orchestration Patterns: Six Topologies and How Each Breaks</title>
      <link>https://devopstales.github.io/ai/multi-agent-orchestration-patterns/</link>
      <pubDate>Thu, 17 Sep 2026 00:00:00 +0000</pubDate>
      
      <guid>https://devopstales.github.io/ai/multi-agent-orchestration-patterns/</guid>
      <description>Single-agent systems peaked with bounded tasks and one prompt. Production moved on: organizations now run double-digit agent counts, and a large share of multi-agent pilots die within months of deployment. The killer isn&rsquo;t the idea — it&rsquo;s picking the wrong coordination topology, or the right one without knowing its failure modes.
</description>
      <enclosure url="https://devopstales.github.io/img/multi-agent-orchestration-patterns-icon.webp" length="5948" type="image/png" />
    </item>
    
  </channel>
</rss>
