Tag: subagents
Two of your agents never read your CLAUDE.md
Claude Code loads your CLAUDE.md into every subagent except two. Explore and Plan skip it by design, and no setting changes that. So the agents you fan out most widely are the ones that never see your rules. ETH Zurich measured what the file costs on the occasions it does load.
How the general-purpose agent works in Claude Code
The general-purpose agent in Claude Code is not the main agent and not something you pick. It is a built-in subagent Claude routes to on its own for complex, multi-step work. It inherits your model and, by default, runs in its own fresh context that Claude briefs with a short summary. This post explains how it actually works and what that costs you.
The built-in agent types in Claude Code
Claude Code ships with five built-in agent types: Explore, Plan, general-purpose, statusline-setup, and claude-code-guide. Most people know two of them. The other three run constantly and shape how much your sessions cost. This is the full catalog, what each one is for, and why knowing them changes how you read your own terminal.
What is a subagent in Claude Code
A subagent in Claude Code is a specialized worker that runs in its own fresh, isolated context window, with its own tools and permissions, and reports back only a summary. It is how Claude does a noisy side task without flooding your main conversation. Here is what a subagent is, what file defines it, and when it earns its cost.
Subagent vs parallel agent vs skill in Claude Code
Subagent, parallel agent and skill get used as if they mean the same thing in Claude Code. They do not. A skill is reusable instructions that cost almost nothing until invoked. A subagent is delegated work in a fresh isolated context. Parallel agent is not a primitive at all. Picking the wrong one wastes tokens or floods your context.