Skip to content
OperatorNest

Approvals before anything that matters

OperatorNest is an AI agent with human approval that researches, reads and drafts on its own and stops for your OK before anything that sends, pays, books, deletes or posts. Each stop arrives as one card in the channel you asked from, with Approve, Edit and Hold, and your decision is logged in the task's receipt.

How the work moves

  1. Starts when

    A task reaches a step that would change something outside your operator's workspace.

  2. Uses

    The draft, the booking or the payment it prepared, plus the reasons behind it.

  3. Asks you before

    Sending email or messages, paying, booking, deleting, publishing or accepting invites.

  4. You get

    A short approval card with what will happen, why, and Approve, Edit or Hold.

  5. On the record

    Your decision, the time, and exactly what ran afterwards, logged against the task.

On this page

An AI agent that asks before it acts

OperatorNest is an AI agent with human approval built into every task. It works on its own until it reaches a step that would change something in the outside world, then it stops and asks you. Research, reading, comparing and drafting happen in the background. Sending, paying, booking, deleting and posting wait for you.

You get the research and the drafts done for you, and you keep the final say on anything that leaves your operator’s workspace.

What an approval looks like

When your operator needs a decision, you get one short message in the place you asked from. It says what will happen, why, and what it prepared. For example:

Send 3 follow-up emails to Acme, Brackenwold Studio and Thornquist Ventures? Drafts are written in your tone. Nothing has been sent yet.

You can approve it as is, open it and edit the drafts, or put it on hold. If you edit, your operator learns from the change for next time.

Set the default for each action

Reading and drafting can continue without a card. An action that sends, books, spends, deletes or publishes waits, with the proposed change and its details in the card. Use the AI agent approval policy builder to write down the boundaries for your own tasks.

Action type Default What the approval card shows
Read or search Continue No approval card; the sources checked appear in the task receipt.
Draft Continue No approval card; the draft is ready for you to review.
Send a message Wait for approval Recipient, exact message, reason for sending, and Approve, Edit or Hold.
Book or schedule with others Wait for approval People involved, date and time, booking details, and Approve, Edit or Hold.
Pay or purchase Wait for approval Item, seller, amount and payment details, with Approve, Edit or Hold.
Delete Wait for approval The file or record affected, what will be removed, and Approve, Edit or Hold.
Publish Wait for approval Exact content, destination, audience and reason, with Approve, Edit or Hold.

Actions that always wait for you

Out of the box, your operator asks before it:

  • sends an email, message or invite in your name
  • pays for anything, or enters card details
  • books travel, tables or appointments
  • deletes, archives or overwrites files and records
  • publishes or posts anything publicly
  • accepts terms, contracts or meeting invitations

Everything else, like searching the web, reading documents you shared, comparing options, filling a spreadsheet or writing a draft, it does on its own and reports in the task’s receipt.

Set your own rules

Some approvals get repetitive. If you send the same invoice reminders every Monday, you can pre-approve that action for that task only. You can also go the other way and require approval for things that don’t normally need it, like any message to a specific client.

Rules are per task. Tightening a rule takes effect on the next step.

Approvals and always-on work

If a decision comes up at 2 a.m., your operator prepares everything, holds that one step, and moves on to the rest of the task. When you wake up, the decision is at the top of your morning brief. Nothing is sent or spent in the meantime.

Every decision is on the record

Each approval is stored in the task’s receipt: what was proposed, what you decided, when, and what ran afterwards. To check why an email went out or who approved a booking, open that task’s receipt.

Example run

Overnight press list

25 targets found, a verified list, 11 pitches sent by mid-morning

Illustrative: this shows how the flow works, not a captured screenshot of a live task. Rows are described generically; no real journalist is named.

Hand-off · Email, 22:50

Subject: Overnight: press and podcast list. Find 25 journalists, newsletter writers and podcast hosts who covered personal AI agents, Meta Muse, Grok Bot or AI assistants in the last 90 days. For each, verify on their own site or recent article: name, outlet, the specific piece, and the best public contact route. Put it in a spreadsheet. Then draft a tailored pitch for each that references their piece. Use my Claude key for the drafts. Hold everything for my review in the morning; send nothing.

Brief

25 targets, 22 verified, 3 dropped, 25 drafts waiting

Found 25 candidates who covered personal AI agents, Meta Muse, Grok Bot or AI assistants in the last 90 days. 22 verified against their own site or byline: for example, a reporter at a national tech outlet who covered the Meta Muse launch on 8 September; a newsletter writer who ran a piece comparing always-on AI agents in mid-September; a podcast host whose recent episode covered agent security concerns. 3 dropped: one had no outlet affiliation that could be verified, one had no public contact route beyond a general inbox already at capacity per their bio, one credited byline turned out to be a syndication, not the original piece. All 25 have a tailored draft waiting, written in your tone and referencing their specific piece.

Approval

Send the 11 approved pitches (8 as drafted, 3 edited)?

Each pitch, the piece it references, and the verified contact route. Podcast-host drafts were redone on GPT, shorter, at your request.

Nothing has been sent yet.

Decision: Approved 8 as drafted, edited 3 before approving, rejected 14. 11 sent starting at 08:30, spaced through the morning rather than all at once.

Timeline

  1. · Email

    Operator replies by email with the plan and an estimate. Nothing will be sent without your approval.

  2. · Browser · Gemini Flash

    Research across recent coverage of personal AI agents and the named competitors, 83 pages visited, checking each candidate on their own site or byline page.

  3. · Browser · Gemini Flash

    25 candidates found, 22 verified with a name, outlet, specific piece and public contact route. 3 dropped, with reasons, for lack of a verifiable outlet or contact route.

  4. · Files

    Spreadsheet written: name, outlet, piece (linked), contact route, why relevant, verified (y/n).

  5. · Claude

    25 tailored pitches drafted, each referencing the specific piece, in your tone from memory.

  6. · Email

    Brief sent: 25 targets, 22 verified, 3 dropped (reasons attached), 25 drafts waiting.

  7. · GPT

    You ask it to redo the podcast-host drafts on GPT, shorter. It switches model for those 6 drafts, keeping the same context and tone; the other 19 stay on Claude.

  8. · Email · Held for approval

    Approval card sent for the reviewed batch: 8 approved as drafted, 3 edited then approved, 14 rejected. Nothing sent yet.

  9. · Email

    11 approved pitches sent, spaced through the morning.

Receipt

Steps
9 recorded
Checked
83 pages visited; 25 candidates found, 22 verified, 3 dropped with reasons.
Models used, and whose key
  • Research and verification (overnight): Gemini Flash (default key)
  • Initial 25 drafts: Claude (your Claude key)
  • Podcast-host drafts, redone shorter: GPT (default key)
Sent
Nothing sent overnight. 11 pitches sent from 08:30, spaced through the morning; the other 14 held back.
Held
14 drafts (not approved) and the 3 dropped candidates, none of them pitched.

Common questions

What does my operator do without asking?

By default it researches, reads, compares, drafts and organizes on its own. Anything that sends, pays, books, deletes, publishes or accepts on your behalf waits for your approval.

Can I let it act without approval for some tasks?

Yes. You can pre-approve specific actions for a specific task, such as sending the Monday invoice reminders to the same list, and tighten or remove that permission at any time.

What happens if I don't respond?

Nothing is sent or spent. The task holds at the approval step, your operator reminds you once in the channel you asked from, and everything else it can do keeps moving.

Where do approvals show up?

In the channel you used to ask, such as WhatsApp, Slack, email or the web, and in your morning brief.

Hand off your first task tonight.

Tell us your email and what you'd hand off first. We'll send your access details and help you set up your operator.