Account
Sign in to Sirloop
Manage your account access token and see which machines are currently relaying through your account.
Sign-in isn't configured yet
The owner hasn't finished setting up account sign-in on this
site. Nothing is broken — there's just no Supabase project wired
in yet. (Owner: see docs/auth-setup.md in the site
repo — not published here, it's a build-time runbook.)
Sign in
Sirloop accounts use your existing Google or GitHub identity — no new password.
Connect your terminal
Send your sign-in to the sirloop app running on this computer?
(port )
Connect your phone app
Continue to your sirloop phone app? This will sign in
.
Hand off your sign-in to the sirloop app on this device?
Signed in
Signed in as .
Account access token
This is your Supabase session access token — it
is account access, so treat it like a password.
It expires (Supabase's normal session lifetime) and you'll need
to copy a fresh one after it does. Set it as
SIRLOOP_ACCOUNT_TOKEN on a machine so
sirloop license --refresh can use it.
••••••••••••••••••••••••••••••••
Anyone with this token can act as your account. Never paste it into a chat, ticket, or untrusted script.
Active relay points
No relay is deployed yet
(RELAY_URL is empty in
js/auth-config.js), so there's nothing to show
here. This depends on the relay's GET
/account/rooms endpoint, which lands in a separate PR.
Your session expired. to refresh it.
The relay answered 404 — billing/accounts aren't enabled on that relay, so it has no room list to show.
Couldn't reach the relay
(). It may be down or
unreachable from here — try again shortly.
The relay answered with an unexpected error ().
No rooms registered to this account yet. Run
sirloop pair --publish on a desk and complete the
hand-off to register one.
| Room | Last seen |
|---|
Room ids only — the relay never learns machine labels (blind relay). Match a room to a machine on your phone, where the label was set at pairing time.