Every DeepSeek Harness plugin

What it is — DeepSeek Harness plugin providing reviewed plan DAG, runtime-owned settlement, event-log truth, and resident reconciler for long-horizon multi-agent tasks.

Who it is for — In DeepSeek Harness web workspaces executing long multi-step planning and review tasks, this plugin is suitable for users missing runtime-owned settlement and reconciler support. If tasks are limited to single-turn dialogues without involving persistent logging or dependency reviews, this plugin's capabilities are not required.

Watch out — Sandbox test passed: installed in a new profile and registered in DeepSeek Harness. No obvious pitfalls found.

The verdict — I will install it because it is designed for tasks requiring hours rather than turns.

What it is — dsh-login-gateway plugin provides an external login gateway for DeepSeek Harness dsh Web UI. After username and password authentication, it fully proxies requests to 127.0.0.1:3080, supporting WebSocket. Zero runtime dependencies.

Who it is for — If you need to access dsh Web UI from external networks but it only listens to 127.0.0.1 internally, this plugin provides a login wall and full reverse proxy. Users who use dsh entirely in an isolated environment do not need this plugin.

Watch out — Installation from source involves executing shell commands. Sandbox test passed: it installs in a fresh profile and gets registered by harness. No obvious issues detected.

The verdict — If I were you and needed to securely expose dsh Web UI externally, I would install it because it adds authentication without modifying the dsh core.

What it is — dsh-history plugin enables viewing all sent messages in long sessions with search and positioning support.

Who it is for — This plugin is suitable for users handling long conversations in DeepSeek Harness web interfaces. It is not suitable for users who need to manually load history, as it supports background prefetching of the complete list on session start.

Watch out — After installation, the restart script must be run to activate the plugin in sessions. Sandbox testing passed and it was successfully registered into the profile. No obvious pitfalls were found.

The verdict — I would install it because it offers a dedicated approach to viewing history in long conversations.

What it is — MyCordis makes Cordis plugins in DSH manageable and enables one-click generation of installation packages.

Who it is for — When you want to batch process Cordis plugins in DSH, MyCordis can complete packaging and installation management through a page. If you focus on developing non-Cordis plugins, you do not need to install this plugin.

Watch out — It successfully passed sandbox test: installed in new profile and registered by harness. It will execute shell commands. No obvious pitfalls found.

The verdict — I would install it because it saves tokens when rebuilding plugins across sessions.

What it is — dsh-what-changed plugin adds a file-change counter button to the DeepSeek Harness web session header, clicking the panel to show exact modified files and diffs.

Who it is for — When an agent uses DeepSeek models in web mode and modifies several files in one session, the user needs to see which files were changed before deciding to commit. It is unsuitable for users who only run pure CLI tasks without any file writes, as they do not need to track agent modifications.

Watch out — Tested successfully in a fresh profile: button registers correctly, counter updates in real time, supports language switch, panel shows actual tool-written diffs. No obvious issues found, though it executes shell commands to fetch events.

The verdict — I would install it because it turns session-level changes into a decision-ready panel without needing external tools.

What it is — DeepSeek Harness plugin that intercepts write/edit/str_replace_editor before execution to show red/green line diff for user approval or rejection.

Who it is for — In code editing tasks on the DeepSeek Harness web profile, this plugin intercepts tool calls to show diff before modification. Users using the never approval policy session do not need this plugin, because it respects the session approval policy and lets the sandbox enforce directly.

Watch out — Sandbox test shows it can be installed but the build script is blocked by pnpm, preventing harness registration. Users need to manually allow the build script from source installation to complete registration. No obvious issues found.

The verdict — I would not install it because it never changes the sandbox mode, only respects existing policies.

What it is — PR evaluation advisor that assesses the success probability of PR submissions based on historical patterns and provides actionable suggestions.

Who it is for — Developers submitting PRs to other open-source repositories can use this tool to assess the success probability before opening them. Individuals focused only on maintaining their own repository can choose not to install it.

Watch out — Installation from GitHub source requires manually allowing the build script to execute. The sandbox test confirmed it runs normally after installation in a fresh profile and registration.

The verdict — I would install it because it supports structured monitoring of outbound PRs across repositories, but only if you are in a Python environment.

What it is — dsh-github-release-radar plugin provides four GitHub API tools for DeepSeek Harness agents: github_releases, github_repo, github_search, and github_repo_tags. These tools allow direct calls to GitHub REST API for public repository data without API key.

Who it is for — When using DeepSeek Harness agents to analyze open-source projects, this plugin exposes tools for accessing releases, repository overview, search, and tags. If your agent workflow does not involve external GitHub repository queries, you may choose not to install this plugin.

Watch out — Sandbox testing showed that the plugin can be loaded into the sandbox but its build script is blocked by pnpm; users need to manually allow the build for github:zoahdev/dsh-github-release-radar to complete harness registration. The plugin supports optional githubToken configuration to increase the anonymous 60 requests per hour limit. No obvious runtime issues were found.

The verdict — I would not install it because manual build allowance is required to complete registration, and there is no evidence of its long-term stability.

What it is — The plugin adds a share button that freezes the current conversation into a read-only HTML snapshot for LAN sharing.

Who it is for — Local network team members who need to share the conversation to other devices fit installing it. Users needing cross wide-area multi-device collaboration are not suitable to install it.

Watch out — On Windows, first access to 0.0.0.0 may trigger firewall prompt. Sandbox test passed. No other obvious issues found.

The verdict — I would not install it because the shared page is not a live view of the session.

What it is — The plugin translates system prompts, tool descriptions, and runtime contexts into Chinese at runtime using DeepSeek Harness's system-prompt/assemble waterfall hook. It covers sections, contexts, tools, and cordis API directory without modifying any DSH source code. Uninstalling restores the original English.

Who it is for — Users working with DeepSeek Harness models in Chinese-language tasks who need localizations for prompts and tool descriptions can install this plugin. Those without Chinese interaction requirements or using models that already support Chinese natively may opt out.

Watch out — Tested successfully in a fresh profile where it registered with harness. Configurable via includeSections, includeContexts, includeTools (all default true) and verbose for debugging. No obvious issues found in sandbox testing. It executes shell commands as a noted behavior.

The verdict — I would install it because it provides runtime-only localization without source modifications, offering value for non-English deployments.

What it is — Provides countdown tools for 64 Chinese exams with rule-aware date math.

Who it is for — Suitable when querying exam countdowns via DeepSeek Harness agents. Not needed when not using agent tool calls in DeepSeek Harness.

Watch out — Source install requires manual approval of the build script. Sandbox test passed in new profile with registration. No obvious issues found.

The verdict — I would install it because it gives agents direct access to exam countdowns, but I would confirm dates with official sources.

What it is — This plugin provides a usage statistics dashboard for the DeepSeek Harness Web UI, showing token usage and model usage.

Who it is for — If you need to view your usage patterns in the DeepSeek Harness Web UI, you can install this plugin. If you prefer other types of dashboard features, you can skip it.

Watch out — Sandbox test passed: installed in a new profile and registered by harness. No obvious issues found.

The verdict — I would install it because it provides local usage analysis without any upload.

What it is — Generates per-session cost and usage report cards for DeepSeek Harness sessions, covering tokens, cache hits, and duration.

Who it is for — Fits users who need to track token consumption and duration in each turn while using DeepSeek Harness for multi-turn conversations. Does not fit users who do not need to view cache hit rates, as they may not require these specific metrics.

Watch out — No obvious issues found. Tested successfully in a fresh profile, where it is registered with harness.

The verdict — I would install it because it provides per-session token usage tracking for later analysis.

What it is — A collapsible draggable floating music player plugin that supports NetEase Cloud Music playlist import, search and chat control of music via agent.

Who it is for — Users who chat with the agent in DeepSeek Harness Web and want to control music in the conversation are suitable for installation. Users who do not use NetEase Cloud Music as the audio source can use other solutions.

Watch out — Sandbox test passed. No obvious issues found. Restricted songs may fail to play full audio in anonymous mode.

The verdict — I would install it because it provides direct music control through the agent tool in chat.

What it is — Floating widget displays real-time OpenCode Go subscription usage for every API key.

Who it is for — When managing OpenCode Go API keys in a DeepSeek Harness web profile and needing real-time quota monitoring, this plugin is suitable to install. If you do not provide an OpenCode Go API key or token, you do not need this plugin.

Watch out — Sandbox test passed: installed in a fresh profile and successfully registered with DeepSeek Harness. No obvious issues found.

The verdict — I would install it because it supports automatic key-pool discovery for multi-window quota display, but the premise is that you need to use it in a DeepSeek Harness web profile.

What it is — Universal image generation router for DeepSeek Harness that auto-discovers image models from OpenAI-compatible endpoints and integrates with agent tools and REST API.

Who it is for — When your DSH agent needs to generate images in conversation like drawing diagrams, you can install this plugin to enable draw_image tool. Users who do not require image generation in their agent workflows do not need to install it.

Watch out — It requires executing shell commands during source build. Sandbox test passed when installed in a fresh profile and registered to the harness.

The verdict — I would not install it because I have no need for agent tools to generate images.

What it is — Adds native vision capability to DeepSeek Harness, supporting Zhipu free interface or local Qwen-VL model.

Who it is for — If you need to add vision support to DeepSeek Harness, install dsh-vision. If your model already has built-in vision functionality, you can skip this plugin.

Watch out — Sandbox test passed: installed in fresh profile and registered by harness.

The verdict — I will install it because it supports the free Zhipu interface.

What it is — This is an incremental code reviewer plugin for DeepSeek Harness.

Who it is for — When processing code changes generated by the agent in DeepSeek Harness, this plugin supports incremental display of differences. Users without a git repository do not need to install it.

Watch out — Sandbox testing succeeded: it installed and registered successfully in a fresh profile. No obvious issues found.

The verdict — I would install it because it enables feedback injection without interrupting the agent's work.

What it is — Provides reverse tunnel for DSH Web GUI, allowing remote devices to expose deployment via frp and manage workspace in the in-app browser.

Who it is for — When using DSH web profile and needing to manage workspace from a phone or remote machine. If all operations are local without remote access needs.

Watch out — No obvious issues found. Requires frp client configuration and environment variables.

The verdict — I would install it because it enables remote access to the web GUI from external devices, but only if frp can be configured.

What it is — Enables agents to access local files on the browser machine and perform read/write operations on authorized directories.

Who it is for — When using DeepSeek Harness, the agent needs to access local directories on the browser's machine in a remote deployment scenario. Users who only require host machine file operations in local setups do not need to install it, as they can use the built-in fs tools.

Watch out — Sandbox test passed: installed in a new profile and registered into DeepSeek Harness. No obvious pitfalls found.

The verdict — I will install it because it allows agents to operate local files on the browser machine and the sandbox test passed.

What it is — Plugin that automatically displays quota and usage for configured providers in the DeepSeek Harness web interface.

Who it is for — Developers configuring multiple providers in the DeepSeek Harness web interface are suitable for installing it. Users only using providers without remaining balance query endpoints are not suitable for installing it.

Watch out — Sandbox test passed: it was installed in a fresh profile and registered into the profile. No obvious issues found.

The verdict — I would install it because it auto-discovers providers and provides a settings panel, but only if my workflow requires web-interface quota monitoring.