Owned worker lab

The idea

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.

The problem
Proving self-onboarding on real services would need real outside accounts.
Why it matters
After one approval the worker made its own forge account, confirmed it by mail and cloned the repo (30/30 gates).
Where it stands
Shown in a lab run as of

Recorded evidence

  • Local run on the real backend · 30 of 30 gates

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

  • Worker's own mailbox

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

  • 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.

  • Standalone autonomous AI employee

    A separate offering: one AI employee with its own private persistent computer and enrolled accounts that onboards itself, does a real engineering task alone and learns from owner corrections.

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.