Qwen3.8-27B Runs 40-Step Agent Tasks Inside DeepSeek Harness
A 27B open-weight model running locally can now sustain multi-step agentic workflows that previously required much larger proprietary models. The combination of vLLM's tool-call parsing and DSH's execution harness and trace view gives developers a self-hosted, debuggable alternative to closed agent platforms.
A real-world integration test drops Qwen3.8-27B-FP8 into DeepSeek Harness and assigns it a multi-step WorldQuant alpha research task. The model reads project files, writes and executes Python scripts, launches parallel simulations, and maintains a running task list across nearly 40 steps. When a race condition corrupts the results file, it diagnoses the concurrency bug from logs and recovers by reading the JSONL output instead. The entire session ran continuously for over 30 minutes with no goal drift.
Setup is two-stage: serve the model with vLLM using the official reasoning and tool-call parsers, then register the OpenAI-compatible endpoint as a custom provider inside DSH. The critical detail is that the model ID in DSH must match vLLM's `--served-model-name` exactly. DSH's trace view then exposes every tool invocation, parameter, and timing breakdown, turning an opaque agent run into an inspectable execution chain.
Tool-call reliability in open-weight models has reached a threshold where a 27B parameter model can sustain a 40-step agent loop without derailing, which shifts the bottleneck from model capability to harness design and observability.
The Docker GPU device mapping (`--gpus '"device=2"'` with `CUDA_VISIBLE_DEVICES=0`) is a common footgun for self-hosted setups; the container remaps host GPU indices, so the two values intentionally differ.
DSH's trace view addresses the core pain point of agent development: when a model runs unattended for 30 minutes and produces a wrong answer, you can pinpoint exactly which tool call or reasoning step went wrong instead of replaying the entire session.