News / Model Watch · Tooling
DeepSeek Harness Adds Multimodal Image Input — the Harness Got Eyes, the Models Didn't
One week after open-sourcing Harness v0.1, DeepSeek shipped two release candidates that put image input into the agent runtime: rc.7 (durable image attachments) and rc.8 (native image requests for DeepSeek adapters, image input for /goal and /plan). Overseas analysts are calling the harness "a second DeepSeek moment." Here is exactly what landed, what is still text-only, and what API builders should do with it.
DeepSeek Harness can now carry images end-to-end — and as of Aug 21, an official DeepSeek model can finally read them.
Per the official release notes:
rc.7 (Aug 17) added durable image attachments to MCP and ACP, with nested image forwarding in PTC mode;
rc.8 (Aug 19) expanded multimodal support with configurable native image requests for DeepSeek adapters, image input for
/goal / /plan, and file & session references in the @ menu.
At publication (Aug 20) the catch was that V4-Pro and V4-Flash were still text-only; on Aug 21 DeepSeek launched deepseek-v4-flash-vision-exp, the first official vision model in the Flash family — launch brief here. V4-Pro remains text-only.
rc.8 rides the npm next tag (latest is still rc.7), and its new SQLite storage format is incompatible with older sessions.
What shipped, per official sources
| Item | Detail |
|---|---|
| rc.7 · 2026-08-17 12:01 UTC | Durable image attachments in MCP and ACP, nested image forwarding in PTC mode; plugins can register their own settings cards; Codex and Claude Code subagent tasks join the Job Panel; new low reasoning effort for DeepSeek models (default stays high); English preset "Code mode" renamed "PTC mode" |
| rc.8 · 2026-08-19 15:37 UTC | Multimodal expansion: configurable native image requests for DeepSeek adapters, image input for /goal / /plan, file & session references in the @ menu (by @LegGasai and @CreatixChu); Claude Code & Codex subagents installable on demand as Profile Bundles; persistent PowerShell on Windows PTY; concurrent web_search; smaller dependency downloads; SQLite backend faster & smaller — storage format incompatible; "DeepSeek Harness" declared a registered trademark with brand guidelines |
| Fixes that matter here | rc.8 fixes model request failures caused by oversized images or excessive accumulated image payloads — the exact failure mode image-heavy agent loops hit — and fixes some custom OpenAI-compatible gateways failing on request-format differences or missing reasoning content |
| npm channels (checked 08-20) | latest → 0.1.0-rc.7; next → 0.1.0-rc.8. Plain npx @deepseek-ai/dsh still resolves rc.7; opt into rc.8 with npx @deepseek-ai/dsh@next |
| Repo momentum | 167,928 stars / 17,953 forks (GitHub API, checked 2026-08-20) — up from the 149,000+ Turing Post cited at its Aug 17 publication |
Background: Harness v0.1 was open-sourced Aug 13 alongside V4-Pro GA — see our v0.1 launch brief for the architecture (everything-is-a-plugin on Cordis, four work modes, MIT license).
The split: harness plumbing vs. model capability
- What got multimodal is the runtime, not the models. Paste an image in dsh today and it persists across MCP/ACP tool calls, forwards through PTC-mode programs, and can ride along in
/goaland/planplanning commands. That is real plumbing that was missing at v0.1 — early reviewers dinged the launch-week stack precisely because a text-only model couldn't chase a two-line visual bug. - DeepSeek's own API models were still text-only at publication — and gained vision a day later. On Aug 21, 2026, DeepSeek officially launched deepseek-v4-flash-vision-exp, an experimental vision model in the Flash family at unchanged pricing; V4-Pro remains text-only. At publication the changelog had carried no vision entry since the Aug 13 V4-Pro GA note, and a top Hugging Face discussion on V4-Pro complained it lacked "native multimodality every other Chinese flagship model has now, including Qwen and Kimi" — exactly the gap the launch just closed for Flash.
- The official docs make the intended pattern explicit. The repo's troubleshooting table: if an image is refused before sending, the model "declares no image modality" — fix it by adding
input: [text, image]to the model entry in$DSH_HOME/settings.yaml. In other words: flip on image requests for a model that actually has vision, via DeepSeek's adapter or any OpenAI-compatible endpoint. - The vision gap was already being bridged by plugins. modlens (self-described first vision plugin for dsh) lets you paste an image into a text-only session and get structured JSON evidence back — OCR, layout, semantics — routed through a pool of vision engines (a free Gemini key, Antigravity CLI, or any OpenAI-compatible endpoint; its README demos Qwen-VL via DashScope's compatible mode). Similar community tools include agent-vision-toolkit (image Q&A, long-screenshot OCR, UI restoration, GUI automation) and dsh-vision-router. Community projects, unaffiliated with DeepSeek — quality varies.
What the overseas coverage says
- Turing Post (Aug 17) published the sharpest English-language take: "DeepSeek is having its second DeepSeek moment." Its argument: with R1, DeepSeek weakened the model moat; with Harness (MIT, 149K+ stars at publication), it is "opening up the layer everyone had started looking to as the next moat" — the agent execution layer. It also traces Cordis's pedigree to Koishi, the chatbot framework by Shigma (now at DeepSeek), whose four years of plugin-lifecycle problems turned out to be agent-runtime problems.
- Launch-week press (covered in our v0.1 brief): VentureBeat framed dsh as an "open-source rival to Claude Code"; The Decoder profiled the architecture and project lead Cui Tianyi (ex-Jane Street); 36Kr's overnight hands-on found 288 plugin repos within 24 hours; Pandaily organized it as Model + Harness = Agent.
- The rc.7/rc.8 releases themselves were mostly tracked by changelog watchers and the plugin ecosystem rather than mainstream outlets in the first 48 hours — third-party guides (chat-deep.ai, dshdocs.com, freedom.tech) logged the "durable image attachments" line within a day. If you follow the story, follow the release notes, not the headlines.
- On X, the project's announcement thread (@deepseek_ai, Aug 13) and maintainer posts from @tianyi remain the canonical channels; modlens author @liustack ships release notes on X first — consistent with the ecosystem's center of gravity sitting in the repo and on X rather than in blogs.
Why this matters for a China-model stack
- The harness is free; image tokens are the new variable. With V4-Pro on peak/off-peak pricing (off-peak $0.66 input / $1.98 output per 1M, peak $1.32 / $3.96 — per The Decoder's reading of the official pricing page), the cost of an agent loop shifts to wherever images get processed. Routing vision sub-calls to a cheap vision-capable model while text models drive the coding loop is exactly the multi-model pattern dsh's plugin model layer was built for.
- rc.8's gateway fix is directly relevant to relay users. The release fixes custom OpenAI-compatible gateways that failed on request-format differences or dropped reasoning content — the class of bug that bites anyone pointing dsh at a third-party endpoint rather than first-party keys. Test your endpoint against rc.8 before blaming the harness.
- The breaking-change cadence is real and delivered. v0.1 promised compatibility-breaking changes; rc.8 delivers one (SQLite storage format incompatible). Pin your dsh version, keep session data out of the upgrade path, and re-verify after every rc bump — the line is still racing toward a stable 0.1.0.
- Branding is now formal. rc.8's notes clarify that "DeepSeek Harness" is a registered trademark with published brand guidelines — plugin authors and tool builders should read them before naming derivatives.
- Independent-project framing. dsh is DeepSeek's open-source project. ChinaModelAPI is an independent OpenAI-compatible relay with no official relationship to it or to DeepSeek — the practical overlap is that a model-agnostic harness is a natural client for multi-model routing, and vision-capable model IDs should be verified live in your provider's dashboard before you wire them in.
Primary sources
- GitHub — deepseek-ai/deepseek-harness releases (rc.7 and rc.8 notes, CN/EN)
- npm — @deepseek-ai/dsh dist-tags (latest = rc.7, next = rc.8, checked 2026-08-20)
- deepseek.com/harness — official developer preview page
- DeepSeek API changelog — no vision entry since 2026-08-13 (text-only status of V4 models)
- Turing Post — FOD#163: DeepSeek is having its second DeepSeek moment (2026-08-17)
- VentureBeat — DeepSeek Harness launches as open-source rival to Claude Code (launch week)
- The Decoder — improved V4 Pro, higher API prices, open-sourced agent software (pricing detail)
- GitHub — liustack/modlens (community vision plugin for dsh, MIT)
- DeepSeek Code directory — agent-vision-toolkit plugin profile (community)
- Hugging Face discussion — V4-Pro native multimodality gap (community)
FAQ
Can dsh read images now?
The harness can carry them — paste, persist, forward, plan with them. Reading still happens in the model: V4-Pro/V4-Flash are text-only, so point the vision step at a vision-capable model via the adapter config or an OpenAI-compatible endpoint.
How do I try rc.8?
npx @deepseek-ai/dsh@next — the latest tag still resolves rc.7. rc.8's SQLite storage format is incompatible with older sessions; fresh install, then re-add your provider config.
Vision-Exp launched — what about V4-Pro?
deepseek-v4-flash-vision-exp went live Aug 21, 2026 — our launch brief has the pricing, quickstart, and limits. V4-Pro vision remains unannounced.
What about my own gateway?
Supported and newly hardened — rc.8 fixes request-format and missing-reasoning failures on custom OpenAI-compatible gateways. Declare input: [text, image] on models that accept images so dsh sends them natively.