Lancer des subagents dans Claude Code
Lance des subagents Claude Code pour recherche parallele, reviews isolees, fichiers d'agents custom et workflows agentiques plus propres.
Reponse rapide
Claude Code peut lancer des subagents via l'outil Agent. Utilise-les pour des sous-taches ciblees : recherche codebase, review, QA, securite ou analyse independante.
Meilleur cas d'usage
Lance des subagents quand le travail peut tourner en parallele ou quand tu veux un contexte isole. Donne a chaque subagent objectif, contexte repo, fichiers ou commandes a inspecter et format de sortie.
A eviter
Ne lance pas de subagents pour une commande, un travail vague ou une decision qui depend fortement de la conversation. Subagent driven bat inline execution seulement quand isolation ou parallelisme compensent le cout.
FAQ
Un subagent Claude Code peut-il lancer d'autres subagents ?
C'est possible, mais un seul niveau reste souvent plus propre. Les arbres multi-niveaux ajoutent du cout et reduisent la visibilite.
Quel premier subagent creer ?
Un subagent branch-readiness ou code-review est un bon premier choix : job etroit, verdict clair.
Lire le guide subagents
Guides associés
Claude Code Subagents: Parallel Agents
Learn when Claude Code subagents help, how to split parallel work, and how to configure a focused custom subagent without creating conflicts.
Subagents are useful when a task can be split cleanly: one agent searches the authentication code, another traces the database path, and the main conversation compares what they found. They add little to “read this file” or to work where every step depends on the same context. Short version: delegate independent research or a separate review when the results are worth the extra context and usage. Give each agent a narrow scope, the files or area to inspect, and a specific report format. Keep dependent work in the main conversation. If you want a step by step walkthrough of launching one, see the subagent spawning guide. Subagents can have their own instructions, tool access, and permissions. They start with a separate context, but by default work from the main conversation’s current directory. That means “separate context” does not necessarily mean “separate files.” If you want a repeatable checklist in the…
Lire le guideClaude Code Agents: When to Use Them
Claude Code Agents (subagents) let you spawn isolated work threads from the main session. Full guide: what they are, when to use them, how to write a custom one, and the patterns that actually ship.
Claude Code is great when you're driving one thread of work. When you need to run three threads in parallel, or want a fresh pair of eyes on a decision, or need to scope out a large refactor without polluting your main session that's what Agents are for. This is what Claude Code Agents actually are, when to use them, and how to write your own. What Claude Code Agents actually are An Agent (sometimes called a subagent) is an isolated work thread you spawn from the main Claude Code session via the Agent tool. It has its own context fresh, with no visibility into your conversation. You hand it a self contained prompt; it does the work; it returns a single message at the end. Three things make this different from just asking Claude another question: 1. Isolated context. The agent doesn't see what you've been doing. It can't…
Lire le guide