<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Tejas Rahane</title>
    <description>The latest articles on DEV Community by Tejas Rahane (@tejas_rahane).</description>
    <link>https://dev.to/tejas_rahane</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4156454%2F8ebe5ce3-b69d-4bea-b870-6a3a6b78b6b3.png</url>
      <title>DEV Community: Tejas Rahane</title>
      <link>https://dev.to/tejas_rahane</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/tejas_rahane"/>
    <language>en</language>
    <item>
      <title>multi-agentic system</title>
      <dc:creator>Tejas Rahane</dc:creator>
      <pubDate>Sun, 11 Oct 2026 08:09:54 +0000</pubDate>
      <link>https://dev.to/tejas_rahane/multi-agentic-system-eei</link>
      <guid>https://dev.to/tejas_rahane/multi-agentic-system-eei</guid>
      <description>&lt;p&gt;&lt;em&gt;This post is my submission for &lt;a href="https://dev.to/deved/build-multi-agent-systems"&gt;DEV Education Track: Build Multi-Agent Systems with ADK&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;p&gt;A distributed multi-agent system that researches a topic, has the research&lt;br&gt;
critiqued, loops until an editor approves it, then writes a course module.&lt;br&gt;
The Agent Development Kit and the Agent-to-Agent protocol are both open source,&lt;br&gt;
so the multi-agent design itself is unchanged — three agents still run as&lt;br&gt;
independent HTTP services that discover each other through A2A agent cards.&lt;/p&gt;
&lt;h2&gt;
  
  
  Cloud Run Embed
&lt;/h2&gt;


&lt;h2&gt;
  
  
  Your Agents
&lt;/h2&gt;



&lt;p&gt;The Agent Development Kit and the Agent-to-Agent protocol are both open source,&lt;br&gt;
so the multi-agent design itself is unchanged — three agents still run as&lt;br&gt;
independent HTTP services that discover each other through A2A agent cards.&lt;/p&gt;

&lt;p&gt;This starts the three A2A servers, waits for their agent cards, runs the&lt;br&gt;
pipeline, writes results to &lt;code&gt;output/&lt;/code&gt;, and shuts the servers down.&lt;/p&gt;

&lt;p&gt;The codelab ships a browser front end; this is the local equivalent. One command&lt;br&gt;
brings up the whole system — the web process starts the three A2A servers on&lt;br&gt;
launch and stops them on exit, so there is nothing else to run:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;.venv&lt;span class="se"&gt;\S&lt;/span&gt;cripts&lt;span class="se"&gt;\p&lt;/span&gt;ython.exe scripts&lt;span class="se"&gt;\r&lt;/span&gt;un_web.py        &lt;span class="c"&gt;# then open http://localhost:8080&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Type a topic and press &lt;strong&gt;Build the course&lt;/strong&gt;. The page shows the three agents as a&lt;br&gt;
live pipeline diagram: each box is a separate process, and it lights up as its&lt;br&gt;
A2A reply arrives — &lt;code&gt;researcher&lt;/code&gt; researching → done, &lt;code&gt;judge&lt;/code&gt; reviewing → approved&lt;br&gt;
(or looping the researcher back for another pass), &lt;code&gt;content_builder&lt;/code&gt; writing →&lt;br&gt;
done. An event log timestamps each step, and the finished module renders as&lt;br&gt;
formatted markdown in the "paper" pane on the right.&lt;/p&gt;

&lt;p&gt;Progress is pushed to the browser over Server-Sent Events&lt;br&gt;
(&lt;code&gt;GET /api/runs/{id}/events&lt;/code&gt;); a 5-second poll for the finished document is the&lt;br&gt;
fallback if the stream hiccups. The same backend the CLI uses drives it, so a run&lt;br&gt;
here is identical to &lt;code&gt;run_all.py&lt;/code&gt; — it just does not write to &lt;code&gt;output/&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Other endpoints: &lt;code&gt;GET /api/health&lt;/code&gt; (model + which agent cards are up) and&lt;br&gt;
&lt;code&gt;POST /api/runs&lt;/code&gt; (start a run, returns &lt;code&gt;{"run_id": ...}&lt;/code&gt;).&lt;/p&gt;

&lt;h2&gt;
  
  
  Key Learnings
&lt;/h2&gt;

</description>
      <category>agents</category>
      <category>buildmultiagents</category>
      <category>gemini</category>
      <category>adk</category>
    </item>
    <item>
      <title>multi-agent system</title>
      <dc:creator>Tejas Rahane</dc:creator>
      <pubDate>Sun, 11 Oct 2026 08:05:24 +0000</pubDate>
      <link>https://dev.to/tejas_rahane/multi-agent-system-2edm</link>
      <guid>https://dev.to/tejas_rahane/multi-agent-system-2edm</guid>
      <description>&lt;p&gt;&lt;em&gt;This post is my submission for &lt;a href="https://dev.to/deved/build-multi-agent-systems"&gt;DEV Education Track: Build Multi-Agent Systems with ADK&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;h2&gt;
  
  
  Cloud Run Embed
&lt;/h2&gt;

&lt;h2&gt;
  
  
  Your Agents
&lt;/h2&gt;

&lt;h2&gt;
  
  
  Key Learnings
&lt;/h2&gt;

</description>
      <category>agents</category>
      <category>buildmultiagents</category>
      <category>gemini</category>
      <category>adk</category>
    </item>
  </channel>
</rss>
