Introduction

One of the core design principles of DeepSeek Harness (DSH) is modularity, with functionality extended through plugins. When using Command Code for model invocation, checking account credits, usage periods, or syncing the model list often requires switching to the Command Code console or using the CLI. The commandcode-dash plugin integrates key Command Code information into the DSH Web settings panel, addressing the need to manage external service status within a single workflow.

What is it

This is a DSH Web plugin maintained by community developer Momonaka. It adds a Command Code-specific configuration block to the DeepSeek Harness settings panel. The plugin primarily addresses three problems: viewing real-time Command Code account credit balances and usage periods; comparing local model configuration with the official provider/v1/models catalog and syncing with one click; and managing the API key directly within the DSH interface.

Core Features

  • Credit and usage monitoring: Retrieves monthly, purchased, and free credit balances via the live billing API. Provides 5-hour and weekly usage windows, displaying remaining time with progress bars and countdowns.
  • Billing period statistics: Shows request count, success rate, consumed credits, and token count.
  • Model catalog management: Displays the context windows of configured models and supports search.
  • Smart sync: Compares local configuration with the official provider/v1/models catalog. Supports one-click sync and requests user approval for new or removed models.
  • Security and authentication: Provides a Setup card for storing the API key with write access, and supports one-click sign-out to forget the key.

Installation and Enablement

  1. Ensure DeepSeek Harness is installed and the web profile is enabled (or use the desktop app).
  2. Ensure the host has Node.js 20+ installed (the plugin uses AbortSignal.any).
  3. Run the install command:
dsh plugin --profile web add commandcode-dash

After installation, restart dsh web to make it take effect.

Typical Usage

  • Configure the API key: On first use, the settings panel displays a form for entering the Command Code API key (write access). The key is stored in the Harness credential store under the reference name COMMANDCODE_API_KEY.
  • Add the key manually: You can also add it manually in the .credentials.yaml file:
refs:
  COMMANDCODE_API_KEY: user_...
  • Manage model routes: After saving the key, the plugin automatically adds two provider routes: commandcode (using the openai-completions protocol) and commandcode-anthropic (using the anthropic-messages protocol). The former supports all models except Claude, and the latter supports Claude only.
  • Sign out: Click the Sign out button at the bottom. After confirmation, the stored key is cleared, and the panel returns to the Setup card state.

Use Cases and Notes

  • Use cases: Developers who need to frequently monitor Command Code spending from the DSH interface, or who want to manage model catalog configuration in a centralized way.
  • Notes: This is an unofficial plugin built by the community and has no affiliation with DeepSeek or Command Code. Before use, confirm that your Command Code plan has access to the Provider API (all plans except the Go plan support it). The plugin depends on the host Node.js environment and requires version 20 or higher. The key is only used to access the Command Code Provider API and is not sent to any other third-party service.

commandcode-dash pushes Command Code management into the DSH settings panel, reducing the cost of switching between tools. For more details or source code, visit the GitHub repository.