Reviewer participants

The idea

One worker owns the work; other workers review it once, read-only, and only useful points reach the owner, with the cost shown.

The problem
People relayed messages between agents by hand to get second opinions.
Why it matters
Several workers contribute to one task without a person relaying.
Where it stands
In production as of

A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.

  • Many workers on one WhatsApp number

    One business number serves the team: each worker signs its messages, the operator addresses workers by name, replies stick to the last speaker, updates batch under Meta pacing, and a worker can get its own number.

  • Internal knowledge first, then specialists

    A worker needs internal evidence before its first web search or question: a knowledge or memory read, a colleague's answer, or a recorded miss. After that it can consult read-only specialist sub-runs, search the web and, with approval, ask an outside expert.

  • Typed requests in every direction

    Workers and people ask each other typed questions (review, information, decision, help, handoff) peer to peer, up or down, with due times, defaults, redirects and an inbox.

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.