DeepSeek Harness rc.8 Adds Image Input, Not Vision

DeepSeek Shipped Image Input for Its Agent CLI. Its Own Models Still Cannot See.

Release candidate 8 wires up an image transport path — for third-party vision models. Chinese coverage read it as a V4 spoiler.

DeepSeek published dsh-v0.1.0-rc.8 of DeepSeek Harness, its first-party coding-agent client, at 15:37:57 UTC on 19 August. The timestamp comes from the GitHub Releases API on DeepSeek's own repository; the previous candidate, rc.7, went out two days earlier.

What actually changed

The headline item is multimodal plumbing: the DeepSeek model adapter can now be configured to send native image requests, and /goal and /plan accept images alongside text. The @ reference menu expands from files to conversation history. Windows PTY gains persistent PowerShell sessions, on by default in the Minimal preset. Web search runs concurrently. Fixes cover model failures from oversized image payloads, lost response prefixes after stream cancellation, and OpenAI-compatible gateway incompatibilities.

What the common telling gets wrong

Chinese tech press ran this as a spoiler for a vision-capable DeepSeek V4. That is inference, not an announcement, and it inverts what shipped. DeepSeek added no vision model. It added an image transport path in the client — the practical effect of which is that you can wire a third-party vision model into Harness by hand. Second, this is a release candidate, the eighth of an unreleased 0.1.0, and describing it as a product launch overstates it. Third, the item most likely to affect a user is buried at the bottom: the SQLite backend optimisation is incompatible with the prior on-disk format.

The distribution move

rc.8 makes Claude Code and Codex installable as optional Profile Bundles inside Harness, and gives Codex a non-interactive permission mode and multiple named instances. DeepSeek is not merely shipping a client so its models have a home — it is making competitors' agents run inside its shell. The strategy is to own the surface, not just the weights.

A dating note worth keeping

ITHome carried this release on 20 August Beijing time, roughly 15 and a half hours after it was published. That lag is typical, and it is why a China desk that dates stories from Chinese datelines will be wrong most days. The repository timestamp is the event.

Why It Matters

The Chinese labs are building their own agent clients rather than leaving distribution to Cursor, Claude Code and Codex — and DeepSeek is going further by hosting those rivals inside its own shell. Image plumbing arriving before any DeepSeek vision model is a sequencing tell, not a product.