Unclaimed self-hosted deployments get a one-time browser claim to bootstrap the first admin
What this changes for operators
- Operators standing up a private self-hosted deployment now have a defined bootstrap path to create the first admin before any invite exists, replacing ad-hoc seeding.
- Whoever completes the one-time browser claim becomes the first admin, so an operator must claim a freshly deployed instance promptly to avoid a race for control.
- This changes the deployment runbook: the claim step is now the gate that establishes ownership of the control plane.
Signal metadata
Source findings
- Paperclip v2026.529.0 - Inline annotations, skills CLI, sidebar controls, self-hosted admin flow, and live model discovery 2026-05-29-paperclip-v2026.529.0
Run: 2026-06-03-weekly-digest-2026-05-28_2026-06-03-frontier-v0
Schema: bitter.frontier_signals.v0 / ID: 2026-06-03-paperclip-first-admin-claim-flow
Research evidence and publication history are open in the repository.