5.8 KiB
description, kind
| description | kind |
|---|---|
| Produced-files and clickable file references for the Web GUI: the deliverables row a finished turn ends with, and inline-code links in the closing prose; for users and maintainers of the deliverables experience. | package-reference |
@deepseek-ai/dsh-client-ui-deliverables
English | 中文
Summary
This package renders the deliverables row a finished turn ends with — the files the mutation tools created or modified — and links matching inline-code references in the closing prose, so a mentioned file opens in the Host. The vocabulary comes from the mutation tools' own locations, never from the closing prose — a produced file is listed whether or not the model remembered to name it. The shipped Web patch is the only composition that loads this package; removing its cordis.yml entry removes the guidance, row, and prose links together.
Table of Contents
- Use this package
- Understand the implementation
- Further Exploration
- Model Experience
- Known Limitations and Deferred Work
- Dev Note
Use this package
Mount this plugin alongside ui-conversation; a finished turn then ends with the produced-files row between the closing message's body and its action footer. Each chip opens the file through the Host opener, with relative paths resolved against the session cwd; a Show in folder action opens the session workspace when the page is loopback and the Host reports it can open paths.
The row
The row shows the largest leading prefix that fits — up to six chips, basename text with the full path as the title — reserving the exact localized + N files width, so the remainder stays visible without wrapping or horizontal scrolling.
Inline-code links
The closing prose carries the same vocabulary: an inline-code token resolves by exact path, or by being exactly the basename of exactly one produced path — a basename two paths share stays inert rather than guessing, so a mention can never open the wrong file. A resolved mention keeps its code chip and takes the markdown sheet's link language, with the full path as its title.
Understand the implementation
Implementation internals — click to expand
The Node half registers the static ui:deliverable-file-references system-prompt section asking the model to mention primary files from successful creation or modification calls and to write those and any other changed-file references as Markdown inline code. The browser half registers ProducedFiles into the chat view's conversation.chat.turnTail hole. deliverablesDefinition folds each Turn's successful first-party mutation calls into DeliverablesTurnData from the validated raw arguments of write, edit, and mutating str_replace_editor commands. Reads, deletes, unsupported tools, malformed calls, and failed results contribute nothing. A new mutation tool needs an explicit Client contribution before it joins the list. The package also provides the chatFileMentions service the chat view consults per closing message; composing the plugin out removes both surfaces and leaves the view's empty chain at zero cost.
Further Exploration
Read these pages when the deliverables surface is not enough. They move from the row to the turn-tail hole and the decisions behind the vocabulary.
- ui-conversation — declares the
conversation.chat.turnTailhole and renders the closing prose. - Workspace file links — the decision behind the produced-files row and the Host open path.
- Inline file mentions — the decision behind clickable mentions in the closing prose.
- Client package map — adjacent browser UI packages.
Model Experience
Clickable file-reference guidance
What the model sees
One fixed paragraph instructs the model to name primary files from successful creation or modification calls in its final response and to format those and any other changed-file references as exact-path or unique-basename Markdown inline code, such as out/report.html.
Token effect
One fixed prompt paragraph whenever this package is loaded; no tool schema, tool result, or per-Turn context is added.
KV Cache effect
The section is static at first-party order 9000 for the lifetime of the package mount, so it remains in the reusable prompt prefix and does not change across Turns.
Known Limitations and Deferred Work
These limits define the current deliverables vocabulary. They are current package constraints, not a general file-linking comparison or a task backlog.
- Mention matching is exact path or unique basename only — a suffix mention stays inert; widening the matcher is deferred until a real closing-message shape needs it.
- Files created indirectly by terminal commands remain outside the matching vocabulary — naming such a file in inline code does not make it clickable unless a successful mutation location also records that path.
- Native folder handoff targets the Host desktop — a browser reached through a non-loopback authority omits the action, as does a deployment reporting no native opener; SSH forwarding that makes a remote Host look loopback-local must set the gateway's
nativeOpen: false.
Dev Note
Working context for maintainers — click to expand
None.