@fzhiyu/dsh-image-view
在所属的工具行内联显示 read_image 调用返回的图像
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add @fzhiyu/dsh-image-view@0.1.1Image View 以 @fzhiyu/dsh-image-view 发布，当前版本为 0.1.1。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
When the agent reads an image, show the image.
read_image already returns the picture — the tool commits the bytes through
the attachment service and hands the model an image block. The web UI just had
nowhere to draw it, so the call rendered as a grey line naming a path, and the
one thing you wanted to see was the one thing that was missing.
This plugin gives that call its own row.
before read_image · /tmp/sp-sing.png
after View image · /tmp/sp-sing.png
[ the image, right there ]
The thumbnail fits a 240px long edge, and clicking it opens the original. Nothing to expand: a row whose only real content is a picture should not make you click to find out what the agent saw.
Everything else is untouched. This registers under one key — read_image — in
the Tool UI's keyed view slot, so every other tool row renders exactly as it did
before, and removing the plugin restores the generic row on the next boot.
dsh plugin --profile web add @fzhiyu/dsh-image-view
# restart DSH
| Call state | Row |
|---|---|
| Running | Summary line with the shipped running sweep |
| Succeeded | Summary line plus the image, loading and retry included |
| Failed | The failure's first line, in the error colour, and no image |
| Interrupted | Marked stopped rather than failed |
A settled result that carries no image block degrades to its summary. The row reports what the call actually returned; it never invents a picture.
session.attachment route. A second path to that data would be a
second thing to authorize correctly.Images are read under the rendering session's own authorization, through the public session verb, and their object URLs are revoked when the plugin unloads — a screenshot pinned for the life of the page is a leak, not a cache.
Targets DeepSeek Harness 0.1.0-rc.6.