<?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 Bruce on AI Engineering</title><link>http://www.heyuan110.com/tags/multi-agent/</link><description>Recent content in Multi-Agent on Bruce on AI Engineering</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 02 Apr 2026 14:00:00 +0800</lastBuildDate><atom:link href="http://www.heyuan110.com/tags/multi-agent/index.xml" rel="self" type="application/rss+xml"/><item><title>OpenClaw Multi-Agent Setup: Stop Letting LLMs Orchestrate</title><link>http://www.heyuan110.com/posts/ai/2026-04-02-openclaw-multi-agent-setup-guide/</link><pubDate>Thu, 02 Apr 2026 14:00:00 +0800</pubDate><guid>http://www.heyuan110.com/posts/ai/2026-04-02-openclaw-multi-agent-setup-guide/</guid><description>&lt;p&gt;&lt;img src="http://www.heyuan110.com/posts/ai/2026-04-02-openclaw-multi-agent-setup-guide/cover.webp"
 alt="OpenClaw multi-agent setup guide covering binding routing, Lobster pipelines, and collaboration patterns"
 
 loading="lazy"
 decoding="async"
 fetchpriority="low"
 width="1200"
 height="630"
/&gt;
&lt;/p&gt;
&lt;p&gt;The biggest threat to your OpenClaw multi-agent system is not misconfiguration. It is &lt;strong&gt;letting LLMs handle orchestration&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;The typical setup looks elegant on paper: a Supervisor agent receives all messages, uses &lt;code&gt;sessions_send&lt;/code&gt; to delegate to specialist agents, collects results, and delivers a unified response. In practice, every routing decision is a full API call, every specialist reply-back is another, and a simple &amp;ldquo;write me a blog post&amp;rdquo; might trigger 6-8 API requests. Worse, without anti-recursion rules, agents can enter circular delegation loops. &lt;a href="https://cogentinfo.com/resources/when-ai-agents-collide-multi-agent-orchestration-failure-playbook-for-2026"&gt;Cogent&amp;rsquo;s failure playbook&lt;/a&gt; documents teams that &lt;strong&gt;burned thousands of dollars in minutes&lt;/strong&gt; from exactly this pattern.&lt;/p&gt;</description></item><item><title>GitHub Agent HQ: Multi-Agent Development Guide for VS Code</title><link>http://www.heyuan110.com/posts/ai/2026-03-13-github-agent-hq-vscode-guide/</link><pubDate>Fri, 13 Mar 2026 15:00:00 +0800</pubDate><guid>http://www.heyuan110.com/posts/ai/2026-03-13-github-agent-hq-vscode-guide/</guid><description>&lt;p&gt;&lt;img src="http://www.heyuan110.com/posts/ai/2026-03-13-github-agent-hq-vscode-guide/cover.webp"
 alt="GitHub Agent HQ multi-agent development dashboard showing Claude, Codex, and Copilot panels in VS Code"
 
 loading="lazy"
 decoding="async"
 fetchpriority="low"
 width="1200"
 height="630"
/&gt;
&lt;/p&gt;
&lt;p&gt;Running one AI coding agent is productive. Running three at the same time — comparing their approaches, playing to each one&amp;rsquo;s strengths, and picking the best output — changes how you build software entirely.&lt;/p&gt;
&lt;p&gt;GitHub Agent HQ makes this possible without leaving VS Code. Announced at GitHub Universe 2025 and launched in public preview in February 2026, Agent HQ lets you run &lt;a href="https://www.anthropic.com/"&gt;Anthropic Claude&lt;/a&gt;, &lt;a href="https://openai.com/index/codex/"&gt;OpenAI Codex&lt;/a&gt;, and &lt;a href="https://github.com/features/copilot"&gt;GitHub Copilot&lt;/a&gt; from a single interface. Think of it as a mission control for AI agents: you assign tasks, monitor progress, compare results, and merge the best solution — all without switching tools.&lt;/p&gt;</description></item><item><title>OpenClaw Multi-Agent Setup: Build AI Teams That Work</title><link>http://www.heyuan110.com/posts/ai/2026-03-05-openclaw-multi-agent-setup/</link><pubDate>Wed, 04 Mar 2026 19:00:00 +0800</pubDate><guid>http://www.heyuan110.com/posts/ai/2026-03-05-openclaw-multi-agent-setup/</guid><description>&lt;p&gt;&lt;img src="http://www.heyuan110.com/posts/ai/2026-03-05-openclaw-multi-agent-setup/cover.webp"
 alt="OpenClaw multi-agent setup guide showing AI team architecture"
 
 loading="lazy"
 decoding="async"
 fetchpriority="low"
 width="1200"
 height="630"
/&gt;
&lt;/p&gt;
&lt;p&gt;You built an OpenClaw personal assistant. It handles your Telegram messages, searches the web, writes drafts, reviews code. Life is good.&lt;/p&gt;
&lt;p&gt;Then reality hits. You ask it to research a competitor, and it responds with coding suggestions from yesterday&amp;rsquo;s conversation. You ask it to write an article, and it pulls in debugging context from a completely unrelated project. Your single agent is drowning in accumulated memory, and every response gets slower and more confused.&lt;/p&gt;</description></item><item><title>Claude Code Teams Guide 2026: Multi-Agent Setup &amp; Collaboration</title><link>http://www.heyuan110.com/posts/ai/2026-02-28-claude-code-teams-guide/</link><pubDate>Fri, 27 Feb 2026 10:00:00 +0800</pubDate><guid>http://www.heyuan110.com/posts/ai/2026-02-28-claude-code-teams-guide/</guid><description>&lt;p&gt;&lt;img src="http://www.heyuan110.com/posts/ai/2026-02-28-claude-code-teams-guide/cover.webp"
 alt="Claude Code Agent Teams multi-agent collaboration patterns"
 
 loading="lazy"
 decoding="async"
 fetchpriority="low"
 width="1200"
 height="630"
/&gt;
&lt;/p&gt;
&lt;p&gt;One agent is good. A coordinated team of agents is transformative.&lt;/p&gt;
&lt;p&gt;Since Anthropic released Agent Teams on February 5, 2026, alongside the Opus 4.6 model, &lt;a href="https://docs.anthropic.com/en/docs/claude-code"&gt;Claude Code&lt;/a&gt; has crossed a fundamental threshold: you&amp;rsquo;re no longer limited to a single agent working sequentially through your codebase. You can now spin up multiple Claude agents that communicate with each other, divide work, and execute tasks in parallel — like a small engineering team that happens to operate at machine speed.&lt;/p&gt;</description></item><item><title>Multi-Agent Orchestration: 4 Patterns That Actually Work</title><link>http://www.heyuan110.com/posts/ai/2026-02-26-multi-agent-orchestration/</link><pubDate>Thu, 26 Feb 2026 10:00:00 +0800</pubDate><guid>http://www.heyuan110.com/posts/ai/2026-02-26-multi-agent-orchestration/</guid><description>&lt;p&gt;&lt;img src="http://www.heyuan110.com/posts/ai/2026-02-26-multi-agent-orchestration/cover.webp"
 alt="Multi-agent orchestration patterns showing Pipeline, Router, Orchestrator-Worker, and Evaluator-Optimizer architectures for AI agent collaboration"
 
 loading="lazy"
 decoding="async"
 fetchpriority="low"
 width="1200"
 height="630"
/&gt;
&lt;/p&gt;
&lt;p&gt;A single AI agent can do impressive things — until it cannot. Give one agent a codebase with 200 files, a conversation history spanning 50 exchanges, and instructions that mix refactoring with testing with documentation, and you will watch it slowly fall apart. Responses drift. Costs spike. The agent starts &amp;ldquo;hallucinating&amp;rdquo; connections between unrelated parts of your project.&lt;/p&gt;</description></item><item><title>OpenClaw Multi-Agent Guide: Architecture, Configuration, and Collaboration Patterns</title><link>http://www.heyuan110.com/posts/ai/2026-02-23-openclaw-multi-agent-guide/</link><pubDate>Mon, 23 Feb 2026 17:00:00 +0800</pubDate><guid>http://www.heyuan110.com/posts/ai/2026-02-23-openclaw-multi-agent-guide/</guid><description>&lt;p&gt;&lt;img src="http://www.heyuan110.com/posts/ai/2026-02-23-openclaw-multi-agent-guide/cover.webp"
 alt="OpenClaw Multi-Agent Collaboration Architecture Guide Cover"
 
 loading="lazy"
 decoding="async"
 fetchpriority="low"
 width="1200"
 height="630"
/&gt;
&lt;/p&gt;
&lt;p&gt;Have you ever had this experience: your AI assistant starts &amp;ldquo;losing its mind&amp;rdquo; mid-conversation &amp;ndash; you ask it to write a blog post, and it suddenly spits out code logic; you ask it to research competitors, and it starts correcting typos from last week?&lt;/p&gt;
&lt;p&gt;The AI didn&amp;rsquo;t get dumber. You&amp;rsquo;re just making one &amp;ldquo;brain&amp;rdquo; do too many jobs. It&amp;rsquo;s like asking the front desk receptionist to also handle accounting, HR, and engineering &amp;ndash; nobody ends up doing anything well.&lt;/p&gt;</description></item><item><title>Claude Code Agent Teams 2026: Parallel Multi-Agent Development (With Cost Optimization)</title><link>http://www.heyuan110.com/posts/ai/2026-02-22-claude-code-agent-teams/</link><pubDate>Sun, 22 Feb 2026 08:00:00 +0800</pubDate><guid>http://www.heyuan110.com/posts/ai/2026-02-22-claude-code-agent-teams/</guid><description>&lt;p&gt;On February 5, Anthropic shipped &lt;strong&gt;Claude Code Agent Teams&lt;/strong&gt; alongside Claude Opus 4.6 — an experimental feature that lets multiple Claude Code instances form a team and work in parallel. If Subagents are errand runners you send out on focused tasks, Agent Teams are an engineering squad whose members can discuss, coordinate, and challenge each other in real time. For complex scenarios involving cross-module development, multi-perspective code review, or parallel debugging, Agent Teams can compress hours of serial work into minutes.&lt;/p&gt;</description></item></channel></rss>