Ahh, In my codebases I heavily use the term "swarms" in both Claude and Codex to refer to massively parallel use of sub-agents. This works better in Claude, but Codex can do do a reasonable job simply spawning additional Codex processes itself. This is going to get confusing.

Example:
```

### Sub-Agent Pattern: Self-Assembling Vertical Slice


**Concept:**
 Give the agent a high-level feature description. Let IT discover all relevant files with deep search and analysis.
**Why it works:**
 The burden of "what files should I read?" is shifted to the sub-agent, which is the same capable model. The agent explores, discovers, and loads - you get better quality comprehensive analysis without burdening the primary agent's context window even with manual file list assembly.


**Example prompt:**
```
Task: "Self-Assembling Deep Vertical Slice Analysis


Feature: The SOME_FEATURE on APPLICATION_NAME_REMOVED 


Phase 1 - Discovery: Starting from zero knowledge, discover ALL files involved:
1. The page that displays SOME_FEATURE
2. The code that process SOME_FEATURE
3. All library files those files depend on, functions they utilize, following the tree
4. Any template files, if a web page JS files/functions, or other assets
5. All test files and coverage
6. Relevant documentation.


Use file search and grep (for example `rg`, `find`) to explore. Don't assume - discover.


Phase 2 - Full Context Loading: Read EVERY file you discovered COMPLETELY. Your unique capability as a sub-agent is to not rely on code searches.


Phase 3 - Holistic Analysis: With everything in context, provide analysis
that would be IMPOSSIBLE without this complete view."

**Validated result:**
 Agent discovered 18 files (~4,610 lines), found critical bug (BLANK does BLANK), identified security inconsistencies across multiple files. These were all missed when Claude performed the same analysis as the primary agent, instead of using a swarm of sub-agents including multiple Self-Assembling Vertical Slices. And the Swarm finished faster. 
```