A thread you can test
Orchestration & Subagents
3 notes move from the word to a real choice at work — understand it first, then decide whether to use it.
Each note stands alone, or becomes the next step in this thread.
THE QUESTION THIS PAGE ANSWERS
ANSWER FIRSTWhat is Orchestration & Subagents, and which AI decisions does it change?
A sub-Agent is a capability seam — in-process, remote, or another product can plug in This page keeps the related concepts, common mistakes, and practical notes in one reading thread.
First decide whether you are blocked by a definition, a choice, or verification; then choose the closest of the 3 notes below.
Start with “Subagent Is a Seam: In-Process to Delegating Claude Code,” then restate the conclusion using your own task.
Do not treat every method in a topic as interchangeable. The answer changes with the input, risk, and acceptance bar.
THIS QUESTION THREAD
Put the word back inside the choice it changes.
Subagent Is a Seam: In-Process to Delegating Claude Code
A sub-Agent is a capability seam — in-process, remote, or another product can plug in
workflow / schedule / plan / todo: Orchestration Primitives
What each of the four orchestration primitives owns, and why they were never merged into one monolith
Skill, Preset, and Self-Modification
cordis_define lets an Agent rewrite its own runtime while running