dsh-thinking-effort

A DSH (DeepSeek Harness) plugin that adds configurable reasoning effort levels to hand-declared llm-pi-ai models and sets a default reasoning effort for subagents.

• 中文 README
• 日本語 README
• 한국어 README
• Installation guide
• 中文安装指南
• 日本語インストールガイド
• 한국어 설치 안내
• Changelog
• 日本語 changelog
• 한국어 changelog

Compatibility boundaries: DSH Runtime compatibility covers the Settings transport only: modern DSH exposes remote.settings, while legacy DSH exposes connection.api.settings. The plugin detects the available runtime capability and keeps the legacy fallback optional, so the settings page does not require a Remote provider on older DSH builds.

Gateway Protocol compatibility is a separate layer. When the DSH schema exposes them, the plugin supports 18 common scalar llm-pi-ai.compat fields, grouped into role/reasoning, format/output, streaming/tools, and storage/cache. Boolean fields offer Auto, supported, and unsupported; enum fields offer Auto and their concrete values; number fields take Auto or an integer. DSH 0.1.0-rc.7 does not provide gateway compat settings. DSH 0.1.0-rc.8 through <0.1.2-alpha.1 provide the other fields, but not supportsFinishReason or supportsThinkingTokenBudget; DSH 0.1.2-alpha.1 through <0.1.3-alpha.2 expose 15 of them, and 0.1.3-alpha.2 and later expose all 18 when supported by the schema. The optional dsh-llm-openai-completions transport can take over eligible custom OpenAI-compatible thinking providers when it is installed and enabled. Auto unsets the current-layer override and restores the next value in the inheritance chain.

DSH 0.1.2-alpha.1 and later accept language-pack locale IDs through LocaleRuntime. This plugin registers ja and ko dynamically, so no DSH core fork is required. Older DSH builds that only expose built-in locale IDs support zh and en only.

The published runtime entries are lib/index.js (Host) and lib/client.js (Client). After changing TypeScript or locale sources, run pnpm run build before running DSH or packing the plugin. Current DSH does not expose a public semver metadata contract, so runtime capability detection is authoritative. An optional version is used only when explicit metadata or test input supplies it; unknown valid versions still use the detected capabilities. The plugin supports both modern remote.settings and legacy connection.api.settings.

The Host registers its dsh-thinking-effort Settings namespace through the host-provided Settings installSection when available, and falls back to the legacy register path otherwise. Under the 0.1.7+ entry-config model neither path exists, and the section comes from the exported Config instead. It does not depend on @deepseek-ai/dsh-settings at runtime, so the package installs cleanly into DSH profiles configured with autoInstallPeers: false without introducing a second Cordis runtime.

DSH compatibility

…