@thewaifu/dsh-token-factory

Use HelixToken managed models and points directly in the DeepSeek Harness WebUI.

TokenFactory adds passwordless device authorization, a HelixToken provider on the native Models page, and a Personal Center for account status, points, model availability, usage, and authorized devices. You do not need to enter a personal DeepSeek API key, and your existing providers remain available.

What You Get

• Passwordless HelixToken authorization from Settings -> Models
• A clear account state badge, current points balance, and welcome-points badge
• Only the HelixToken models currently available to your account
• Recent model usage and point consumption
• Authorized-device visibility and revocation controls
• Chinese and English UI that follows the Harness language setting
• Light, Dark, and System appearance support

Requirements

• Node.js ^22.19.0 or >=24.0.0
• DeepSeek Harness WebUI 0.1.2-rc.1 or a compatible newer release
• Internet access to the managed HelixToken service
• A modern desktop browser

Check Node.js before installing:

node --version

Install

Add TokenFactory to the Harness Web profile from the official npm registry:

dsh plugin --profile web add @thewaifu/dsh-token-factory --registry=https://registry.npmjs.org/

Start the WebUI:

dsh --profile web

Open the local address printed by Harness.

Authorize HelixToken

1. Open Settings in the Harness WebUI.
2. Select Models.
3. Find HelixToken above the DeepSeek provider.
4. Select Authorize.
5. Confirm the current device on the authorization page.
6. Return to Harness after approval.

Authorization is passwordless. TokenFactory never asks for your HelixToken password or personal DeepSeek API key. Reauthorizing the same device restores its account instead of creating a duplicate.

After authorization, the HelixToken row shows the account reference, Enabled state, current points, and welcome points. The status dot turns green, Personal Center becomes available, and supported models appear in the model selector.

Chat With A Model

Open the Harness model selector and choose an available tw-helixtoken model. The managed catalog currently supports these routes when enabled for your account:

• tw-helixtoken/deepseek-v4-flash
• tw-helixtoken/helix-cheap
• tw-helixtoken/helix-auto

The available list can change with service availability. TokenFactory does not replace your current default model automatically.

Older sessions may still reference a legacy helixtoken/... route. Select the matching tw-helixtoken/... model from the current model selector before continuing that session.

Personal Center

After authorization, open Personal Center from Harness Settings to view:

• Available, granted, used, and reserved points
• Models currently available to your account
• Recent model usage and point consumption
• Authorized devices and device revocation controls

Account status refreshes automatically while the WebUI is visible and refreshes immediately when you return to its browser window.

Update

Stop the WebUI, update the plugin, and start it again:

dsh plugin --profile web update @thewaifu/dsh-token-factory --registry=https://registry.npmjs.org/
dsh --profile web

Refresh the browser after Harness restarts. Use a hard refresh if an older interface is still cached.

Remove

Stop the WebUI and remove TokenFactory from the Web profile:

dsh plugin --profile web remove @thewaifu/dsh-token-factory

Removing the local plugin does not automatically delete the associated account or revoke other authorized devices. Revoke devices from Personal Center first when needed.

Troubleshooting

TokenFactory Is Missing From Settings

Check the Web profile:

dsh plugin --profile web list

The list must contain @thewaifu/dsh-token-factory. If it is missing, run the install command again and restart the WebUI.

The Interface Did Not Update

Stop the old dsh web process, update the plugin, restart Harness, and hard-refresh the browser page.

A Legacy Model Is Replaced Automatically

Routes beginning with helixtoken/ belong to an older provider identifier. Open the model selector and choose the current tw-helixtoken/... route explicitly.

Chat Ends With STREAM_CLOSED

First select a current tw-helixtoken/... route and retry in a new conversation. If the response still ends with SSE stream ended without [DONE], contact the service operator: the managed Gateway must normalize the upstream SSE terminator, and updating only the local plugin cannot repair that server-side stream.

Authorization Or Account Information Is Unavailable

Retry authorization after a short wait. If the issue persists, contact the service operator. Other configured model providers remain available during a temporary HelixToken service interruption.

Installation Reports EBADENGINE

Upgrade to Node.js 22.19.0 or later, or use Node.js 24, reopen the terminal, and install again.

Data And Security

• TokenFactory connects to the managed HelixToken service automatically.
• TokenFactory never asks for or stores your personal DeepSeek API key.
• Device credentials are stored through the DSH Credentials service, not browser local storage.
• Account, points, usage, device, and model-request data is sent to the HelixToken service when you use TokenFactory.
• Access tokens are short-lived and are not displayed in the interface.
• Service credentials and per-user upstream keys remain on the managed service and are not included in this package.

License

Licensed under the Apache License 2.0.