Flows workflow logoFlows
Streaming and Partial-Result UX
0/4 steps0%

Step 1 of 4

Design the event protocol

Streaming without structure is just faster confusion.

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

Prompt Capsule
Design a typed streaming event protocol for the agent. Event types to include: run_started {run_id}, text_delta {content}, tool_started {call_id, tool, args_summary}, tool_progress {call_id, note} (optional heartbeats), tool_finished {call_id, ok, result_summary}, turn_completed {turn}, run_completed {status, usage}, run_error {message}, run_cancelled {partial: bool}. Each event carries a sequence number and timestamp. Document the protocol in a schema file with versioning (v1). Decide the transport (SSE for one-way UI updates is the default choice) and justify it in one paragraph.
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 versioned, typed event protocol document.

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