Device-code sign-in for the worker's tools

The idea

An admin signs the worker's gh or Codex in on its computer with the vendor's device code, which reaches only the admin and is never stored; the doctor signs a wrong account out.

The problem
Worker tools need their own vendor login without exposing it.
Why it matters
The worker uses its own account, and a wrong account is caught.
Where it stands
Built, off in production as of

Recorded evidence

  • Production · Released switched off; a production check found sign-ins refused
  • Local run on the real backend · Real gh and Codex device-code prompts on a real guest, then cancelled; no account signed in

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

  • One approval by a second person for the computer and its sites

    One approval by a second person (an owner, or an admin who did not issue the computer) binds the computer's install manifest and allowed hosts; onboarding runs as a resumable job with a doctor, snapshot and restore, and each added site needs another such approval.

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

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.