dsh-paste-to-path
DSH Native 附件与经典的基于路径的 P2P 工作流之间的最终兼容桥接层。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add dsh-paste-to-path@0.0.7Paste To Path 以 dsh-paste-to-path 发布，当前版本为 0.0.7。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Final release: choose DSH Native or classic P2P attachments.
English | 简体中文
dsh-paste-to-path originally gave DeepSeek Harness a universal attachment Dock when the Web composer accepted only a small image whitelist. DSH 0.1.5+ now ships its own generic-file pipeline with background upload, persistence, one attachment rail, model-readable paths, and Sidebar previews.
That closes the gap this plugin was created to fill. Version 0.0.7 is the final compatibility release.
It keeps exactly two user-facing choices:
.txt attachment.The default is deliberately modern:
Take over DSH Native attachments: off
Long text as attachment: on
Files and images therefore use DSH Native by default. P2P does not register its picker or Dock and does not consume file paste or drop events.
| Takeover | Ordinary files and images | Long pasted text |
|---|---|---|
| Off (default) | DSH Native owns picker, paste, drop, upload, cards, persistence, and model paths | Converted to a .txt file and admitted through the DSH Native attachment pipeline |
| On | Classic P2P owns picker, paste, drop, path Dock, Host storage, and path references | Converted through the classic P2P path-backed pipeline |
This is exclusive ownership, not two competing attachment systems. When takeover is off, browser-provided files are left completely untouched for DSH. When takeover is on, classic P2P owns the entire attachment interaction.
The original design separated two concerns:
getting a file into the conversation
≠
understanding the file's contents
P2P saved a file on the DSH Host, inserted a path reference, and let the Agent choose an available image, document, archive, or filesystem tool. It did not wrap model capabilities or bind users to one vision stack.
DSH now follows the same core model for generic files, with a stronger durable implementation. Maintaining a second default attachment system would create duplicate UI, competing paste/drop handlers, and weaker lifecycle behavior. The correct final state is therefore Native by default, with classic P2P available only by explicit choice.
dsh plugin --profile web add dsh-paste-to-path
Then restart DSH:
dsh web
This final release targets:
DeepSeek Harness >= 0.1.5-rc.1 and < 0.2.0
Users maintaining pre-native-attachment DSH installations should pin the historical release:
dsh plugin --profile web add dsh-paste-to-path@0.0.6
On DSH 0.1.6+, open the plugin's installed-bundle page and configure the paste-to-path row. On DSH 0.1.5, the same controls remain available through the older configurable-plugin settings surface.
The profile defaults are:
- insert:
- id: paste-to-path
name: dsh-paste-to-path
config:
takeOverNativeAttachments: false
longTextAsAttachment: true
longTextThreshold: 8000
The settings UI keeps the two primary choices and nests longTextThreshold under long-text conversion. It defaults to 8000 JavaScript characters and can be changed directly from the plugin settings page or in the profile configuration.
With takeover off, P2P does not handle:
All of those remain native DSH responsibilities.
For a qualifying long text paste, the plugin creates a browser File and admits it through DSH's public Conversation attachment state machine. DSH then owns its upload, card, retry, durable storage, and read-only model path.
If native admission cannot start, the plugin does not prevent the paste, so the original text remains available to the composer.
Enabling takeover restores the historical workflow:
paste / drop / choose
↓
save on DSH Host
↓
P2P attachment Dock + reference chip
↓
send a short English path instruction
↓
Agent chooses an available tool
This mode still supports arbitrary files, image thumbnails, text editing within the configured size limit, Host-path linking, and the localhost-only Windows Explorer clipboard fallback introduced for Issue #2.
Classic mode is retained for preference and compatibility, not recommended over DSH Native for new installations.
In Native mode, attachment storage and transport are entirely owned by DSH.
In classic takeover mode:
0.0.7 is the final release of dsh-paste-to-path. The repository and historical packages remain available, but no further releases are planned: the project will not compete with or reimplement future DSH attachment architecture.
The workaround became optional because the platform fixed the underlying problem. That is the best possible ending for this plugin.