DSH Plugin Registry

DeepSeek Harness Plugin Directory

Search and compare installable DeepSeek Harness plugins across the full DSH Plugin Registry. Filter by category, plugin type, verification status, and repository activity.

2497plugins
Page 57 of 105
View plugin dsh-memory

dsh-memory

qwert702/dsh-memory

1GitHub stars
Manifest Valid

Long-term memory plugin for the DeepSeek Harness Web GUI with project/global stores, automatic memory extraction and prompt injection.

DSH Profile: webv2.0.0
View plugin
View plugin dsh-rss-daily

dsh-rss-daily

shangjian2023/dsh-rss-daily

2GitHub stars
Manifest Valid

A DeepSeek Harness plugin that creates daily RSS news digests, optionally edits them with the configured DSH model, and delivers them through supported webhooks.

DSH Profile: webv0.3.4MIT
View plugin

About the DeepSeek Harness Plugin Directory

The DSH Plugin Registry organizes installable community plugins for DeepSeek Harness into a searchable directory. Browse plugins by capability, plugin type, verification status, repository activity, and category while keeping the source repository visible for every entry. Each registry page connects plugin discovery with install information, source-backed capability analysis, security signals, compatibility evidence, and other facts that help users evaluate an extension before installing it.

How Plugins Enter the Registry

DSH Plugin discovers projects from the public DeepSeek Harness plugin ecosystem and community submissions. A repository is not treated as an installable plugin simply because it uses the dsh-plugin topic. Registry classification checks source evidence, package and bundle metadata, install information, and plugin identity before a project is published as a plugin or plugin bundle. This keeps the directory focused on usable DeepSeek Harness extensions instead of mixing plugins with unrelated repositories, tutorials, SDKs, wrappers, or other resources.

How to Choose a DSH Plugin

Start with the capability you need, then check the plugin's target DSH profile, source repository, recent activity, license, install path, and documented limitations. Security Signals surface dependencies, lifecycle scripts, manifests, and other source facts. Compatibility Evidence records version-specific runtime results and clearly distinguishes tested and untested combinations. These signals make comparison easier, but third-party plugin code should still be reviewed before installation.