AI Agent Hub
Back to plugins
🤖

dsh-provider-qoder

Model Inference Updated 2026.08.21

Run the following command in DeepSeek Harness:

dsh plugin install minglu6/dsh-provider-qoder

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install minglu6/dsh-provider-qoder on a machine that already has dsh and pnpm to install the Qoder CN inference adapter plugin from https://github.com/minglu6/dsh-provider-qoder

About this plugin

DeepSeek Harness is a flexible model-inference orchestration framework, but wiring it to the Qoder CN gateway means dealing with COSY request signing, WAF-encoded streaming, and the PAT-to-short-lived-job-token exchange. dsh-provider-qoder packages that entire chain into a plug-and-play adapter so Qoder CN inference services slot into DeepSeek Harness as naturally as any other backend.

Under the hood the plugin registers an llm-qoder settings namespace and resolves connection facts per request. Public-cloud users only need to paste a PAT; enterprise VPC deployments can pin the vpcInstance in settings.yaml. Model discovery follows a live-first strategy: every time DSH enumerates the provider, the adapter fetches Qoder signed catalog, so newly released wire keys (e.g. gmodel) appear without a plugin update while known models keep stable selector ids (gm51model → glm-5.2). A static models override is available for deployments that deliberately pin the selector list, replacing live discovery rather than extending it.

The design is a good fit for teams that already run multiple inference backends under DeepSeek Harness and want a single scheduling entry point, particularly when traffic must go through Qoder CN public-cloud or enterprise-VPC gateway. Auth, transport, malformed-JSON, and empty-catalog failures are surfaced as discovery errors rather than silently falling back to a stale built-in list, keeping the troubleshooting path transparent and predictable.

Use Cases

  • Plug Qoder CN public-cloud inference into DeepSeek Harness with a single PAT, no extra plumbing
  • Point an enterprise VPC gateway via vpcInstance and fold Qoder CN into unified inference orchestration
  • Auto-detect newly released Qoder models through live catalog discovery without a plugin update
  • Pin a static selector list for compliance or canary-release deployments

Best For

  • Engineering teams already orchestrating multiple inference backends under DeepSeek Harness and looking to add Qoder CN
  • Platform or DevOps engineers who must route through an enterprise VPC gateway to Qoder CN
  • SRE teams that value transparent failure semantics across auth, transport, and catalog discovery in their inference stack