<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Subagents on The Coders Blog</title><link>https://thecodersblog.com/tag/subagents/</link><description>Recent content in Subagents on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 06 May 2026 22:26:28 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/tag/subagents/index.xml" rel="self" type="application/rss+xml"/><item><title>Google Dev: Subagents Arrive in Gemini CLI</title><link>https://thecodersblog.com/gemini-cli-subagents-2026/</link><pubDate>Wed, 06 May 2026 22:26:28 +0000</pubDate><guid>https://thecodersblog.com/gemini-cli-subagents-2026/</guid><description>&lt;p&gt;Ever felt like your AI assistant is juggling too many tasks, dropping the ball on context and delivering subpar results? That’s precisely the pain point Gemini CLI’s new subagents aim to obliterate. The struggle of managing complex, repetitive, or high-volume commands within a single AI interaction is finally being addressed, and it’s a game-changer for developers.&lt;/p&gt;
&lt;h3 id="the-context-rot-problem"&gt;The Context Rot Problem&lt;/h3&gt;
&lt;p&gt;Traditional AI CLIs often suffer from &amp;ldquo;context rot.&amp;rdquo; As you feed more information, more commands, and more complex instructions, the AI&amp;rsquo;s ability to recall and correctly act upon early parts of the conversation degrades. This leads to redundant explanations, missed details, and ultimately, wasted developer time. Imagine asking your AI to refactor a codebase, then add new features, then write tests – without proper delegation, the AI quickly gets overwhelmed.&lt;/p&gt;</description></item></channel></rss>