The plugin-based architecture of DeepSeek Harness allows functionality to be extended. When multiple API providers need to be called, frequently checking platform balances or estimating current-session usage can interrupt the workflow. dsh-api-dashboard is designed to address this pain point by providing real-time multi-platform status monitoring.

Feature Overview

This is a client-side plugin. Its core value is showing real-time platform balances and estimated current-session usage below the input box in the Web GUI.

Main capabilities include:

  • Three-layer UI design: status bar (below the input box), dashboard drawer, and platform details.
  • Usage monitoring: supports estimated current-session usage, mixed-currency display (no FX conversion or merging), and sub-agent usage.
  • Billing and thresholds: provides peak/off-peak playful billing, a three-color threshold indicator (green/yellow/red), and balance alert notifications.
  • Practical tools: one-click recharge, Big Fat Fish widget, custom integration, configuration persistence, and one-click self-update.

Installation

In the desktop version of DeepSeek Harness, install it with the following command:

dsh plugin --profile web add dsh-api-dashboard

Usage and Configuration

The plugin supports configuration persistence. Thresholds, currencies, refresh interval (1-60 seconds), and custom entries are saved in a local state file and will not be lost after restart.

Configuration can be adjusted via the settings panel. After saving, it is written to ~/.dsh/dsh-api-dashboard. (the file extension may vary depending on the specific version; please use the actual file as reference). You can also directly edit the cordis.patch.yml file.

Supported platforms:

  • Domestic platforms: DeepSeek, Zhipu GLM, Kimi, StepFun, SiliconFlow, MiniMax.
  • Overseas platforms: OpenRouter, Novita AI, xAI Grok.
  • Others: custom relay/gateway, custom models.

Notes

  • Runtime: Can only run inside DSH (mobile DSHA shares the same framework as the desktop version).
  • UI display discrepancy: On mobile DSHA, the client UI does not appear after installation (the command targets the desktop version).
  • Key security: API Keys are read only from environment variables or the DSH credential system; they are not written into code or repositories.
  • Data accuracy: Starting with v1.4.1, plugin routes include an authentication gate (no cookie → 401, cross-origin → 403). For platforms such as OpenAI, Claude, Gemini, Groq, Mistral, and Together that do not expose a balance query API, the panel will accurately display “Not available” and will not fabricate numbers.
  • License: MIT License.

Basic Information