dsh-claude-cli
Use the locally installed Claude Code CLI as a DeepSeek Harness LLM provider — no API key, native tool calls through an MCP bridge
AI Analysis
核心用途是将本地 Claude Code 命令行工具接入 DSH 作为模型后端，免去 API 密钥配置。适合已安装 Claude Code 且希望在 DSH 中直接调用其原生工具能力的用户。
Install
npx -p @deepseek-ai/dsh dsh plugin --profile web add github:katsos/dsh-claude-cliREADME
Read the full README ↗Configuration
| Field | Default | Meaning |
|---|---|---|
providers | ['anthropic-claude-cli'] | Provider routes this adapter serves. |
executable | 'claude' | Path or command name of the CLI. |
cwd | harness cwd | Working directory for the CLI process. |
streamIdleTimeoutMs | 300000 | Maximum gap between CLI output lines before the request fails as TIMEOUT. |
unsupportedFields | 'error' | error rejects request fields the CLI cannot honor; ignore drops them. |
defaultEffort | — | low | medium | high | xhigh | max, used when a request selects none. |
extraArgs | [] | Extra arguments for CLI flags this plugin does not model. |
extraArgs is passed before the plugin's own flags, and an entry naming one of
them is rejected when the plugin loads. Both matter: the CLI keeps the last
occurrence of a repeated flag, so appended arguments would otherwise win. A
single --tools default was enough to restore the CLI's full tool set — Bash
and Edit included — inside the harness's working directory. Use extraArgs for
flags the plugin leaves alone, such as --betas.
Models are whatever the CLI accepts: the aliases fable, opus, sonnet, haiku, or a full id such as claude-sonnet-5. The catalog is advisory — an unlisted id is passed to --model unchanged.
Usage terms
Nothing here bypasses authentication. Requests run through the official CLI, as whatever claude is already logged in as, using the same documented --print mode Claude Code ships for non-interactive use.
What this plugin adds is different in kind: it makes a subscription login the model backend for another agent framework. Anthropic's Consumer Terms reserve programmatic access for API keys, saying you may not reach the services "through automated or non-human means, whether through a bot, script, or otherwise". Whether driving the CLI this way falls inside that sentence is Anthropic's call to make, not this README's.
Treat your own plan's terms and the Usage Policy as the authority over anything written here. In particular:
- Prefer an API key and an HTTP provider for unattended, high-volume, or production traffic. This plugin suits work you would otherwise have run by hand in Claude Code.
- Reselling access, serving other people's requests, and evaluating the models to build a competing product are each separately prohibited, whichever credential you use.