Orchestration examples

Concrete flows that show the coordination patterns in action, from a full app builder with browser QA down to the minimal orchestrator shape and the UI it feeds.

Example: app builder with browser QA

This is the pattern behind AI app-builder products. The user sees one task, but the orchestrator splits it across code, browser, and deployment agents.

Sandbox-first code agent

The code agent should build inside the sandbox rather than building locally and uploading only at the end.

get_or_create persistent sandbox
write files under /workspace
run install/build/test inside sandbox
start preview server
stream stdout/stderr to product UI
snapshot after meaningful progress
publish when verified

This is the loop that makes MIOSA useful for coding agents.

Computer QA agent

Use a computer agent when the output needs visual/browser inspection.

open preview URL
capture screenshot
click through navigation
fill a form
test login or signup
capture errors
return screenshot and findings to orchestrator

The browser agent should not edit code directly. It reports findings. The sandbox agent patches the code.

Minimal orchestrator shape

Product UI pattern

An orchestrated MIOSA product usually has three panels:

Good progress events include:

• plan created
• sandbox created or resumed
• file written
• command started
• stdout/stderr chunk
• command completed
• preview ready
• screenshot captured
• artifact created
• deployment started
• deployment ready

See also