Configuring dsh-find-plugin
DeepSeek Harness installs dsh-find-plugin into the web profile when the documented installation flow is used. Restart dsh web after installation so DeepSeek Harness loads the plugin in the web session. The README does not document configuration keys, environment variables, or user-editable configuration files.
Commands and tool behaviour
The plugin registers the find_dsh_plugin tool. DeepSeek Harness may invoke it when the agent receives a request that would benefit from discovering a plugin. A request can describe a capability or name a category, such as terminal TUI tools, WeChat notifications, or Git diff review.
The tool performs a live GitHub repository search scoped to the official dsh-plugin topic. It re-ranks the results by stars and returns each result with:
- a star count;
- a one-line description;
- a repository link; and
- a ready-to-run
dsh plugin add command.
The returned command can be given to the agent for execution, but the README treats discovered plugins as third-party code.
Curated descriptions
When a GitHub result is also present on awesome-dsh-plugin, dsh-find-plugin replaces the GitHub description with the hand-written bilingual description from plugins.json. The lang parameter selects the language. This substitution does not alter the star-based ranking.
Caching and review
GitHub searches use an anonymous API and have a five-minute, per-query cache. The README does not specify a cache file path or a setting for changing the cache duration. Review a discovered repository’s source before installation and pin a commit rather than relying only on the generated command.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub