Tokenman中文

Subscriptions and quota

Claude OAuth subscriptions do not require an account UUID. The hub periodically reads the five-hour and seven-day windows for each credential. Importing the same token twice counts once; replacing a token under the same name waits for a new reading. Account association is optional, and imports never borrow the importing machine's login identity. A failed read shows its reason and the observation time of that credential's last reading; an unread credential shows no quota.

Sessions use a Claude or ChatGPT (Codex) subscription. A subscription's sign-in credential exists only in the hub; a machine is lent a short-lived copy, renewed as it runs out, and members can never read the long-lived credential.

Where subscriptions come from: either works

Use the subscription we provideConnect your own subscription
SuitsNot wanting to buy and manage subscriptionsAlready having Claude Pro / Max, ChatGPT Plus / Pro
Who adds it to the subscription poolUsYou
Self-hosted— (self-hosting has only your own subscriptions)You
HostedSay how many when the hub is opened, and we add themYou add them yourself, see below

They can be mixed: one subscription pool can hold both ours and your own. Every subscription is shown on the Subscription pool page, with the name of whoever it belongs to.

The subscription pool

The console's Admin → Subscription pool. One row per subscription: how much is left in each of its two quota windows (5 hours and 7 days), when they reset, who is using it, how many sessions, its state.

Adding a subscription

An admin selects Add subscription, chooses Claude Code or Codex and gives it a name (letters, digits, dots, hyphens and underscores). Everything stays in the browser:

The input is hidden and clears on submit or close. The server validates it before encrypted storage. No SSH, operator token or account UUID is needed.

The page returns the result directly and reads the initial quota. Retry network failures; a valid credential whose quota cannot yet be read shows Quota pending. Refresh quota in its details reads the backend again. Duplicate tokens return the existing subscription. To replace a credential under the same name, explicitly select Update credential in its details; replacement follows validation. An unconfirmed expiry is shown as Unknown.

Only vault credentials appear in the pool. Historical usage remains in usage reports. Personal subscriptions retain their owner and do not count toward shared capacity. Service and Plan are separate columns: Max shows 5× or 20× only with a known tier. Unknown plans show Unrecognized; details retain the raw value, source and known observation time. A name containing 20X is not evidence of a plan.

Members connect their own

Every member can connect their own Claude Pro / Max or ChatGPT Plus / Pro: Usage → "My own subscriptions" → Connect my own subscription → pick Claude or ChatGPT and name it → open the official sign-in page in their own browser, sign in and approve → paste back the code the page shows (Claude), or the whole address of the page it lands on that won't load (ChatGPT). The account's password is typed only on the provider's page; it never passes through the hub.

Who may use which subscription

An added subscription is not given to everyone automatically. New users and new machines may use no subscription at all by default; grant them explicitly:

What a person can finally use = the subscription pool ∩ what that machine is granted ∩ what that person is granted. A change takes effect within 30 seconds. Check a user’s access on a service node shows directly which subscriptions someone can use on a given machine.

A subscription needs a new login, pausing, removing

Per-person quota

Give a person two limits, for 5 hours and for 7 days (in tokens; write 200k, 2M). What counts is input + cache writes + output; cache reads do not count. Past the limit, their next request is refused and the session shows:

已达个人额度：近 5 小时已用 X / 上限 Y token，约 N 后恢复（额度由管理员设置） (personal limit reached: X of Y tokens used in the last 5 hours, back in about N; the limit is set by an admin)

Only that person is affected; everyone else carries on. As the window rolls on it lifts by itself — nothing for you to do.

Limits are set on the command line (today the web can show them but not set them):

fleet hub accounts                                          # find their identity id, like gh:1234567
fleet hub set fleet.person_budget.gh:1234567 "5h=200k,week=2M"
fleet hub set fleet.person_budget.gh:1234567 "week=2M"      # 7 days only
fleet hub unset fleet.person_budget.gh:1234567              # no limit

Self-hosted, with the operator token, fleet config budget works too: with no argument it lists each person's usage and limit; fleet config budget gh:1234567 5h=200k week=2M sets one, … off removes it.

Quota is counted only when a session goes through the credential proxy. On hosted machines it is on for every account by default; on a self-hosted machine an admin runs fleet cred-proxy enable --machine once — every account becomes a tenant of the machine's one proxy. An account not on it is neither counted nor stopped.

A new member's trial limits

A person let in through an approved request starts with trial limits: 7 days, 3M tokens of the shared pool (counted like a person's limit: input + cache write + output, a cache read not counted), and 1 session at a time. Past the end or the tokens, their next request is refused and their session says which ("试用期已于 … 结束" / "试用额度已用完"); a start past the session count is refused with the reason.

They see it themselves at the top of the console and the chat — "Trial · 6 days left · 120k / 3M tokens · 1 session at a time" — coloured within a day of the end or at 80% used; ended or used up, it says why and offers "Ask to become a member" — while the trial runs normally, the Usage page carries a quiet one under the limit card too. Asking marks their row in the admin's People list and tells every admin once (WeChat if they follow the service account, else mail), tapping through to that person in People, where one button makes them a member. Admins see each person's trial limits and usage in People, and change them or make the person a member from the row.

Trial QR codes: scan, follow, try

Trial QR codes, under People in the admin console: make a code — a channel name (only admins see it), the trial plan (fleet.apply.trial above by default, changeable), how many people it gives a trial at most (200 by default, 0 = no cap), until when, and whether it needs approval (no by default). Two kinds: permanent (the default; never expires, stopped from here — the service account holds 100,000 in all, shared with the company's other products) and temporary (at most 30 days, then void). Download the picture as soon as it is made, for a poster, a slide or a group chat. To send it to a friend as it is, Make a poster beside the code (or Poster in its row): one 1080×1440 picture with the code, the product in a line, the trial it gives and three steps to start, in 中文 or English; on a phone long-press it to save or forward, on a computer Download PNG.

The website's scan card takes its code from here too: make one with the channel site and no approval, and the front page shows it (its scans land in that code's funnel); with none, the front page draws its own as before.

Someone scans it with WeChat and follows the service account (one already following just scans), and the account answers at once with a "Your trial is on" card; tapping it opens the chat inside WeChat — no sign-in, no request. They are on the list like a person approved from "Ask to use", with this code's trial limits and subscriptions; the request record says this code approved it.

Each code is a row: given / cap, the funnel scan › follow › start › first line › member, its state; on top, the last 7 days' totals and the median time from scan to first line. Open a code to see who it reached; stop one person in People as usual.

Seeing who used how much