description, kind
| description | kind |
|---|---|
| Recommend built-in official plugins for explicit user needs and enable them from conversation cards. | package-bundle |
@deepseek-ai/dsh-experimental-plugin-recommendations
English | 中文
Summary
Users can discover a relevant built-in plugin while discussing a concrete need. The Agent answers first, then offers one card at the completed Turn’s end; the user can open its plugin details, choose Enable, or choose Not now. Enable applies through HMR and automatically notifies the Agent; no page refresh or follow-up message is needed. Enabling changes the whole profile and persists across restarts. Only an immediately applied change resumes the original request. Users can later disable or remove the plugin from its details page.
Table of Contents
- Use this package
- Understand the implementation
- Further Exploration
- Model Experience
- Known Limitations and Deferred Work
- Dev Note
Use this package
Enable Plugin recommendations in the Plugins page’s Experimental plugins group. Shipped profiles leave this experimental bundle disabled. It has no configuration fields.
- name: @deepseek-ai/dsh-experimental-plugin-recommendations
Outcomes and recovery
Enable requires permission to modify the profile. The Host rechecks catalog eligibility before changing it. A saved selection can require restart or be overridden; those outcomes do not resume the Agent. Failed and cancelled changes can be retried. A lost response leaves the outcome uncertain until the Session projection reconnects; repeated card actions are idempotent.
Understand the implementation
Implementation internals — click to expand
The catalog and activation reuse pluginManager. The main Agent interprets expressed needs; Host code enforces the official shipped catalog, one successful proposal per Turn, and a separate human action. Concurrent proposals reserve the Turn before catalog lookup; failed proposals release that reservation. Replaying a settled proposal preserves the limit after reload, while a later Turn can recommend again. Trusted catalog text is persisted in tool-result metadata, while a Session projection folds decision receipts. Concurrent actions on one card share an operation, and disposal drains admitted changes. Profile files own installation state; experimental Session records only own the historical decision. Removing the bundle withdraws tools, cards and its generated Remote contribution.
Further Exploration
- Plugin manager — profile changes.
- Session projection — durable derived state.
- Recommendation cards — completed-answer placement.
- Conversation UI — transcript placement.
Model Experience
Recommendation tools
What the model sees
list_official_plugins returns disabled eligible plugins. suggest_plugin records one proposal with the explicit need and explanation. A successful user activation appends a notice containing that need. It directs the Agent to continue only already requested work; discovery-only requests end with a brief activation confirmation, without expanding into account-wide searches or bulk edits. Tool descriptions restrict recommendations to expressed needs; this is semantic guidance, not an intent classifier enforced by the Host.
Token effect
Two tool schemas are present while the experimental bundle is enabled. Catalog results, recommendations and successful activation notices append context.
KV Cache effect
Recommendation facts append to the transcript. Enabling a plugin can change subsequent tool declarations and their cache reuse.
Known Limitations and Deferred Work
Intent cases are in tests/fixtures/intent-cases.json. Tool guidance asks the Agent to clarify vague needs, respect a request not to recommend, and produce one concise final answer after proposing. These semantic decisions are evaluated with real model runs; they are not keyword guards.
- Only shipped, optional, official plugins are eligible; missing packages and third-party registries are excluded.
- Recommendations require a live root conversation; there is no unsolicited opportunity discovery.
- A historical receipt does not continuously track changes later made on the Plugins page.
Dev Note
Working context for maintainers — click to expand
None.