Flows workflow logoFlows
Choose the Right Dispatch: Spawn, Fork, or Direct
0/4 steps0%

Step 1 of 4

Implement spawn: fresh context specialists

A spawn is a new employee: they know only what the dispatch tells them.

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule
Build the spawn path. Maintain a registry of agent definitions (explorer, planner, verifier, general) each with: its own system prompt, tool list, default model (cheap+fast for read-only scouts, inherit for reasoning-heavy roles), and permission mode. On dispatch: look up the definition, build a FRESH context containing only the definition's system prompt plus the dispatch message - no parent history. Assemble the child's tool pool independently under its own permission mode, not a copy of the parent's. Because the child starts from zero, enforce dispatch-prompt discipline: task, relevant background, constraints, expected output format - a checklist the orchestrator prompt requires. Return the child's final report as a tool result the parent folds into its context.
Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

Working spawn dispatch with per-definition prompts, tools, models, and fresh contexts.

Should NOT happen

  • An existing feature broke
  • A button only logs to console
  • Data disappears after refresh
  • Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Track what changed, failed, or needs follow-up. Notes export with the flow.

Made with Emergent