dsh-settings-hub: Unified Management of Third-Party Plugin Settings for DeepSeek Harness
`dsh-settings-hub` is a DeepSeek Harness plugin maintained by Amengclass, designed to address the scattered and disorganized settings of third-party plugins. It aggregates all plugin settings through a unified entry point and supports dynamic discovery, automatic grouping, drag-and-drop reordering, and zero-intrusion installation. The plugin is compatible with web and desktop environments (0.1.x/0.2.x), although some plugins may not yet be supported due to differences in registration mechanisms. During installation, be mindful of the configuration requirements for pnpm 11 and the impact of browser caching on reordering.
Read Moredsh-setting-manager: Show/Hide Control for Settings Page Section Navigation
The dsh-setting-manager plugin provides batch show/hide control for DeepSeek Harness setting sections through the right-click menu. It uses `display:none` to hide sections, persists their state to a local JSON file, and supports reuse across browser sessions. It strictly follows the DSH theme, incorporates security validation mechanisms (such as loopback restrictions and protection against DNS attacks), and offers batch operations with fault-tolerant fallback. The plugin is easy to install and aims to resolve the cumbersome navigation caused by an excessive number of sections.
Read MoreDSH Settings Plus: Adds a Settings Management Interface to DeepSeek Harness
`dsh-settings-plus` is an MIT-licensed plugin developed for DeepSeek Harness (DSH), designed to address the gap in settings management within plugin-based extensions. It provides form-level and file-level settings management capabilities and exposes an SDK for other plugins to register settings namespaces. The plugin is installed to a specified DSH profile via the `file:` bundle method, rather than being built as part of the host source code. Its core capabilities include enumerating registered settings namespaces and plugin composition configurations from the live `cordis` registry, defaulting to a read-only strategy to ensure security; it realizes form-level editing via `settings.section` and the schema form renderer...
Read More