Sign in and out of the hub from the client: the proxy answers t5de-proxy.local

A manager runs the hub connection, so signing in or out takes effect while the client runs; the client's T5DE settings page asks it for the status and to sign in (showing the code and opening the hub's page) or out. Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-29 19:18:14 -07:00
1 parent 5b4e44c4e7
commit 5eca0b57a6
@@ -56,7 +56,8 @@ leaves the machine.

 ## The hub

-`t5de-proxy signin [-hub URL]` signs the proxy in to T5DE's hub (git.t5de.dev/t5de/t5de-hub; URL is the hub's
+The client's Settings > T5DE page signs in and out (the proxy answers it at `http://t5de-proxy.local/hub`,
+`internal/control`). `t5de-proxy signin [-hub URL]` also signs the proxy in to T5DE's hub (git.t5de.dev/t5de/t5de-hub; URL is the hub's
 API): it shows a code to enter on the hub's website (`/device`, OAuth 2.0 device authorization) and saves the
 session token it gets in `%APPDATA%\T5DE\proxy\hub.json`, encrypted for the Windows user (DPAPI). From then on the
 running proxy keeps a WebSocket to the hub (`internal/hub`) with the token as a bearer token, reporting which IMVU