Set up DSH (DeepSeek Harness)

01 / PREPARE

Install the agent and prepare access

1. Install the agent using its official guide. Check its version before merging the examples below.
2. Purchase your DeepSeek plan, then open Billing & API keys to copy your active key. OpenAI base: https://ds-api.savemytoken.com/v1. Claude Code base: https://ds-api.savemytoken.com. DeepSeek credentials are a separate scope.
3. Back up the file you will edit. Merge fields into existing objects and tables; preserve unrelated providers, tools and permission settings. Keep credentials in private local settings.
4. Start dsh web, open the printed local address, then Settings → Models → Add model provider → Custom model API. Select OpenAI Chat Completions and enter the delivered /v1 base and key in that form.

Ready when: the agent opens, and you know which plan, process and configuration directory you will use.

02 / CONFIGURE

Save the connection and model catalog

Create the parent directories if needed. Download or copy each file, replace the example endpoint and local placeholders, then merge it into the stated location. Downloads and the examples below contain the same configuration.

- id: llm-pi-ai
  config:
    providers:
      savemytoken-deepseek:
        compat:
          supportsDeveloperRole: false
        models:
          - id: deepseek-flash
            reasoningEfforts:
              off: none
              low: low
              high: high
              max: max

Ready when: the files parse successfully and the selected profile points to the delivered URL, key reference and exact model catalog.

03 / START

Start the agent and choose your model

Open a terminal in a trusted project. Complete the file setup before running these commands.

dsh web

Use Provider ID savemytoken-deepseek in the form. Fetch available models, select the permitted IDs below and save. If discovery is unavailable, add each exact ID and display name manually. Choose the provider beside the composer.

Check: the provider is the one you configured and the selected model is deepseek-flash. A visible model list alone does not prove inference works.

04 / REASONING

Choose and verify reasoning effort

Model discovery can supply names without effort metadata. Merge the capability fragment into the active profile, restart and open the Effort menu. Off explicitly maps to none; a null/empty mapping may only omit the parameter.

This patch does not set the starting effort. Before the first request, select the default listed in the table: High for DeepSeek, Max for GLM/Kimi, XHigh for Qwen, and High (On) for MiMo/MiniMax. Recheck after switching models.

Choose provider → choose model → choose Effort → start a new session

On DeepSeek Flash, choose Low, then High, then Low again. Inspect the active setting each time before sending the next message. A longer answer is not evidence that effort changed.

REASONING CONTROLS

Choose effort for the actual model

The setup templates start with DeepSeek Flash. Add other delivered routes only after confirming their exact IDs and capabilities.

05 / DESKTOP

Harness Desktop / local Web UI

Harness Desktop has the same custom-provider setup flow, but can use a different profile from dsh web. Add the provider and credentials in Desktop's own Settings → Models.

Use the app's configuration-file action to locate the active profile before merging model capabilities. Editing the web profile does not configure Desktop. Restart and choose the intended model and effort in a new session.