AI Agent Hub
Back to plugins
dsh-llm-qwen-local preview

dsh-llm-qwen-local

Model Inference Updated 2026.09.01

Run the following command in DeepSeek Harness:

dsh plugin install starefinger/dsh-llm-qwen-local

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

Run dsh plugin install starefinger/dsh-llm-qwen-local in your terminal to install the plugin; the full source code is available at https://github.com/starefinger/dsh-llm-qwen-local .

About this plugin

You have a locally deployed Qwen3.8-27B served by vLLM and want to plug it into DeepSeek Harness for unified CLI and Web UI workflows, but the native DSH adapters do not cover the Qwen lineup. dsh-llm-qwen-local fills that gap: it translates DSH requests into the OpenAI-compatible /v1/chat/completions endpoint behind your vLLM instance, so you can use your local Qwen model as naturally as a managed one.

Two deployment-specific differences are treated as first-class configuration. A per-model multimodal switch honestly declares whether the endpoint serves vision reasoning, preventing silent image-to-placeholder degradation or mid-turn failures after an image message is persisted. Every reasoning-effort level, including its display name, wire spelling, default value, and how the off state is represented, is fully configurable, matching whatever vocabulary your vLLM build accepts without touching code.

Built for developers who already run Qwen models (especially the Qwen3.8-27B class) on vLLM in a local or intranet environment and want to fold them into the DeepSeek Harness workflow for daily development, tool calling, and multimodal understanding. No public-cloud API key, no DashScope or Qwen Cloud required, just a vLLM instance and DSH 0.1.1-rc.2 or newer.

Screenshots

Use Cases

  • Plug a locally vLLM-served Qwen model into the DSH unified CLI and Web UI workflow
  • Control multimodal vision reasoning per model via the first-class multimodal switch
  • Map reasoning-effort levels to the exact wire vocabulary your vLLM build accepts

Best For

  • Developers running Qwen models on vLLM in local or intranet environments
  • Users who want self-hosted models folded into the DeepSeek Harness unified workflow
  • Independent developers needing multimodal understanding or tool-calling scenarios