Foreword

When running multiple conversations and switching between different Providers in DeepSeek Harness (DSH), the balance, token consumption for the current session, peak/off-peak billing periods, and background task status are often scattered across different pages. To confirm “how much balance is left,” “how much this conversation has cost,” or “if it’s currently peak pricing,” you typically have to interrupt your current workflow to check elsewhere.

The DeepSeek Harness Control Center (npm package name: deepseek-harness-wallet) introduced below is a locally-prioritized DSH client plugin developed by community maintainer feibi-mochi. It consolidates balance monitoring, usage estimation, peak/off-peak clock, multi-account switching, completion reminders, and recharge options next to the input box, allowing you to grasp account status without leaving the current conversation.

What Is This

The Control Center is a client plugin (category: Client) in the DSH ecosystem. The current stable version on GitHub and npm is v0.3.4, licensed under MIT.

One-line positioning: A local control center next to the DSH conversation interface that provides balance, usage, peak/off-peak billing, encrypted multi-account, health checks, reminders, recharge, and session control.

It has no affiliation with the official DeepSeek platform; plugin data is stored locally and does not store prompts or response content.

Core Features

Balance and Session Usage

The plugin displays a compact label next to the input box, typically in the following form:

Balance ¥5.89 · Session ¥0.72 · Official 18.8M | Third-party 800K · ↗Recharge
  • Official DeepSeek: Refreshes balance every 60 seconds (with quick retry on startup) and estimates current session costs. Costs are locked in at the price when each usage occurs, supporting the v4 peak/off-peak pricing implemented from 2026-08-17.
  • Third-party Providers: Only tracks session tokens (input/cache read/output), with no balance guessing or cost conversion, requiring zero configuration.
  • Provider Bucketing: The settings page lists observed wrapper routes; once checked, subsequent calls are counted into the official token/cost bucket, but existing historical data is not retroactively re-bucketed.

Clicking the label opens a detail panel to view balance breakdown by currency, token details, manual refresh, and jump to the official recharge page (the first click shows the domain for confirmation to prevent phishing).

v4 Peak/Off-Peak Billing Clock

The sidebar provides a 24-hour circular clock for v4-flash, v4-pro, and v4-flash-vision-exp:

  • Weekday peak: Beijing time 09:00–12:00, 14:00–18:00
  • Saturday and Sunday are billed at off-peak rates all day (starting from 2026-08-23)
  • After Friday 18:00, it previews “weekend all-day off-peak”; before Monday 09:00, it shows the remaining time until peak hours

The plugin periodically syncs with the official pricing page, and only price lists that pass full validation are applied; if the network fails, the last verified rules are used.

365-Day Local Usage Ledger

Starting from v0.3.2, local usage events are collected and retained for up to 365 days. Stable request identifiers are deduplicated, official costs are locked in at the time of occurrence, official and third-party data are stored separately, and prompts or response content are not saved. The wallet settings page displays a heatmap by default; “Clear this session’s wallet data” only clears the current conversation records and is separate from “Clear historical ledger.”

Multi-Account Encrypted Switching

In the wallet panel → Account Management, add accounts (name + API Key), switch, or delete:

  1. The first added account automatically becomes the current account and synchronizes to the DSH credential store.
  2. A confirmation dialog appears before switching—because subsequent LLM requests will be billed under the new account.
  3. Switching writes to the credential store via credentials.set('DEEPSEEK_API_KEY', ...), and the llm-deepseek route resolves per request, using the new account on the next LLM call without requiring a restart.
  4. Account keys are encrypted and stored in $DSH_HOME/storages/accounts.json: Windows uses DPAPI, other platforms use AES-GCM key files with owner-only access. The interface only displays masked keys.

If the startup environment already provides the DEEPSEEK_API_KEY environment variable, switching is rejected; you need to unset this variable in the shell before enabling multi-account switching.

Z.ai Coding Plan Monitoring

Monitors configured global and China-region plans through a generic official plan adapter without exposing credentials to the browser. The 5-hour model token window and monthly MCP tool quota are displayed separately, with remaining ratios as primary indicators; if queries fail, the last successful snapshot is retained, and plan quotas are not converted to RMB balance.

Reminders, Layout, and Session Control

  • Conversation Completion Reminder: Optional persistent or timed auto-off; deduplicates and queues when multiple conversations complete simultaneously, coordinates across tabs; uses in-page alerts when system notifications are unavailable.
  • Low Balance Reminder: When below the threshold, the label turns red and triggers a desktop notification once; automatically resets when balance recovers. Thresholds are persisted per account and currency to two decimal places, with no cross-currency comparison.
  • Movement and Scaling: Labels can be freely dragged and snapped, switched between horizontal/vertical layouts, with scaling from 100%–125%; the detail panel can detach as a floating window or minimize to a dot.
  • Optional Permanent Deletion: Only enabled if the DSH host truly provides session deletion capability; users can enable it in settings; remains disabled in unsupported environments.

Installation and Enabling

Install from npm (current stable version v0.3.4):

dsh plugin --profile web add deepseek-harness-wallet

Or install directly from GitHub main source:

dsh plugin --profile web add github:feibi-mochi/deepseek-harness-control-center

After installation, restart dsh web and force-refresh the page.

Updating and uninstalling:

dsh plugin --profile web update deepseek-harness-wallet
dsh plugin --profile web remove deepseek-harness-wallet

The package name changed from dsh-wallet to deepseek-harness-wallet in v0.1.1. If you previously installed the old package name, first run dsh plugin --profile web remove dsh-wallet to avoid having two copies registering UI simultaneously.

Typical Usage

After completing the installation steps above, follow this process:

  1. Click the wallet card or peak/off-peak card to open the control panel; you can also view the health check card in Harness settings.
  2. Adjust the peak/off-peak card’s horizontal/vertical layout and 100%–120% scaling as needed; the wallet label is 100%–105% inside the input box and up to 125% when docked or floating.
  3. To shrink the card, you can disable the official recharge button; official and third-party data can be shown or hidden separately.
  4. Drag the card to a blank space; if you can’t find it after switching layouts, click “Reset/Dock” in the panel to restore it to the sidebar.
  5. When needing multiple accounts, open the wallet panel → Account Management, add name and API Key, and after confirming the switch, subsequent billing will be under the new account.

The card follows DSH’s light/dark theme; after upgrading the plugin, please force-refresh to ensure the new frontend version is loaded.

Applicable Scenarios and Notes

Suitable for:

  • Those who frequently use official DeepSeek or Z.ai Coding Plan in DSH and need to check balance and current session usage at any time
  • Those who need to switch between multiple DeepSeek accounts and want keys stored locally with encryption
  • Those using v4 models and want to reference peak/off-peak periods to control call costs
  • Those who want to receive reminders when conversations complete or notifications when balance falls below a threshold

Please note before use:

  • The plugin runs with the permissions of the current dsh process and sends the current API Key to the official /user/balance endpoint to query balance; after enabling multi-account switching, the selected key is also written to the DSH credential store for subsequent model requests. Before installation, you should read the source code and confirm the MIT license terms.
  • Session costs are locally estimated by the plugin, not official billing; the balance returned by the official API is authoritative.
  • The usage ledger collects data starting from v0.3.2; older aggregated data lacks reliable dates and will not be backfilled.
  • This version has been verified in real environments with Windows + Edge + DSH Web; other browsers and desktop shells are designed for compatibility based on capabilities, but this does not mean every combination has been tested on real devices.

Conclusion

DeepSeek Harness Control Center consolidates balance, usage, peak/off-peak billing, and account management next to the conversation, reducing the need to switch between multiple pages. If you frequently run long conversations or multi-account development in DSH, this plugin is worth trying.