Sub-Agent Delegation with Context Isolation
0/4 steps0%

Step 1 of 4

Specify the delegation contract

Isolation only works if the interface between agents is narrow and typed.

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

Prompt Capsule
Design the dispatch_agent tool contract. Input: a task prompt that must contain (a) the question or job, (b) the exact deliverable format (e.g. 'a list of file paths with one-line reasons'), and (c) what to do if the answer cannot be found. Output: a single report string plus metadata (turns used, tools called, truncated: bool). Rules: sub-agent receives its own system prompt describing it as a focused researcher; it gets read-only tools unless the parent explicitly grants more; depth limit 1; turn budget 10. Write this contract as the tool description the parent model will read.
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

A dispatch tool contract with deliverable-format requirements built in.

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