Spawn Storm

Catches a burst of subagent starts so parallel Task fan-out cannot multiply cost and blast radius unnoticed.

Part of Behavior Guards. Thresholds are configurable in Console.

What it catches

• Many child agents started in a short window
• Not the same as tool-volume detectors (Tool Storm / Rate Budget)

Example

The agent “parallelizes” a migration by spawning many Task children at once. Each child opens tools and tokens. Spawn Storm warns, then asks or blocks further spawns.

Try it

Relay → Guards → Spawn Storm — Configure, use Sample / prompt tip, confirm the nested incident. Use Recommended Connect hooks so lifecycle events reach Relay.