<?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 Systems on Vikas Mishra</title><link>https://vikasmishra.ai/tags/multi-agent-systems/</link><description>Recent content in Multi-Agent Systems on Vikas Mishra</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 08 Aug 2026 15:29:34 +0530</lastBuildDate><atom:link href="https://vikasmishra.ai/tags/multi-agent-systems/index.xml" rel="self" type="application/rss+xml"/><item><title>Agent Orchestration Is a Graph Problem, Not a Prompt Problem</title><link>https://vikasmishra.ai/blog/agent-orchestration-is-a-graph-problem/</link><pubDate>Sat, 08 Aug 2026 09:00:00 +0000</pubDate><guid>https://vikasmishra.ai/blog/agent-orchestration-is-a-graph-problem/</guid><description>&lt;p>Most multi-step agents I see in the wild have the same shape: a straight line. Step one, then step two, then step three, each one waiting for the previous one to finish before it starts.&lt;/p>
&lt;p>Here is the question almost nobody asks about that line: how many of those steps actually needed to wait?&lt;/p>
&lt;p>In my experience, usually less than half. The rest just queue, one job at a time, while the context window fills up with intermediate output and the agent slowly forgets what it was doing. When people tell me their agent is slow or unreliable, the model is rarely the problem. The problem is that they drew a line where the work was a graph.&lt;/p></description></item></channel></rss>