Every DeepSeek Harness plugin

What it is — The attention reminder plugin for the DeepSeek Harness Web UI.

Who it is for — When using the DeepSeek Harness Web UI to handle sessions, one needs to be reminded of waiting input or unopened sessions. If not using the DeepSeek Harness Web UI for session handling, this plugin is not necessary.

Watch out — The sandbox test passed: in a fresh profile the plugin is installed and registered by harness. No obvious issues found.

The verdict — I would install it because it shares counts from the built-in sessions store for reminders without depending on extra code.

What it is — Records model request token usage to per-day JSONL files and displays stats charts with per-model breakdown in Web settings page.

Who it is for — In DeepSeek Harness web UI for content generation tasks using DeepSeek models, someone who needs to track token consumption is suitable for installing this plugin. Users not concerned with model pricing details need not install this plugin.

Watch out — Sandbox test passed with installation in a new profile and successful registration. History backfill runs on first startup. No obvious issues found.

The verdict — I would install it because it provides live cost calculation and pricing dialogs based on model rates.

What it is — DSH Web UI settings page manages inspection, addition, removal, enable/disable and live status viewing of MCP servers.

Who it is for — Users who need to manage MCP servers in DSH web UI. Users who prefer managing MCP servers in non-DSH web UI environments can use other ways.

Watch out — Sandbox test passed: successfully registered in new profile. Static check indicates it will execute shell commands. No other obvious issues found.

The verdict — I will not install it because it will execute shell commands.

What it is — DeepSeek Harness plugin to chat, monitor, and approve DSH agents from WeChat via iLink gateway.

Who it is for — If you want to chat with, monitor, and approve DSH agents using WeChat, it provides session targeting and digest heartbeats. If you have other WeChat agent tools already set up, you do not need this plugin.

Watch out — From source installation, pnpm blocks the build script for github:Jesse-njx/dsh-chatnode-wechat, requiring manual approval to complete harness registration. No obvious pitfalls found, but must use a dedicated WeChat account to avoid 403 errors. It can execute shell commands but static checks are just warnings.

The verdict — I would install it because it allows approving DSH agents via WeChat, but only after manually allowing the build script and using a dedicated account, as the gateway is unofficial.

What it is — Displays OpenCode Go quota progress ring left of the model selector.

Who it is for — When using OpenCode Go model in DeepSeek Harness for tasks, users who need to monitor quota remaining are suitable to install this plugin. Users who do not want the browser to execute shell commands can skip installing it, as the plugin requires the host to run subprocesses.

Watch out — Sandbox test passed: installed in a fresh profile and registered into the profile. Requires shell command execution; on Windows it may require configuring sandbox workspace root to avoid ACL restrictions.

The verdict — I would install it because it can inject quota status into the system prompt, saving token usage.

What it is — dsh-eval-harness is a DeepSeek Harness plugin that runs YAML-defined cases against real headless agents, asserts on tool calls/args/results/token usage, and provides a baseline gate for CI regression testing.

Who it is for — When using DeepSeek Harness inside a CI pipeline to execute real agent runs and assert plugin behavior, this plugin supplies YAML-driven cases and gate logic.
If you only need manual plugin documentation and do not require automated regression gates, you do not need to install this plugin.

Watch out — Static checks indicate shell command execution. Sandbox testing confirmed successful installation and registration inside a fresh profile.
No other obvious issues were observed.

The verdict — If CI regression testing with baseline gates is required, this plugin is worth installing because it embeds the gate directly into workflow exit codes.

What it is — Provides secondary working directories for DSH projects, allowing the agent to edit multiple repositories side-by-side in the primary workspace.

Who it is for — When the agent needs to maintain source code, test, and docs repositories simultaneously in the primary workspace, this plugin provides the necessary support. Projects that use only a single working directory do not benefit from this plugin.

Watch out — Sandbox testing passed after installation in a fresh profile, and it was registered with Harness. No obvious pitfalls were found.

The verdict — I would install it because it enables simultaneous multi-repo editing in the primary workspace, with the premise that write operations must correctly specify the workdir.

What it is — Mobile layout fixes for DeepSeek Harness Web UI on narrow screens.

Who it is for — If you use DeepSeek Harness Web profile and access it in a narrow-screen browser for conversation, this plugin is needed to fix mobile layout issues. If you use a desktop browser or do not care about mobile compatibility, it is not needed.

Watch out — No obvious issues found. After installation, opening Web UI in narrow-screen browser repairs layout problems for settings panel, sidebar, and popups.

The verdict — If you use DeepSeek Harness Web profile and access it in a narrow-screen browser for conversation, this plugin is needed to fix mobile layout issues.

What it is — dsh-vision adds vision capabilities to text-only DeepSeek in Harness, using Doubao Web by default for zero-cost image recognition with memory and cache.

Who it is for — If you're using DeepSeek to review UI screenshots or complex diagrams, dsh-vision can automatically analyze them. Not everyone needs vision features.

Watch out — Shell commands are executed during install. Sandbox testing passed on a fresh profile. No obvious issues found.

The verdict — I wouldn't install it unless you value zero-cost browser-based vision over other paid APIs.

What it is — Integrates Edge TTS and RVC for voice reading of assistant replies in DeepSeek Harness web UI.

Who it is for — In the DeepSeek Harness web profile, this plugin enables voice reading of assistant replies. Users who do not use the web profile will not be able to use this plugin.

Watch out — Sandbox test confirmed successful installation in a fresh profile and registration by Harness. No obvious issues found.

The verdict — I would install it because the sandbox test passed and it supports RVC custom voices, but only if voice feedback for replies is needed, with the premise of using the web profile.

What it is — This plugin bridges QQ private and group chats to DeepSeek Harness, giving each conversation an isolated persistent agent session that supports commands, approvals, multimedia, and outbound files.

Who it is for — When you need to interact with DeepSeek Harness agents directly via QQ private or group chats, this plugin is suitable. If your DeepSeek Harness tasks do not involve QQ as the input/output interface, you do not need this plugin.

Watch out — Sandbox test shows the plugin installed as an ordinary dependency and did not extend to a profile layer. This is not a defect, as the plugin is not of bundle type. No obvious issues found.

The verdict — I would install it because it enables direct QQ-to-agent interaction in DeepSeek Harness, but only if QQ is the primary interface for your tasks.

What it is — Agent Client Protocol server for DeepSeek Harness.

Who it is for — When DeepSeek Harness requires real-time streaming, reasoning trace and MCP tools support, this plugin is suitable. For users who do not want the plugin to execute shell commands, this plugin is not applicable.

Watch out — Sandbox test shows it can be installed but pnpm blocks builds for @deepseek-ai/dsh-subprocess-local@ 0.1.0-rc.6, koffi@ 3.1.5, and node-pty@ 1.1.0, preventing full harness registration. Manual permission must be allowed for the build script to complete installation. No obvious other issues found.

The verdict — I would install it because it supports MCP tools and session recovery, but manual build permission is required to complete registration.

What it is — The dsh-openviking plugin integrates OpenViking retrieval, resource management, and session memory into DeepSeek Harness.

Who it is for — When handling multi-turn dialogues in DeepSeek Harness that require persistent memory, this plugin is suitable. If your work only involves local file management, you can use other tools.

Watch out — Sandbox testing passed, with installation and registration in a new profile. Plugin configuration involves setting the endpoint in cordis.patch.yml. No obvious issues were found.

The verdict — If I were you, I would install it because it supports cross-tool sharing of the same memory set.

What it is — Integrates local Codex CLI into DeepSeek Harness to enable text-based models with image viewing and file reading capabilities.

Who it is for — For users running DeepSeek-V4-Pro in DeepSeek Harness who need to analyze images or read files. If you can call Codex CLI independently without plugin integration in DSH, you can skip it.

Watch out — Requires Windows, Node.js 22.5+, and Codex CLI installation. Some modes are experimental. Sandbox test passed with registration in new profile.

The verdict — I would install it because it provides vision and supervision for text models, but only if you have a Windows setup with Codex CLI.

What it is — Provides SQLite or PostgreSQL session persistence backend for DeepSeek Harness.

Who it is for — Suitable in scenarios where session data persistence is needed in DeepSeek Harness. Users who do not require relational database persistence can choose other solutions.

Watch out — The sandbox test shows it can be installed but the build script is blocked by pnpm. From source installation, manual approval of the build script is required to complete registration. No obvious issues found in other aspects.

The verdict — I would install it because it provides RDB session persistence, but I must note the manual build approval step.

What it is — Provides Agent2Agent realtime mesh capability, including project registry and message history.

Who it is for — When you need to implement real-time message sharing between multiple agents in DeepSeek Harness, this plugin can meet the need. If you only handle independent tasks for a single agent, you do not need this plugin.

Watch out — When installing from source, you need to manually allow its build script. Sandbox test shows it can be installed successfully but the build script will be blocked by pnpm, preventing registration. No other issues found.

The verdict — I would install it because it enables real-time message mesh between agents, but I need to manually allow the build script execution as an extra step.

What it is — This DSH Web plugin allows dragging to adjust the width of AI reply message columns.

Who it is for — When analyzing long table data in DSH Web, if the fixed width leads to horizontal scrolling and makes screenshots inconvenient, install this plugin. Users who prefer to keep the default width without adjustment can skip it.

Watch out — Sandbox test passes after installation in a new profile with harness registration. Width settings are persisted via localStorage and take effect live without page refresh. No other issues found.

The verdict — I would install it because it addresses the fixed width issues for table data in DSH Web, but only if the user is doing table analysis.

What it is — DSH Web input history plugin: supports Ctrl+Up / Ctrl+Down to recall and switch sent messages.

Who it is for — Particularly useful when editing multi-line inputs in DSH Web and needing quick access to previous messages. Not suitable for users who prefer not to use keyboard shortcuts in this way.

Watch out — Installation requires building from source, which involves manual approval of the build script. Static check hints at possible shell command execution. Sandbox test passed in a new profile with no issues found.

The verdict — As someone using DSH Web, I would install it because it offers a terminal-style way to navigate input history, but only if I accept the source build requirement.

What it is — The dsh-win-notify plugin pops up Windows Toast notifications with sound when DeepSeek Harness agents complete tasks. Clicking the notification can switch to and foreground the DSH tab.

Who it is for — Users running DeepSeek Harness in headless profile on Windows who need notifications for task completion are suitable for installing this plugin. Users not on Windows or who do not require notification features do not need to install it.

Watch out — It was tested in a fresh profile and registered successfully. The sandbox environment passed the test. The plugin only depends on Windows built-in PowerShell 5.1 with no additional dependencies.

The verdict — I would install it because it provides task completion notifications on Windows and allows direct foreground switching to DSH tabs, which is useful in headless setups.

What it is — DeepSeek Harness usage recorder plugin records per-model hourly token usage and displays stacked bar chart in the Web GUI.

Who it is for — When monitoring token usage in DeepSeek Harness web profile, this plugin is suitable. Users who do not use the web GUI can skip this plugin.

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

The verdict — I would install it because it provides specific token usage statistics in the GUI, but only if web profile is used.

What it is — Aggregate remote DeepSeek Harness servers' sessions and local tools' history dialogues into the official Web UI, providing hub gateway and official UI bridge.

Who it is for — When managing development tasks across multiple remote servers with DeepSeek Harness, needing to unify sessions and history from various machines in one workspace tree. If you only operate on a single local machine without needing cross-server aggregation or importing other tools' logs, no need to install this plugin.

Watch out — Installation requires manually allowing the build script, as it's blocked by pnpm. In sandbox testing, cpu-features@0.0.10 and ssh2@1.17.0 prevented full harness registration. It's an alpha version with potential config changes before 1.0.

The verdict — If I need to unify multi-machine session history in a cross-server environment, I would install it because it allows remote agents to run in the background without relying on local connections, but manual build approval is required for full functionality.

What it is — Provides cross-session message passing and decision recording for DeepSeek Harness agent sessions to avoid repetition, contradiction or deadlock.

Who it is for — When agent sessions collaborate on code in different work directories, they need to verify changes through declarations and messages to prevent conflicts. Users running a single session independently do not need it, because multi-session interaction is not required.

Watch out — Sandbox testing passed in a fresh profile and was registered with harness. Static check indicates it executes shell commands. No obvious issues found.

The verdict — I would install it because it records decisions to handle multi-session deadlocks, but only when multiple concurrent sessions are involved in the workflow.

What it is — Provides structured safe Git tools for DeepSeek Harness, including git_status, git_diff, log, branch, stage, commit, stash, show, fetch, pull, remote, checkout with a guard against destructive commands.

Who it is for — In coding agents within DeepSeek Harness, when they need to execute Git operations, this plugin offers structured safe alternatives. If you are not using DeepSeek Harness, you do not need this plugin.

Watch out — Sandbox testing passed in a fresh profile with harness registration. No obvious issues found. The plugin executes shell commands.

The verdict — I would install it because it parses outputs into structured JSON instead of prose.