Configuring deepseek-harness-wallet
The wallet panel’s Account Management(账户管理) view accepts an account name and API key. The first account becomes active automatically. Switching accounts writes the selected key through credentials.set('DEEPSEEK_API_KEY', ...); the llm-deepseek provider route resolves that reference for the next request, without requiring a restart. Thresholds are editable per account and currency and are persisted locally. The README does not provide environment-variable names or a configuration-file path.
How deepseek-harness-wallet stores usage
The plugin maintains a local ledger covering 365 days. Stable request identities are deduplicated, and the cost for an official usage event is fixed to the pricing rule active when that event occurred. Current-session data can be cleared without deleting the conversation; historical ledger clearing is separate. Prompts and responses are not stored. Collection starts after upgrading to v0.3.2; older aggregate counters are not backfilled.
Provider and pricing behaviour
DeepSeek Harness receives the active provider and model context so the composer chip and sidebar clock can change their contents. Official pricing is periodically read from the DeepSeek pricing page, but only a fully validated table is applied. A failed request keeps the last validated rule. deepseek-v4-flash-vision-exp uses V4 Flash pricing, including image tokens reported by DeepSeek Harness. Configured Z.ai Global and China plans expose token-window and MCP-tool quotas rather than a CNY balance.
Commands and requirements
The documented controls are panel actions: manual refresh, recharge-page navigation, account management, layout and scale changes, completion reminders, and optional deletion when the host advertises a deletion capability. The README documents no plugin-specific command, supported operating-system list, or additional runtime requirement. The package is flagged with a terminal surface, but the supplied documentation does not identify its terminal entry point or reachable data.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub