moulds.ai
Workers

A worker runs the whole job — and asks before anything ships.

Not a chatbot, not a black-box automation: a multi-step AI teammate you spawn from a plain-English goal, gate with approvals, and audit call by call.

Multi-step

A worker isn't one prompt — it's a whole job broken into steps you can read: research, draft, check, send. Each step has its own status, inputs, and outputs.

Approval-gated

A worker runs with an approval step enforced in front of anything it sends — an email, a message, a send of any kind. That's a platform rule, not a convention: a worker without the gate can't be saved and won't run. The run parks at the gate and waits for your explicit approve. No approve, no send.

Auditable

Every run keeps its receipts: the step list, each step's output, and every single AI call — model, tokens, and the exact prompt and response.

How spawn works

From a plain-English goal to a working draft

A screen recording of the spawn flow, captured in production.

  1. 1

    Describe the job

    Type the goal in plain English — no flowcharts, no code. “Research five prospects a week and draft the outreach.” is enough.

  2. 2

    The composer drafts a worker

    It picks specialist agents from the catalog, wires them into steps, sets the schedule — and inserts approval gates before anything outbound.

  3. 3

    You review, then it runs

    Nothing runs until you approve the draft. From then on it works on schedule, parking at every gate for your explicit go-ahead.

Typing a plain-English goal into the Spawn a worker box on moulds.ai, then watching the composer work through its stages until a draft worker is ready to review.
Sped up — real run: 3m 53s · recorded Jul 2026