Worker's own mailbox

The idea

A worker gets its own email account to sign up, confirm and sign in to sites by itself, with mail treated as outside content.

The problem
Self-onboarding into services needs an address the worker controls.
Why it matters
The worker creates and confirms its own accounts without a person's inbox.
Where it stands
Built, off in production as of

Recorded evidence

  • Local run on the real backend · Mailbox build evidence

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

  • Secrets used by reference

    Passwords, codes and captured tokens are stored as references; the platform fills or stages them into the guest and masks output, so no value reaches events, logs or model context.

  • Owned worker lab

    Lab infrastructure on the operator's Docker host, with a forge, a mail server and a lab CA, where a worker proves self-onboarding with no outside account.

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.