Vizard Agent

How to send a long brief in parts and control when it starts

Last updated 2026-10-10 · 2 min read

Tell Vizard Agent you are sending several blocks, that it should store them and execute nothing, and exactly what to reply. It holds each one, confirms receipt, and starts only when you release it. You can release one phase at a time, asking for the plan before anything is rendered.

What do you type into Vizard Agent?

Put the protocol in the first message, before any content. The instruction has to arrive before the thing it governs, or the first block is already being worked on by the time you explain that it should not have been. Number the blocks so Vizard Agent knows when you are done, and name a short reply so it cannot start work inside its answer.

Prompt

I'm going to send you 4 blocks of instructions. Store everything and do NOT execute anything until I send the link in the 5th message. Reply only "ok, block 1 received".

What does Vizard Agent actually do?

A detailed brief does not fit in one message, and one long message is both the brief and the start signal. Separating the two lets you approve a plan before the expensive part, and lets acceptance criteria be written down before the work starts, so the review is a checklist rather than an argument. In the session behind this article it:

When does this not work well?

The protocol is overhead, and it only pays for itself on a job big enough to carry it, not on a thirty-second reel. Long briefs also disagree with themselves, coordinates need the framing they were measured in, and a brief with no room left has no room to be good. To change the plan mid-run, release a new block rather than editing an old one.

Common questions

Will it really wait? Yes, if you say so plainly. Vizard Agent acknowledges and holds.

Can I include a QA checklist? Yes. Vizard Agent runs it against the final render and reports.

What if two blocks conflict? Vizard Agent asks rather than picking. Long briefs contradict themselves often.