Claude Code Sub Agents: Parallel AI Development

Anthropic's Claude Code now supports sub agents - specialized AI workers you can deploy for specific development tasks. Instead of cramming every instruction into a single system prompt, you build a team of focused agents, each with its own expertise, tools, and context.

This changes how you structure AI-assisted development. A frontend specialist handles your React components while a research agent fetches documentation. A debugging expert investigates logs while you stay focused on architecture. Each agent operates independently, equipped with exactly the capabilities it needs.

Creating Specialized Agents

Sub agents live in markdown files inside your project's .cloud/agents/ directory. To create one, type /agents in Claude Code, then choose whether the agent should be project-specific or global across your machine.

The configuration is straightforward. You define:

• Name and description: How Claude identifies when to invoke the agent
• Tool access: Which core Claude Code functions and MCP servers the agent can use
• System prompt: The expertise, coding standards, and behavioral biases for this specialist

For example, a frontend engineer agent might carry deep expertise in Next.js, Tailwind, and shadcn/ui. You grant it full file access, but restrict a database agent to SQL commands and log reading. A research agent gets only web search and scraping tools - no ability to modify your codebase.

The markdown format makes these configurations portable. Commit them to your repository, share them across teams, or iterate on system prompts over time as you discover what works.

Delegating with Context Isolation

The real power emerges when you delegate tasks across multiple agents simultaneously. Rather than forcing a single model context to switch between unrelated concerns - researching APIs, writing components, debugging tests - you spawn specialists for each domain.

In practice, this looks like parallel task execution. You might instruct Claude Code to build a landing page with dynamic content pulled from current AI news. The system spawns a research agent to search the web and extract relevant stories while a frontend agent begins scaffolding the Next.js application. The research agent returns its findings, and the frontend agent integrates them into the UI - each working within their optimized context window.

This isolation prevents context pollution. Your frontend agent does not need to know the details of how research was conducted - only the structured results. Your research agent does not need file system access to your application code. Each stays focused, reducing errors and improving output quality.

Practical Use Cases

Code Review Specialist
Configure an agent with strict linting rules, security checklists, and your team's style guide. Invoke it before commits to catch issues without cluttering your main development flow.

Documentation Writer
Equip an agent with your codebase and a template for your docs site. Task it with updating API references while you build new features.

Infrastructure Debugger
Grant an agent access to AWS CloudWatch, Kubernetes logs, or your deployment platform's MCP server. When production issues arise, it investigates telemetry while you assess architectural implications.

Integration Specialist
Working with a new framework not in the LLM's training data? Create an agent with web search and documentation scraping tools. It retrieves current API references and feeds accurate information to your implementation agents.

Configuration Best Practices

Keep system prompts explicit and scoped. Instead of vague instructions like "be helpful," specify exactly what the agent should and should not do. If you dislike certain patterns - gradient backgrounds, emoji-heavy output, verbose comments - state those constraints directly.

Use the tool selector ruthlessly. An agent with access to twenty unnecessary MCP servers will waste tokens and produce confused results. Give each agent the minimum viable toolset for its responsibility.

Start with project-specific agents for domain knowledge, then graduate reusable specialists to global agents. A well-tuned React component builder probably deserves system-wide availability. An agent customized for your internal API conventions should stay repository-local.

The Road Ahead

Sub agents represent a shift from monolithic AI assistance toward composable, multi-agent workflows. The markdown-based configuration makes these setups transparent and version-controlled. As MCP ecosystems expand - connecting Claude Code to Gmail, Linear, Figma, and hundreds of other tools - the specialization possibilities multiply.

The constraint is no longer what a single model can hold in context. It is how thoughtfully you can decompose your development workflow into discrete, delegable responsibilities.

---

Frequently Asked Questions

What are Claude Code sub agents?

Sub agents in Claude Code are specialized AI workers that you configure to handle specific development tasks. Each sub agent has its own system prompt, tool access, and context isolation. Instead of overloading a single AI with all responsibilities, you build a team of focused specialists - a frontend agent, a research agent, a debugging agent - each optimized for its domain.

How do I create a sub agent in Claude Code?

Type /agents in Claude Code to create a new agent. You can make it project-specific (stored in .cloud/agents/ in your repo) or global (available across all projects). The configuration is a markdown file where you define the agent's name, description, allowed tools, and system prompt with its expertise and behavioral constraints.

Can sub agents run in parallel?

Yes. Claude Code can spawn multiple sub agents simultaneously to work on different parts of a task. For example, a research agent can fetch documentation while a frontend agent scaffolds components. Each agent operates in its own context window, preventing one task's complexity from polluting another.

What tools can sub agents access?

You control which tools each sub agent can use. Options include core Claude Code functions (file operations, terminal commands), MCP servers (GitHub, databases, Slack), and web search capabilities. Best practice is to grant each agent the minimum toolset required for its job - a research agent gets web search but not file write access.

Are sub agent configurations version controlled?

Yes. Sub agent configurations are stored as markdown files in your project's .cloud/agents/ directory. You can commit them to Git, share them with your team, and iterate on system prompts over time. Global agents live outside your repo but can be exported and shared as well.

---

Watch the Video