dsh-commandcode-provider

dsh-commandcode-provider

English | 简体中文

Unofficial DeepSeek Harness LLM provider plugin for Command Code, ported from pi-commandcode-provider (MIT). Community integration. You need your own Command Code account, API key or subscription, and Command Code's terms apply. Not affiliated with Command Code, Inc. Quick start Features Plugin bundle — one dsh plugin add installs a commandcode provider route with the live model catalog. Settings page — accounts (keys, browser sign-in, live quota, dedicated models), model visibility, privacy switches, connection options. Annotated catalog — plan tier, deal/FREE badge, peak/off-peak, image support and context window in the picker; free models first. Custom model names — override a model's display name by catalog id so external tools that match on the name string (peak-hour reminders, cache-pricing plugins) keep working; the model id, request body, pricing and picker order are unchanged. Multi-account rotation — an exhausted account hands over to the next one; pin a preferred account or route models to dedicated ones. Browser sign-in — run the official authorization flow from the settings page; the approved key lands in the local credential store. Plans &

Model picker — plan tier, deal/FREE, peak/off-peak, Image and context annotations:

Usage dashboard — /commandcode per-account report:

Settings page — accounts with live quota, model visibility, privacy switches, connection options:

Install

This build admits dsh >=0.2.1-rc.2 =0.2.2-alpha.2 =24.9.0 and this plugin admits that engine, so the package-wide floor had to follow: a plugin that claims to support an engine must not be installable on a Node version that engine cannot start on. What that means in practice: npm reports EBADENGINE when installing or updating this plugin on Node 22/23. It is a warning, not a hard failure, unless your npm sets engine-strict=true. The 0.2.2 engines genuinely cannot run on Node 22/23, so a profile admitted there would fail at startup — the failure this floor exists to prevent. The 0.2.1 RC engines still run on Node 22, but engines.node is a single floor for the whole package, so it applies to them too. That is the cost of admitting two channels in one build.

nvm install 24 && nvm use 24 (or any Node 24.9+ distribution) resolves it. Node 24 is a current LTS line.

Older dsh releases are no longer supported: the last plugin release for dsh 0.1.7 is 0.11.17, for 0.1.2–0.1.6 it is 0.11.11, and for the 0.5.0-era line 0.9.1 — all installed by exact version, none maintained. pnpm 11 holds back new releases. minimumReleaseAge defaults to 1440 minutes, so a version published less than a day ago is skipped and @latest resolves to the *previous* release — silently, with a success exit code. To install a release from the last 24 hours, name it exactly: @mars-sea/dsh-commandcode-provider@0.11.15. This applies to every profile, including the terminal UI below. Updating