🔱

Claude Code Sub-agents Pattern

Self-ReportedAll claims are the subject's own. No external evidence is on record yet.Curated

Lead agent spawns specialist subagents in isolated context windows.

Curated from Claude Code Docs — Sub-agents — not claimed by or endorsed by the organization. Metrics cited only as the source states. Absent metrics render as [unknown].

Spec sheet

The benchmark fields — designed for comparison across teams.

Topology: Orchestrator–Worker
Agent count: 2
Platform: Claude Code
Industries: software-delivery
Task kinds: multi-file-codingresearchcontext-management
Trust tier: Self-ReportedAll claims are the subject's own. No external evidence is on record yet.
Proof entries: 1

Topology & roster

Orchestrator–Worker

Hub-and-spoke with context isolation. Lead agent coordinates and assigns work. Each subagent runs in its own context window and returns only a summary to the lead. Subagents only report results back to the main agent and cannot communicate with each other (vs. agent teams, which allow peer messaging).

🧑‍💻

Claude Code Lead AgentLead

🤖

Claude Code SubagentSubagent

Performance metrics

Windowed metrics with provenance. [unknown] means it was not tracked — an honest hole beats an invented figure.

Task success ratenot estimated

[unknown]

evidence-linkedwhy?

Claude Code subagent patterns — no published benchmark figures at time of indexing.

as of Jan 1, 2025

Token economics

Cost transparency is part of the honesty architecture. [unknown] means it was not tracked — not that it is zero.

No cost metrics on record. Cost tracking is hard across runtimes; honest absence beats invented figures.

Blueprint

Operational DNA — why it works, how it was built, and how it is overseen. Not files for sale; knowledge of the design.

Why it works

Context isolation keeps the main conversation clean and prevents token waste from exploration work. Tool allowlists on subagents enforce constraints mechanically. Cost routing (cheaper model for subagents) is documented as a first-class design pattern.

How it was built

Subagent definitions use custom system prompts and tool restrictions. Cost control: routing tasks to faster/cheaper models like Haiku for subagents. Each subagent definition has a description that Claude uses to decide when to delegate. Source: code.claude.com/docs/en/sub-agents.

Oversight model

Subagents can be constrained via tool allowlists (e.g., read-only access). Lead maintains control; subagent results are summarized back to lead context.

Proof (1)

The team's shared track record — tasks, incidents, lessons, milestones. Per-entry provenance tags are always visible.

ArtifactJun 1, 2025evidence-linked
Claude Code sub-agents documentation published
Official documentation describes subagent patterns, context isolation, tool allowlists, and cost routing to cheaper models.
https://code.claude.com/docs/en/sub-agents

Attestations (0)

Named third-party statements from people with first-hand experience. Attestations are what separates Peer-Attested from Evidence-Linked.

No attestations yet. Worked with this configuration or agent? Attest to it using the form below — attestations are named third-party statements and are what separates Peer-Attested from Evidence-Linked.