brief, plan, act, check
Every turn follows the same loop. The person stays in charge of anything that costs money, and the agent checks its own work before it answers.
The creative agent I build at Galleri5, inside G5 AI Studio. Give it a brief and it plans, generates and edits image, video and audio work, then checks what it made.
Every turn follows the same loop. The person stays in charge of anything that costs money, and the agent checks its own work before it answers.
Creative work does not fit in a quick chat reply. A turn can run for minutes while video renders, and in that time people change their minds, the context fills up, and generations fail after someone approved them. I designed MIRO's turns for that.
For production work, a chat reply is not enough. MIRO builds interactive apps right in the conversation: review boards to compare and approve shots, and production trackers that follow a plan step by step.
Before it answers, it looks at what the app actually rendered, so a broken screen gets caught by the agent instead of the person. Approvals are tracked across the work, so changing an approved step flags everything that was built on it.
Every turn is traced end to end, including the reason any tool call failed, and the tracing is designed so it can never break a turn. LLM judges label each traced turn's outcome and failure cause, so problems show up as numbers instead of anecdotes.
The content-safety check runs on a 600+ case eval suite that gates every push. Tuning it halved false positives, from about 8% to under 4%, while it still catches 98%+ of unsafe cases. Playbook selection has its own eval too.
Agents write code to do real work: process media, build documents, make charts. That code is untrusted by default. I built the sandbox it runs in from scratch, and it now handles 80K+ runs a month.
I also prototyped a lighter runtime (an unpacked root filesystem under bubblewrap with minimal capabilities) that cut cold start from 37 to 48 seconds down to 17.
Every job MIRO starts goes through the inference gateway I built from an empty repo: 190K+ jobs a month, 990K+ since launch, routed to 170+ model endpoints across fal, Replicate, Google, self-hosted H100s and others.
Before MIRO, I built AI Studio's canvas planner. It turned a brief into a plan of image, video and audio steps that people could see, edit, approve and run, and it checked every plan before anything was spent. A lot of what MIRO does well, like checking its work before showing it, started there.