<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sub-Agents on Devops Monk</title><link>https://blog.devops-monk.com/tags/sub-agents/</link><description>Recent content in Sub-Agents on Devops Monk</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 05 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.devops-monk.com/tags/sub-agents/index.xml" rel="self" type="application/rss+xml"/><item><title>Claude Code Sub-Agents: Specialist Assistants and Delegation</title><link>https://blog.devops-monk.com/2026/06/claude-code-subagents-delegation/</link><pubDate>Fri, 05 Jun 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/06/claude-code-subagents-delegation/</guid><description>A sub-agent is a specialized Claude instance that runs in an isolated context window with its own allowed tools, memory, and instructions. While your main Claude session handles the conversation, a sub-agent spins up to handle a specific task — investigation, code review, security audit, testing — in parallel with your work.
Sub-agents excel at tasks that require:
Reading many files without cluttering main context Specialized expertise in one domain Fresh perspective (the agent isn&amp;rsquo;t biased by earlier conversation) Parallel execution (multiple agents working simultaneously) Sub-Agents vs Skills vs Hooks Before diving into sub-agents, understand the distinctions:</description></item></channel></rss>