Connect an account
This page describes the optional subscription-engine interface. It requires ENGINES_ENABLED=1. In team mode, an administrator opens Manage subscription sign-ins from Connections; in legacy mode, accounts appear on Home. The default API-only setup uses provider connections instead.
An account is one subscription: a ChatGPT Plus, Pro or Business account; an X Premium, Premium+ or SuperGrok account for Grok Build; a Kimi Code subscription. You sign in on the vendor's own page. The console never sees your password.
The sign-in
- Press Connect in the subscription account view and pick the account type.
- Tick the box that says the subscription is yours. The sentence you agree to is recorded with the account, with its time.
- Open the link (or scan the code) and type the short code the dialog shows. Approve on the vendor's page.
- The dialog updates by itself. When the vendor confirms, the account is connected. In team mode, explicitly enroll the selected accounts as a gateway connection before minting team keys. Legacy mode can mint a personal key automatically after the first connection.
ChatGPT also offers a browser sign-in: pick it from the dialog when the device code does not suit you. The browser lands on an address starting with http://localhost:1455/auth/callback that may not load; paste that whole address into the dialog to finish.
One sign-in runs at a time per account type. A sign-in expires after fifteen minutes.
What is stored
- The vendor's sign-in token, held by the engine that serves the account: on disk, under the data directory, readable by the service user only.
- A masked email and the plan name when the vendor gives one.
- The consent sentence, its version and the time you agreed.
- The windows the vendor reports, as a short cache.
The console never stores your password and never asks for it.
Windows
Each account page shows the windows the vendor reports: for ChatGPT the short and the long window as the engine reads them from the vendor's usage endpoint; for Grok Build the current period; for Kimi Code the windows its usage endpoint lists. A window is shown as the percent left and the time it resets. When the vendor cannot be read, the page says so and keeps the last values with their time.
Pause, floor, use last
- Pause removes an account from the engine's available capacity. Requests need another eligible account to succeed.
- Floor applies to the ChatGPT account guard. It pauses an account below the configured remaining percentage. Empty means no floor; this is separate from team token allowances.
- Use last (ChatGPT only) makes the account serve only when no other ChatGPT account of yours is serving.
Sign in again
When the vendor asks for a fresh sign-in the account shows needs a new sign-in and pauses. Use Sign in again, then verify the account status and its gateway connection before returning it to the team's pool. Account identities and reauthentication behavior depend on the engine.
Disconnect
Disconnect deletes the token from the engine and from this server. The account's history stays in the console for the retention period. Review any enrolled connection that depended on the account; removing upstream capacity does not transfer a team key's permissions to another provider.
Health checks
With HEALTH_ENFORCE=1 the console watches each account's failed requests and pauses an account after four failed checks in a row, or at once when the credential is finished. With HEARTBEAT_ENABLED=1 it also checks each Grok Build and Kimi Code account on a read-only vendor endpoint, using a default per-account interval of 15 minutes. The scheduler wakes every minute to find due checks. Both optional controls are off by default.
Four rules hold whatever the setting: the console's own failure never counts against an account; a free account only proves that the token works; there is one score per account; a read is cached for a short time so the vendor is never hammered.