一句话定位

在 DSH Web 的输入框旁常驻一个迷你"钱包"标签，显示 DeepSeek 官方账户余额、本会话成本与三方 Token 用量，提供多账号一键切换、低余额提醒与官方充值入口。

核心能力

• 实时显示官方 DeepSeek 余额：60 秒自动刷新，启动时附加 2 / 6 / 15 / 30 秒梯次重试，未配置 API Key 时给出友好错误而非崩溃（index.js:35 / index.js:737-749）
• 本会话成本与 Token 分桶：监听宿主 llm/stream 事件，把输入 / 缓存读 / 缓存写 / 输出 / 推理 token 分别按官方 provider 和其它 provider 入账，每次用量锁定当时价，避免跨档位串台（index.js:710-731 / index.js:481-498）
• 24h 峰 / 谷计费分时钟：侧边栏底部环形钟实时展示北京时区高峰（09:00–12:00、14:00–18:00）与低谷半价时段，含切换倒计时与可选的桌面系统通知（index.js:41-43 / CHANGELOG.md:7-10）
• 多账号管理与热切换：在面板「账户管理」添加多个 DeepSeek 账号（名称 + API Key），切换后无需重启，下一次 LLM 请求即按新账号计费；UI 只显示掩码后的 Key（index.js:435-451 / README.md:39-44）
• 防钓鱼的官方充值入口：标签右侧"↗充"按钮直接打开 https://platform.deepseek.com/top_up，URL 在代码里硬编码不可改，首次点击会弹窗确认域名（index.js:28 / README.md:138）
• 标签支持拖拽停靠、缩放与浮动窗口：可在输入框旁、悬浮、侧边停靠三种模式间拖动，停靠位置与缩放比例会持久化；面板可剥离为可拖动浮动窗，进一步最小化为可移动的圆点（lib/client.js:1965-2099 / CHANGELOG.md:38-44）
• 完成提醒与峰 / 谷切换桌面通知：对话完成时通过宿主通知通道弹窗，可选常驻或定时关闭；不支持系统通知时降级为页内通知（lib/client.js:715-755 / README.md:31）

技术实现

• 语言: JavaScript（ESM）：index.js 是 host half，lib/client.js 是 client half（package.json:5 / package.json:6-11）
• 关键依赖: 零第三方运行时依赖；仅使用 Node 内置 node:crypto / node:fs / node:os，浏览器侧通过 React（由 DSH Web 注入）渲染，CSS 变量全部走 --dsw-alias-* 主题（package.json:0 / index.js:19-22 / lib/client.js:262-310）
• 架构模式: 双半包宿主插件（dual half）。host half 通过 ctx.on('llm/stream', usageTap, { global: true }) 包裹模型流拦截 usage 块，按 provider 入账；ctx.webServer.register 暴露 /api/wallet/{snapshot,threshold,refresh,clear-session,accounts,accounts/activate,accounts/remove,official-providers} 共 8 个 JSON 路由；client half 通过 window.__ModuleLoader__.load({ id: 'deepseek-harness-wallet', factory }) 把自己注册进页面，适配层 createCompatibilityAdapter() 统一抽象通知 / 存储 / 权限 / 外部链接 4 类宿主编配点（index.js:697-903 / lib/client.js:6-11 / lib/client.js:45-240）
• 入口文件: 服务端入口 index.js（apply / name = 'wallet'）；客户端入口 lib/client.js；挂载声明 cordis.patch.yml（在 web profile 插入 id=wallet，name=deepseek-harness-wallet）（cordis.patch.yml:1-4 / package.json:49-61）

适用场景

适合已经把 DeepSeek 作为主力模型、需要在每次会话时一眼看到官方余额、本场花费和三方 Token 消耗的人。它把原本散落在官方开放平台控制台、DSH 模型设置与会话详情里的费用信号统一收口到一个可拖动的小标签里，多人共用一台机器或多账号轮换计费时尤其有用。

前置依赖与兼容性

安装方式

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

配置项

本插件不读取宿主配置文件；所有用户级设置都通过面板内 UI 调整并即时落盘。下方为各设置的实际键名、作用与默认值（lib/client.js:18-35 / lib/client.js:1043-1140）：

常见问题

Q: 安装后标签（chip）不出现怎么办？

A: 必须先 dsh plugin --profile web add deepseek-harness-wallet，再 restart dsh web，最后在浏览器里硬刷新页面。客户端半包通过 window.__ModuleLoader__.load({ id: 'deepseek-harness-wallet' }) 注入，硬刷新是触发装载的必要条件。

Q: 余额为什么显示错误 / 没有数字？

A: 余额依赖 DEEPSEEK_API_KEY，没有或 key 失效时直接对官方 /user/balance 端点查询，key 只作为 Authorization 头离开本机。Token / 成本会计不依赖 key，仍可正常工作；只要在 DSH 模型设置里配上 key 或让账号管理添加，余额就会恢复。

Q: 三方模型会话为什么没有余额和成本，只有 Token？

A: 余额与官方价表只对接官方接口，三方 provider 没有官方价表也没有余额端点，所以只统计输入 / 缓存读 / 输出的 Token 量，不估算花费和余额。

Q: 怎么在多个 DeepSeek 账号之间切换？下次计费跟着谁？

A: 在面板"账户管理"里添加账号（名称 + API key），切换会写入凭据通道 credentials.set('DEEPSEEK_API_KEY', ...)。llm-deepseek 路由按请求解析该凭据，所以下一次 LLM 调用即按新账号计费，不需重启。如果环境变量里也设了 DEEPSEEK_API_KEY，凭据通道会拒绝覆写，切换会失败并提示。

Q: 充值链接地址可以换吗？

A: 不能。RECHARGE_URL = 'https://platform.deepseek.com/top_up' 在宿主侧硬编码，不可配置——这是有意做的防钓鱼措施。首次点击会弹窗确认域名。

Q: "永久删除会话"开关是灰的，怎么开？

A: 这是宿主能力，非插件可独立实现。它要求宿主 DSH 真正实现了会话删除路径并向客户端广播 data-dshw-capability-permanent-delete='true'；当前官方发行版没有此能力，所以开关保持禁用。如果你是宿主开发者，参考 integrations/dsh-session-delete/ 套件把能力接上即可。

Q: 数据存到哪里？清除本会话数据会不会删掉对话？

A: 钱包数据存到 $DSH_HOME/storages/wallet.json，账号存到 $DSH_HOME/storages/accounts.json，UI 内显示内容 / 缩放 / 布局等存在浏览器 localStorage。"清除本会话数据"只清掉当前会话的 token / 成本计数，不会删聊天和会话本身。

Q: 机器上装了旧版 dsh-wallet，怎么清理？

A: dsh-wallet 在 0.1.1 改名为 deepseek-harness-wallet，老包不卸载会和新包重复占同一行 UI。执行 dsh plugin --profile web remove dsh-wallet 后重启 dsh web 即可。

Q: 会话成本（¥/$）看起来不太准？

A: 成本是按每次用量事件落到价格表时的"当时价"逐次估价的：v4 模型自带峰 / 谷两档（北京时间 09:00–12:00 与 14:00–18:00 为高峰，谷价为高峰一半），历史调用的计费不会被新价覆盖。官方接口返回的余额是权威值，估价仅作参考。

上手难度

入门 — 一条 dsh plugin add + 重启 dsh web + 硬刷新即在输入框旁看到标签；想用多账号或自定义阈值时进入面板"账户管理"。

已知问题与限制

• 必须硬刷新：客户端半包在 window.__ModuleLoader__.load 里注册，装载发生在页面加载时；安装 / 更新后未硬刷新页面标签不会出来（AGENTS.md:23-25）
• 多账号与环境变量冲突：若 Shell 已 export DEEPSEEK_API_KEY，凭据提供方会拒绝覆写，切换按钮直接报错——临时 unset 后再切（README.md:43-44）
• 永久删除取决于宿主能力：当前官方 DSH 发行版未提供 permanentDelete 能力，UI 开关保持禁用；不可通过改配置伪装；接入步骤在 integrations/dsh-session-delete/ 单独说明（AGENTS.md:54-57）
• 旧包名残留：早于 0.1.1 的 dsh-wallet 不会自动卸载，需手动 dsh plugin --profile web remove dsh-wallet 避免两个包抢同一行（README.md:93）
• USD 账户成本为估算：CNY 价格表按官方长期固定汇率换算，标签明确写为「本约 $x」；汇率非实时，官方余额为权威值（README.md:42-43）
• 充值 URL 不可配置：https://platform.deepseek.com/top_up 硬编码为防钓鱼设计（README.md:138）

DeepSeek Harness Control Center

DeepSeek Harness monitoring, alerts, recharge, and session control center.

Balance ¥5.89 · Session ¥0.72 · Official 18.8M | Third-party 800K · ↗ Recharge

English · 简体中文 · Install · Compatibility · Changelog

A local-first companion that keeps account status, per-conversation usage, completion reminders, official recharge, flexible layout, and host-gated session controls beside the DSH composer.

If DeepSeek Harness Control Center helps you, please consider leaving a ⭐ Star. Thank you!

What it does

余额 ¥5.89 · 本场 ¥0.72 · 官 18.8M | 三方 800K · ↗充

• Official DeepSeek — live balance (60s global refresh with fast boot retries), current-session cost locked to the price active for each usage event (including the 2026-08-17 peak/off-peak rollout), and token breakdown.
• 24h peak/off-peak ring clock — resident sidebar footer widget indicating real-time pricing windows (peak vs. 50% discount off-peak), countdown to next switch, and optional desktop switch notifications.
• Third-party total — current-session tokens (input / cache read / output). No balance guessing, no cost math, zero configuration.
• Click the chip to open the detail panel: correctly formatted per-currency balances, cost and token splits, a freely editable low-balance threshold in CNY (two decimals, persisted globally; alerts only compare a CNY balance and never mix currencies), manual refresh, and a jump to the official recharge page (first click shows the domain for confirmation — anti-phishing).
• Move, dock, and scale — drag the chip freely, preview nearby snap targets, use compact horizontal or vertical layouts, adjust its scale from the control panel, and show official or third-party data independently. The choices are remembered locally.
• Floating window mode — detach the detail panel into a draggable window with a remembered position, or minimize it directly to a freely movable dot; the dot turns red below the threshold.
• Completion reminders — optionally notify when a conversation finishes, with persistent or timed modes, queueing and deduplication for simultaneous completions, cross-tab coordination, and an in-page fallback when system notifications are unavailable.
• Optional permanent deletion — when the DSH host advertises a real deletion capability, an opt-in setting enables a confirmed permanent-delete action in the session menu; unsupported hosts keep the control disabled.
• Low-balance alert — below the threshold the chip turns red with a breathing animation and fires one desktop notification; it resets automatically once the balance recovers.
• Theme-native UI — built entirely on --dsw-alias-* theme variables, so light and dark themes both render correctly; the panel closes when you click outside and flips open-direction near screen edges.
• Clear current-session wallet data — one button clears only the open conversation's token/cost records; it does not delete the conversation, and every other conversation is untouched.

Multi-account

• Open the wallet panel → 账户管理 to add accounts (name + API key), switch the active one, or remove them.
• The first account added becomes the active account automatically and is synced into the credentials seam.
• Switching prompts a confirmation because it changes LLM billing for subsequent requests: the switch writes the account key into the credentials seam (credentials.set('DEEPSEEK_API_KEY', ...)), and since the llm-deepseek provider route resolves that reference per request, the very next LLM call is billed with the new account — no restart needed.
• Account keys are stored plaintext in $DSH_HOME/storages/accounts.json; the UI only ever shows masked keys. Balance lookups prefer the active account's key and fall back to the credentials seam when no account is active.
• Session cost follows the active account's currency: USD-settled accounts show 本约 $x — a clearly-labeled estimate converted from the CNY price table at the vendor's long-standing list ratio (not a live FX rate); CNY accounts show the exact 本场 ¥x.
• If DEEPSEEK_API_KEY is supplied by the launching environment, switching is refused with a clear error (the credentials provider rejects shadowed writes) — unset it in your shell to enable switching.

Project overview

One place for the signals that matter

DeepSeek Harness can keep several conversations and model providers active at once, but balance, usage, background-task status, and session actions normally live in different places. Control Center brings the information worth checking repeatedly beside the composer, so the current workflow can answer three questions at a glance: How much official balance remains? What has this conversation used? Does anything need attention?

Present when needed, quiet when not

The project is designed around quick reading and in-context action rather than another full-page dashboard. Its compact surface expands only when needed, adapts to the available space, and leaves layout and reminder behavior under the user's control. Accounting remains separated by conversation and provider, while wallet-data cleanup and permanent session deletion remain intentionally different operations.

Extensible without hiding the boundaries

The npm package handles monitoring and interface behavior; optional host powers are enabled only when DSH actually provides them. That capability-based boundary keeps unsupported actions visibly unavailable and gives browsers or desktop wrappers a small, reviewable adaptation surface. Future providers and controls can therefore be added without changing the established deepseek-harness-wallet package identity or silently expanding what the plugin is trusted to do.

Want permanent session deletion? It cannot be enabled by configuring the plugin alone. Give the integration guide and Agent adaptation prompt to an Agent with access to the buildable DSH source. The control-panel switch becomes available only after the host implementation is built, tested, and advertises the capability.

Details: compatibility · data and trust · pricing

Install

From npm:

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

or from GitHub directly:

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

Restart dsh web, then hard-refresh the page.

Update

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

Remove

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

The package was renamed from dsh-wallet to deepseek-harness-wallet in 0.1.1. If you installed the old name, remove it with dsh plugin --profile web remove dsh-wallet first.

Browser, desktop, and OS compatibility

The client contains no operating-system-specific feature branch; it checks the Web and host capabilities it needs. That makes the same code portable, but portable code is not the same as real-device verification:

The last row describes intended compatibility, not a claim that every browser/OS/wrapper combination was physically tested. If system notifications are unavailable or denied, reminders fall back to an in-page notice; if Web Locks are unavailable, a renewable local-storage lease coordinates reminder ownership across tabs. CSS zoom also has a transform fallback. Core wallet data, controls, dragging, docking, scaling, and visibility settings use these shared paths rather than an OS name check.

Electron, Tauri, and other DSH desktop wrappers can run the wallet when they expose the normal DSH Web plugin loader, slots, wallet HTTP endpoints, DOM, and fetch. A wrapper that restricts native notifications, persistent storage, or external links may define one optional adapter before the plugin bundle loads:

window.__DSH_WALLET_ADAPTER__ = {
  // All fields are optional. Keep storage synchronous and localStorage-compatible.
  storage: { getItem, setItem, removeItem },
  notify({ title, body, tag, requireInteraction, onClick, onClose }) {
    // May return a notification-like handle, Promise, or nothing.
    // Call the supplied onClick/onClose callbacks for native events.
  },
  requestNotificationPermission() { return 'granted' },
  openExternal(url) { return true },
  capabilities: { permanentDelete: true },
}

notify() may return a notification-like handle, a Promise for one, or nothing for fire-and-forget native APIs. The payload also includes onClick / onClose callbacks so Electron IPC, Tauri notification actions, and other desktop bridges can return events without copying wallet logic; returning false asks the wallet to use its browser fallback. requestNotificationPermission() is optional for hosts such as Tauri and macOS that require a native permission request. Returning false from openExternal() likewise asks the wallet to try the browser fallback. Declare permanentDelete only when the host actually implements the wallet preference and session-menu action; compatible hosts advertise it automatically, while unsupported hosts show a disabled control instead of a switch that has no effect. Platform adaptations are intentionally confined to createCompatibilityAdapter() in lib/client.js, so an Agent can add a new wrapper without editing wallet accounting or UI logic.

For buildable DSH hosts, the npm package and repository include a versioned Agent-assisted permanent-delete integration kit with a Chinese guide, complete Agent prompt, read-only preflight, compatibility manifest, upstream notice, and an exact-baseline reference patch. The patch is not a universal installer: a different DSH commit must be inspected and adapted by semantics, and closed or non-rebuildable desktop applications remain unsupported.

Data & trust

Pricing timeline

CNY per 1M tokens, curated from official announcements (cache writes are not billed):

• Since 2025-02-09 — deepseek-chat 2/8 (cache read 0.5), deepseek-reasoner 4/16 (cache read 1)
• Since 2026-04-24 — v4-flash 1/2 (cache read 0.02), v4-pro 3/6 (cache read 0.025)
• Since 2026-08-17 00:00 Beijing — peak/off-peak pricing for the v4 models (peak windows Beijing 09:00–12:00 / 14:00–18:00; off-peak is half the peak rate):
  • v4-flash (off-peak / peak): cache read 0.05 / 0.10, input 1.5 / 3, output 4.5 / 9
  • v4-pro (off-peak / peak): cache read 0.15 / 0.30, input 4.5 / 9, output 13.5 / 27

deepseek-chat and deepseek-reasoner keep their flat rates. Each usage event is priced when it arrives; upgrading from 0.1.2 migrates legacy counters once using the then-current rate. Costs are estimates; the API-returned balance is authoritative.

Roadmap

• Third-party price tables (cost per token)
• Balance history chart
• Balance-API adapters for other providers (e.g. Zhipu)

License

MIT