Every DeepSeek Harness plugin

What it is — This DSH plugin allows the agent to autonomously call context_compact to compress chosen conversation spans into self-written checkpoints.

Who it is for — When using DeepSeek Harness for agent-driven multi-step tasks that require compressing completed conversation spans to retain opening task plans, this plugin is suitable for installation. Users who handle only single-turn conversations do not need this plugin, since they do not require span compression.

Watch out — Sanbox test passed: successfully installed and registered into the harness in a fresh profile. No obvious pitfalls found.

The verdict — I would install it because it keeps information loss from compaction as small as possible, with the premise of using the agent to autonomously call the tool.

What it is — DeepSeek Harness plugin operates local Obsidian knowledge base, providing search, note read/write, bidirectional links and batch organizing.

Who it is for — When using DeepSeek Harness to manage Obsidian knowledge base, people needing note read/write and search capabilities are suitable for installation. If not concerned with Obsidian command triggering and relationship graph generation, people not suitable for installing this plugin.

Watch out — Sandbox test passed: installed in a new profile and registered into the profile by harness. Installation will execute shell command. No obvious pitfalls found.

The verdict — I would install it because it supports independent local vault operation via the file channel and Obsidian Local REST API enhancement.

What it is — DeepSeek Harness settings interface adds a skin switching page

Who it is for — Users who switch skins in the DeepSeek Harness Web GUI settings panel are suitable for installing this plugin. Users who do not use DeepSeek Harness Web GUI do not need to install this plugin.

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

The verdict — I would install it because it supports hot switching without restart.

What it is — Integrates file browsing into DeepSeek Harness Web UI, supporting workspace directory preview and editing.

Who it is for — Users who need to browse workspace folders in the DeepSeek Harness Web UI are suitable for this plugin. Those not using DeepSeek Harness Web UI can choose independent file management tools.

Watch out — Sandbox testing confirmed that the installation command succeeds, but it loads as an ordinary dependency without becoming a profile layer. No obvious issues detected.

The verdict — I would install it because it provides workspace file preview, but only as an ordinary dependency in the DeepSeek Harness Web UI environment.

What it is — This plugin serves as a Feishu entry point for DeepSeek Harness, driving DSH agents via Feishu bots with streaming cards, interactive buttons, and attachments.

Who it is for — If you need to direct DSH agents in Feishu group chats for handling images or files, this plugin fits your setup. Users who run DSH on Telegram or Discord without Feishu integration do not need it.

Watch out — Sandbox testing requires manually allowing the build script to complete registration. The blocked package is protobufjs@7.6.5. No other issues found.

The verdict — I would install it because it provides a dedicated Feishu interface for DSH agents, but only after manually permitting the build script.

What it is — This is a VS Code extension that integrates DeepSeek Harness as a right-side chat agent, allowing it to read, edit, and run project files.

Who it is for — When you are using DeepSeek models in VS Code to handle project code, it fits. If you do not want to integrate a chat agent in the VS Code sidebar, or already have alternative tools, it does not fit.

Watch out — You need to download the vsix file from GitHub and install it in VS Code; it can execute shell commands; no obvious issues were found. Sandbox testing passed in a fresh profile and was registered into the harness profile.

The verdict — If you are already developing in VS Code and need AI-assisted editing and running, I would install it because it directly uses DeepSeek Harness; but if you only want browser use or have other integrations, you could skip it.

What it is — A DeepSeek Harness plugin for inspecting MCP status and managing MCP servers through the command and settings panel.

Who it is for — If you are using the web profile of DeepSeek Harness to inspect MCP server status and manage servers, this plugin is suitable. If you are using a different profile, this plugin does not apply.

Watch out — Sandbox testing shows the plugin can be installed but pnpm blocks the build script for github:kairoz9/dsh-mcp-admin, preventing harness registration. Users must manually allow the build by adding the key to the profile's pnpm-workspace.yaml. No other obvious issues were found.

The verdict — If I were you, I would install it because it allows managing MCP servers in the settings panel and writing back to cordis.patch.yml, but requires manually allowing the build script to complete installation.

What it is — dsh-file-panel adds a right-side file panel to DeepSeek Harness, automatically popping up when the agent creates or downloads files, with image/text preview, reveal-in-folder, and open actions.

Who it is for — When using the DeepSeek Harness web GUI to develop or debug with an agent that generates files, install this plugin. It is not necessary for users who do not run the web interface or prefer command-line only workflows.

Watch out — Installation requires adding from GitHub or local source, with a manual build script approval step. Sandbox testing passed in a fresh profile with harness registration. Shell command execution is a static check note, no other issues found. It only activates for localhost connections.

The verdict — I would install it for web GUI agent sessions needing file handling, as it provides direct session file management not covered in the prior sections.

What it is — dsh-tui is a terminal interface plugin that provides a TUI entry for DeepSeek Harness.

Who it is for — Users who drive agent tasks from the terminal suit installing it. Non-TTY users need not install it because it requires real terminal input.

Watch out — Sandbox testing shows it installs but is blocked by pnpm on a build script; manual approval is needed for registration. No other issues found.

The verdict — I would install it for the terminal TUI but must manually approve the build script first.

What it is — DSH Forge is an isolated development environment for DeepSeek Harness plugins, supporting configuration synchronization and plugin experiment management.

Who it is for — Plugin developers who need to test new DeepSeek Harness features in isolation should install it. Users who interact with Harness for general daily tasks should not, because it is not intended for everyday use.

Watch out — Installation from source requires manually allowing the build script, otherwise registration cannot complete. No other obvious issues were found.

The verdict — If I were a plugin developer, I would install it because it isolates the environment for experimentation and verification, but I would need to manually approve the build script step first.

What it is — Provides native LlmAdapter for DeepSeek Harness to access Command Code Go Plan models via /alpha/generate.

Who it is for — Go Plan users who want to use Command Code models in DeepSeek Harness through /alpha/generate. Users of the Provider API should choose standard OpenAI compatible endpoints.

Watch out — Sandbox test passed. Requires providing Command Code API Key. No obvious issues found.

The verdict — I would install it because it merges reasoning effort support from official catalog for Go Plan users in DeepSeek Harness, but the premise is having a Go Plan subscription.

What it is — Provide Tavily web search support for DeepSeek Harness as a web_search provider.

Who it is for — When using DeepSeek Harness in a profile to perform tasks, this plugin allows enabling Tavily search. Profiles that do not need additional search services do not need to install it.

Watch out — The sandbox test passes in a new profile and it registers with harness. No obvious issues found.

The verdict — I would install it because it provides a way to switch to Tavily without removing the package when keyless search is needed.

What it is — dsh-wechat bridges WeChat private chat to DeepSeek Harness, supporting bidirectional transmission of text, images, files, audio and video.

Who it is for — People who want to interact with DeepSeek Harness agent via WeChat private chat and handle approval cards are suitable for installing it. People who only want to use the DeepSeek Harness graphical interface can skip it, because they can continue relying on that interface.

Watch out — Sandbox test passed: installed in new profile and registered into the profile. No obvious issues found. It executes shell commands.

The verdict — If I were you, I would install it because it allows restoring the native DeepSeek Harness experience in WeChat.

What it is — A DeepSeek Harness terminal style plugin that provides terminal presentation, input interaction and session-related TUI capabilities.

Who it is for — Users who want interface presentation support when using DeepSeek Harness in terminal are suitable for installing this plugin. Users who do not need WeChat remote bridging can choose other plugins.

Watch out — Sandbox test shows it can be installed but the build script will be blocked by pnpm. No other obvious issues found.

The verdict — This plugin is worth installing for its session management, permission mode switching and WeChat remote control, but requires manual build script allowance from source.

What it is — DSH user plugin manager organizes plugins into a three-layer architecture view.

Who it is for — When you have many plugins to manage in DeepSeek Harness and need to view their sources and responsibilities, this plugin is suitable for installation. Users who do not use temporary Cordis plugins need not install it.

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

The verdict — I would install it because it provides a three-layer view and hot loading management, but only if you need to manage multiple plugins.

What it is — Conversational AI research assistant for scholarly literature, supporting multi-source paper search and folder-based favorites management.

Who it is for — Academic researchers who want to use DeepSeek Harness to describe research topics in conversation to obtain multi-source paper cards and save them in persistent folder-based favorites. Those primarily engaged in programming tasks unrelated to literature research, who do not need AI-assisted academic studies, can choose other plugins focused on file processing.

Watch out — Installation from source requires manual approval for build script execution; however, sandbox test passed with successful registration in a new profile and no obvious issues observed.

The verdict — I would not install it because it requires sourcing from GitHub and executing shell commands, preferring pre-built packages instead.

What it is — This is a desktop client for DeepSeek Harness that includes a bundled backend and tray resident.

Who it is for — Users who want an independent desktop window and tray resident when using DeepSeek Harness are suitable for installing this plugin. Users who do not use JavaScript are not suitable for installing this plugin.

Watch out — The installation automatically executes scripts. When installing from source, one needs to manually allow the build script first. No obvious pits found.

The verdict — If I were to install it, I would install it because the sandbox test passed and it registered into the profile.

What it is — Integrates DeepSeek Harness agents, sessions, and tools into the official OpenCode TUI frontend.

Who it is for — Users who want to integrate DeepSeek Harness agents, sessions, and tools into the official OpenCode TUI are suitable for installing this plugin. Users not using the OpenCode TUI terminal do not need to install this plugin.

Watch out — Tested successfully in a fresh profile and registered into the profile by harness. Supports text and image attachments but does not support PDF and other binary files. Some peripheral routes are schema-valid stubs.

The verdict — I would install it because it provides the bridge for integrating DeepSeek Harness into the official OpenCode TUI.

What it is — This is a cross-platform desktop client for DeepSeek Harness that starts with a double click on macOS, Windows, and Linux.

Who it is for — If you are working on web tasks with DeepSeek Harness on macOS and need a fixed window in the Dock, this is suitable. Users who prefer command-line only interfaces on Windows or Linux do not need it, as they can use the terminal directly.

Watch out — No obvious pitfalls found. Sandbox testing passed, registering successfully in a new profile.

The verdict — I would install it because it reuses existing profiles without extra dependencies.

What it is — dsh-proxy plugin forwards LAN ports to local DSH service and supports Basic Auth and WebSocket protocols.

Who it is for — If you run services in a DeepSeek Harness web profile and need LAN IP access with browser authentication, install this plugin.

You need an independent process for the proxy if you skip this plugin, as it requires source build.

Watch out — Install from GitHub source. Sandbox test passed in fresh profile and registered. No obvious issues found.

The verdict — I would install it because it runs as a DSH plugin that starts and stops with dsh web and has a settings page. This applies to web profile use.

What it is — DeepSeek Harness plugin: automatically fills context window, max tokens, name and input modalities for llm-pi-ai custom provider models from models.dev.

Who it is for — Users who need to complete metadata for models configured in llm-pi-ai settings area should install it. Users of non-custom providers do not need it.

Watch out — Tested successfully in a fresh profile. Will execute shell commands. No obvious issues found.

The verdict — I would install it because it provides offline indexing and optional refresh. This is worthwhile for llm-pi-ai custom model users.

What it is — This plugin simulates Codex-style prompts to help GPT-family models use tools reliably for selected routes.

Who it is for — When using gpt-5.6-* models for tool calling tasks in DeepSeek Harness, developers missing reliable tool simulation can install this plugin. If you want a plugin that runs independently without consuming DSH existing capabilities or prefer native tool behavior without extra support, you can skip it.

Watch out — In sandbox testing, the plugin installs successfully but its build script is blocked by pnpm, requiring manual approval of the build to complete registration. No other obvious issues found.

The verdict — I would install it because it provides tool simulation support for specific models without altering core DSH behavior, although the build requires manual approval to finish registering.

What it is — Provides a configurable 17-segment status bar for DeepSeek Harness to display live session status, model, context, tokens, TPS, cost estimates, jobs, and queue.

Who it is for — Users who need real-time token consumption rate and cost estimates when performing sessions in DeepSeek Harness composer. Users who do not use the settings page do not need it because defaults suffice.

Watch out — Sandbox test passed after installing in a fresh profile and registering with harness. No obvious issues found. Coexists with another similar plugin.

The verdict — I would install it because it allows users to maintain model price book for cost estimation without external services, but only for DSH versions 0.1.0-rc.5 and later.

What it is — Browser4 is an AI-native browser engine for autonomous agents, intelligent extraction, and large-scale web automation.

Who it is for — When using the browser4 plugin in DeepSeek Harness, it suits users who need web automation tasks. If users use non-PowerShell environments, they don't need it because it is written in PowerShell.

Watch out — Sandbox testing passed: it installs into a new profile and registers into the profile with Harness. It requires manually allowing the build script when installing from source. It will execute shell commands.

The verdict — I would install it because sandbox testing passed and it registers into the profile.