dsh-context-annotations
在 DSH 对话中的任意位置选择文本，为其附加备注，并将整个批注批次与下一条消息一并发送。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:YubaiLoving/dsh-context-annotations#6e85845aad787ec7e657d7537b3ac234b80b5370Context Annotations 以 dsh-context-annotations 发布，当前版本为 1.0.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
English · 中文
A DSH (DeepSeek Harness) Web GUI plugin: select any text in the conversation, write a note about it, and let the whole batch ride along with your next message — for that one round only.
This repository carries the dsh-plugin topic, which the DeepSeek Harness documentation requires of plugin repositories so they can be discovered; the link above is the inline, clickable form of that requirement.
The browser half owns the editing UI; the Host half owns delivery.
/api/dsh-context-annotations
(a route registered through ctx.connection.fetch, behind the carrier's trust
fence). It never writes into the draft.agent/pre-step
waterfall. pre-step hands over exactly the messages the step claimed — never
replayed history — so a batch can only ride one round. When the step carries a
source.kind === "user" message, the Host appends one extra message that holds
only the marker (💬 N 条注释) and leaves the human message byte-for-byte
unchanged.ctx.systemPrompt.section()
contributes it to the prompt, and the rendered prompt is logged as a hidden
system/message node. The conversation therefore shows one short bubble while
the request carries the full list; both are reconstructable from the log, and
no plugin event type is invented.user/message record, and the prompt is likewise
reconstructable from the log. By design, fork, resume and replay should
reproduce the conversation the model saw; no plugin event type is invented.pre-step marks it consumed (the
browser then clears the strip) and that turn's turn/end retires it from the
prompt, so a later round never inherits it. A batch that no round consumed is
left pending instead — a note written while the model is still answering waits
for your next message rather than vanishing with that turn.consumed explicitly, which marks the local annotations sent (the strip
collapses and the markers stay, dimmed). The same request adopts a still-pending
batch after a page reload.The conversation gains exactly one short message:
💬 2 条注释
The model receives the list as a system-prompt section:
1. 所选文本：
<the selected passage>
注释：<your note>
2. 所选文本：
<the selected passage>
注释：<your note>
| Path | Role |
|---|---|
lib/index.js | Host half: batch store, /api/dsh-context-annotations, agent/pre-step fold |
lib/client.js | Browser half: selection button, note editor, numbered markers, composer strip and panel |
cordis.patch.yml | Insert the plugin row into the profile |
locale/{zh,en}.json | Plugin Manager title and description |
test/smoke.mjs | Dependency-free test of the fold semantics and the browser bundle's registration |
test/client.mjs | Regression test for the browser store: per-Session push, explicit consumption, editor identity, composer exclusion |
The bundle currently reads no configuration. The folded list carries no marker line, so it reads as the user's own numbered notes rather than a plugin block.
Installed from this repository:
plugin_manager install_bundle target="github:YubaiLoving/dsh-context-annotations"
Or from a local checkout of this directory:
plugin_manager install_bundle (target: this directory)
data-* markers of the shipped
conversation shell ([data-conversation-content], [data-composer-seat],
[data-composer-card]) and the browser's own selection. No other plugin's DOM
is modified.MIT