Browser & Web

What it is — ModSearch provides web search, X search, and page fetching capabilities for text models in DeepSeek Harness.

Who it is for — When using DeepSeek-V4-Flash for tasks requiring up-to-date information, it supplements web search capabilities. If you use a model with native web access, it is not needed.

Watch out — Installation requires browser login for the default engine or free API keys from alternatives. Sandbox test passed: works in fresh profile and registered. The plugin executes shell commands. No obvious issues found.

The verdict — I would install it because of the free default engine and automatic failover support.

What it is — The plugin provides Tabbit browser control capability for DeepSeek Harness.

Who it is for — When performing automation tasks with DeepSeek Harness that require browser integration, this plugin enables Tabbit control. It is not necessary if your DSH runs in a sandbox without local GUI Browser access, because this Skill does not make Tabbit automation available.

Watch out — Sandbox testing passed: installed in fresh profile and registered by harness. Static check indicates it can execute shell commands. From source install, the build script needs manual allowance first. Requires Tabbit browser version 1.9.0 or higher.

The verdict — I would install it because it handles Tabbit installation and Skill loading via background tasks, but only if local Tabbit GUI access is possible.

What it is — dsh-tabbit plugin integrates Tabbit Browser for DeepSeek Harness to provide tabbit-browser browser automation skills.

Who it is for — It is suitable when the agent needs web automation, information extraction or QA. Users who are already running Tabbit Browser locally can choose not to install it.

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

The verdict — I would install it because it allows the agent to directly control Tabbit Browser via tabbit-cli.

What it is — Adds free multi-engine web search with auto-failover and test tool to DeepSeek Harness.

Who it is for — If you use a gateway like opencode-go that does not support the web_search tool and need web search in DeepSeek Harness, this plugin enables agent networking. If your tasks do not require network search, you do not need to install this plugin.

Watch out — Sandbox test passed, successfully registered in a new profile. No obvious issues found.

The verdict — I would install it if I need to perform searches with gateways that don't support web_search, as it provides multi-engine auto-fallback.

What it is — dsh-web-search-pro provides 9 tools for multi-engine web search, platform search, caching, and Playwright rendering.

Who it is for — Users who need to search on GitHub, Bilibili, YouTube and other platforms can install this plugin. Users focused on local DeepSeek Harness management do not need this plugin.

Watch out — Configuration of exaApiKey and jinaApiKey is required. External dependencies such as Playwright and bili-cli must be installed. Sandbox test passed, no obvious issues found.

The verdict — I would not install it, because it is not a necessary tool.

What it is — Adds shared real browser plugin for DeepSeek Harness, enabling agent to drive visible native Electron window shared with humans for observation and takeover.

Who it is for — When performing web automation tasks with DeepSeek Harness agent that require human oversight, this plugin is suitable to install. If your tasks do not involve visible browser control, using headless solutions is sufficient.

Watch out — No obvious issues found. Sandbox test passed: installed in new profile and registered into profile. Self-hosts in plain dsh web environment without desktop shell.

The verdict — I will install it because it self-hosts on plain dsh web without requiring a desktop shell.

What it is — dsh-web-tools is a DeepSeek Harness plugin that integrates multi-provider web search and fetch, supporting Tavily, Exa, Firecrawl and others with native settings UI.

Who it is for — Users who need to call web_search and web_fetch tools during DeepSeek Harness responses are suitable for this plugin. For users who only need a single provider, this plugin is not necessary.

Watch out — Sandbox testing passed: the plugin was installed in a fresh profile and successfully registered as web.searchProvider. No obvious pitfalls found.

The verdict — I would install it because it provides quota display and API key health status checks.

What it is — DeepSeek Harness URL reader plugin that fetches any page and returns clean main content or Markdown.

Who it is for — When a DeepSeek Harness agent needs to read URLs into clean body text for analysis tasks, this plugin is suitable. Users who do not perform web fetching do not need it.

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

The verdict — I would install it if I were you because it supports offset continuation and 5-minute session cache, but only if the agent requires webpage reading for long content.

What it is — The dsh-annotate plugin lets users select browser elements directly and send structured visual feedback to the DeepSeek Harness Agent in the next turn.

Who it is for — When using DeepSeek Harness for Vibe Coding, if browser UI problems are hard to describe in plain text, this plugin can provide structured visual feedback. Users who do not need browser interface feedback or do not use Harness Agent do not need to install this plugin.

Watch out — Installing from GitHub source requires first manually allowing the build script. Tests show it can be installed but the build script was blocked, preventing DeepSeek Harness registration. No obvious pitfalls were found.

The verdict — I would install it because it provides structured browser element feedback to the DeepSeek Harness Agent, but only if the build script is manually allowed; otherwise, it cannot be properly registered.

What it is — dsh-browser provides browser runtime service and 9 interactive tools using Playwright chromium kernel and OpenCLI as local plugin dependencies.

Who it is for — When building plugins that need browser automation or web interaction capabilities in DeepSeek Harness, for example by injecting the browser service to power web-search-pro, this plugin can be used. It is not suitable for users who do not depend on browser runtime or OpenCLI, as it executes shell commands.

Watch out — Sandbox testing showed the build script for @jackwener/opencli@1.8.6 was blocked by pnpm, preventing automatic harness registration. Users must manually allow it to successfully install.

The verdict — Do not install it because the build script needs to be manually allowed first, otherwise registration will not complete.

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.

What it is — Integrates Tavily as web search provider for DeepSeek Harness web_search tool and provides a GUI settings card.

Who it is for — If you perform web search tasks in DeepSeek Harness that require up-to-date information, this plugin is suitable. If you prefer to manage the search provider via cordis.patch.yml without GUI cards, you don't need this plugin.

Watch out — Sandbox test passed: installed in a new profile and registered into profile. The web GUI card is hidden unless the web-search-tavily namespace is added to the WEB_SETTINGS_NAMESPACES list in dsh-host-apiproxy.

The verdict — I would install it because it allows GUI configuration of the API key and result count, though the card requires adding the namespace to the apiproxy allowlist.

What it is — This is an Exa web search plugin that supports anonymous MCP fallback.

Who it is for — If you need web search in DeepSeek Harness and want no API key configuration, this plugin is suitable. Users who prefer the official maintained Exa integration can skip installing this plugin, since the official package covers the core features.

Watch out — Sandbox testing passed. It can be installed and registered in a new profile. No obvious issues found.

The verdict — I would install it if the anonymous MCP search rate limits are acceptable, because it provides a feature missing from the official package.

What it is — This plugin provides real Chrome browser control for AI agents via Playwright MCP and embeds a live screenshot panel in the GUI.

Who it is for — When using DeepSeek Harness to develop AI agents for web navigation or form-filling tasks, this plugin is suitable due to real browser control and live GUI feedback. Users who perform only code-level browser simulation without needing visible operation displays may find alternative tools sufficient.

Watch out — Sandbox test passed after registration in a fresh profile. The system requires Google Chrome or Edge to be installed. The workspace needs to run npm install @playwright/mcp.

The verdict — I would install it for tasks requiring real visible browser control because it integrates with DeepSeek Harness for live feedback, but only if Chrome is available on the system.

What it is — Provides native browser tools for DeepSeek Harness, enabling per-agent isolated sessions, bounded snapshots, ref-based interactions, screenshots, and safe routing.

Who it is for — When an Agent needs to perform web navigation and data extraction via model calls, this plugin is suitable; pure-text Agents without web interaction needs do not require it.

Watch out — Tested successfully in a fresh profile where the plugin registers correctly. Agents complete Wikipedia browsing, search, and screenshot in about 15 seconds. It executes shell commands and may download a 200 MB Chromium cache on first use.

The verdict — I would install it because it allows Agents to safely route tasks to a browser using native tools.

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 — Drives the user's real browser through the local Kimi WebBridge daemon, providing tools for page navigation, input filling, screenshots and PDF export.

Who it is for — When using DeepSeek Harness agents to perform web automation tasks, this plugin provides support for real browser environment. If users prefer cloud-based browser services over local Kimi WebBridge daemon, they need not install this plugin.

Watch out — Sandbox testing passed in a fresh profile and it was registered by DeepSeek Harness. When installing from source, the build script needs to be manually allowed first. Certain build tool failures may cause plugin entries to remain in the profile configuration.

The verdict — I will not install it because it requires support from the local Kimi WebBridge daemon and may need manual configuration in some environments.

What it is — It mounts the hosted Exa search MCP endpoint through the dsh-mcp-client bridge and registers Exa tools as agent tools.

Who it is for — For agent tasks in DeepSeek Harness that require web search and fetch capabilities, this plugin supplies the necessary tools. If you already have your own search solutions or do not rely on external endpoints, you can skip it because it does not implement OAuth login.

Watch out — It passed sandbox testing and registered successfully in a new profile with no obvious issues. It supports anonymous use on the free tier.

The verdict — I would install it because it only adds tools via configuration patch without modifying the harness installation.

What it is — Integrates SearXNG as a web search provider into DeepSeek Harness agents.

Who it is for — This plugin suits users who run their own SearXNG instance and employ DeepSeek Harness agents for web information tasks. It is unsuitable for users who do not intend to deploy a local SearXNG instance.

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

The verdict — I will install it because it enables agents to perform web searches via a self-hosted instance instead of paid APIs.

What it is — dsh-s1 provides first-class s1_* tools for web research in DeepSeek Harness.

Who it is for — When using DeepSeek Harness for web research, this plugin can provide s1_* tool support. For users not running in a profile environment, it cannot be used.

Watch out — Sandbox test passed in a new profile. It requires S1_KEY to function. No obvious issues found.

The verdict — I would install it because it runs in-process with a bundled s1 skill.