Back to directory

dsh-claude-provider

Curated pickMaintenance: Active

mofeng2223/dsh-claude-provider

Custom Claude provider support for DeepSeek Harness

View on GitHub
$ npx @deepseek-ai/dsh plugin --profile web add @mofeng2223/dsh-claude-provider

32

stars

0

forks

JavaScript

Language

MIT

License

2026-08-14

Created

2026-10-03

Last push

A DeepSeek Harness plugin that adds a dedicated Claude provider type with native Anthropic model discovery, per-model reasoning modes, and automatic Claude model defaults — all written to settings.yaml on save.

DSH integration

Native runtime

Author-claimed

Safety audit

Unaudited

Last verified

2026-09-06

License

MIT

01What can it help you accomplish?

  • Add and configure a Claude (Anthropic) provider in DeepSeek Harness without hand-editing settings.yaml

    A dedicated Claude Provider form that writes native settings.yaml entries on save, with model-specific reasoning modes (five/four levels or a toggle) and automatic Claude model defaults

    DeepSeek Harness users who want to route Claude models through the official Anthropic Messages protocol with native defaults

  • Discover and populate Claude models for a provider

    Lists models via the native Anthropic-compatible `GET /v1/models` endpoint (cursor pagination) and auto-fills context window, max output, and reasoning-mode set for known Claude IDs

    Users running Claude providers who want model lists and defaults without manual entry

02How to install into DeepSeek Harness

Installation steps

  1. 01

    Install the Web profile for the browser interface: `npx @deepseek-ai/dsh plugin --profile web add @mofeng2223/dsh-claude-provider`

    $ npx @deepseek-ai/dsh plugin --profile web add @mofeng2223/dsh-claude-provider

  2. 02

    Restart the corresponding DeepSeek Harness process after installation.

  3. 03

    From source: `git clone https://github.com/MoFeng2223/dsh-claude-provider.git`, `cd dsh-claude-provider`, `npm install`, `npm run build`, `mkdir -p dist`, `npm pack --pack-destination dist`, then `npx @deepseek-ai/dsh plugin --profile web add ./dist/mofeng2223-dsh-claude-provider-*.tgz`

    $ git clone https://github.com/MoFeng2223/dsh-claude-provider.git

Verify the integration

Not specified by the author

Rollback

  • `npx @deepseek-ai/dsh plugin --profile web remove @mofeng2223/dsh-claude-provider`
  • Note: uninstalling does not delete `~/.dsh/settings.yaml` or stored credentials.

03DSH integration and capability boundaries

DSH integrationNative runtime

Installed as a dsh plugin via `npx @deepseek-ai/dsh plugin --profile web add`; writes native settings.yaml entries on save

  • Dedicated Claude provider type

    Claude (Anthropic) provider credentials entered in the Models settings page→A separate **Claude Provider** form that can hold multiple Provider IDs without mixing them with generic custom providers

  • Model-specific reasoning modes

    Each Claude model selected under a Claude Provider→One of three mode sets per model: five levels (Low, Medium, High, XHigh, Max), four levels (Low, Medium, High, Max), or a toggle (On/Off); new models default to five levels, Claude providers default to High

  • Native Anthropic model discovery

    A Claude Provider configured with an Anthropic-compatible base URL→Lists models through the provider's native Anthropic-compatible `GET /v1/models` endpoint, including cursor pagination

  • Automatic Claude model defaults

    A discovered model whose ID matches a recorded Claude model ID→Automatically fills the model's context window, maximum output length, and reasoning-mode set; manually entered models stay fully editable and are not overwritten

  • Isolated to Claude Providers only

    n/a→Discovery, defaults, and reasoning controls apply only to Provider IDs explicitly created as Claude Providers; all other providers keep their original behavior

04Who is it for? When not to use it?

Good for

  • DeepSeek Harness users who want to route Claude models through the official Anthropic Messages protocol with native defaults
  • Users running Claude providers who want model lists and defaults without manual entry

Not for

  • Native reasoning-effort parameters for Claude models require DeepSeek Harness 0.1.1-rc.1 or newer. On supported versions the plugin only writes native settings.yaml entries on save and no longer intercepts or rewrites model requests at runtime.

05Compatibility, maintenance and safety notes

  • Discovery, defaults, and reasoning controls apply only to Provider IDs explicitly created as Claude Providers; DeepSeek Harness's built-in providers and ordinary custom providers keep their original behavior even when they use anthropic-messages or a claude-* model ID.
  • Native reasoning-effort parameters for Claude models require DeepSeek Harness 0.1.1-rc.1 or newer. On supported versions the plugin only writes native settings.yaml entries on save and no longer intercepts or rewrites model requests at runtime.
  • Uninstalling the plugin does not delete ~/.dsh/settings.yaml or stored credentials; existing Claude providers remain ordinary custom anthropic-messages routes, and only the dedicated UI, model discovery, and recorded defaults disappear.
Not specified by the authorNot specified by the authorv0.4.2

readme_verified

06Frequently asked questions

How do I install dsh-claude-provider?

Run `npx @deepseek-ai/dsh plugin --profile web add @mofeng2223/dsh-claude-provider` in your terminal, then restart the corresponding DeepSeek Harness process. You can also build from source and add the generated .tgz package.

What does this plugin add beyond DeepSeek Harness's built-in custom provider?

It adds a dedicated Claude Provider form on the Models settings page, native Anthropic model discovery via `GET /v1/models` (with cursor pagination), and automatic Claude model defaults (context window, max output, reasoning-mode set).

Do I still need to edit settings.yaml by hand?

No. The plugin writes the corresponding native settings to `settings.yaml` when you save a Claude provider through the front-end form, so you never edit the file manually.

Does uninstalling the plugin delete my Claude configuration or credentials?

No. Uninstalling the plugin does not delete `~/.dsh/settings.yaml` or stored credentials; existing Claude providers remain ordinary custom `anthropic-messages` routes, and only the dedicated UI, discovery, and recorded defaults disappear.

Does it change other providers in DeepSeek Harness?

No. Discovery, defaults, and reasoning controls are limited to Provider IDs explicitly created as Claude Providers; DeepSeek Harness's built-in providers and ordinary custom providers keep their original behavior.

08Data and sources

  • Author-claimedgithub.comcc173d01676d…

    it writes the corresponding native settings to `settings.yaml` when a Claude provider is saved through the front end.

This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-09-06. Found an error? Submit a correction.

🏆

Best DeepSeek Harness Plugins

Twelve plugins worth installing first — picked from the whole catalog, across every category.

DSH Plugins is an independent community directory of DeepSeek Harness plugins. Not affiliated with or endorsed by DeepSeek. Third-party plugins are not security-audited — review the source before installing.

New DeepSeek Harness plugins, weekly. No spam.