Introduction

The plugin-based architecture of DeepSeek Harness (DSH) allows developers to extend the system’s core capabilities through seams (interfaces). For scenarios that require web access, directly integrating an external search API is a common need. By registering a Web Search Provider, this plugin routes DSH’s web-search seam to the Tavily API and provides a visual configuration entry point, avoiding the complexity of manually writing Provider code.

What Is This

This plugin is maintained by libinghui55 and is a Tavily-based Web Search Provider. It connects DSH’s web-search seam interface to the Tavily API and generates a configuration card named tavily-search in the settings UI, supporting a toggle switch and API key management.

Core Features

  • Provider registration: Registers a Web Search Provider with the ID tavily and takes over the Harness web seam.
  • GUI configuration card: Provides a configuration interface named tavily-search under Settings -> Plugins.
  • Toggle control: Provides an on/off switch. When disabled, the Provider reports itself as unavailable and declines search requests.
  • Secure storage: The API key is stored through the Harness Credentials Service. It is not written to the settings file and is not echoed back to clients.
  • Multi-level resolution: Supports resolving the API key from literal configuration, an environment variable, or the credentials file.
  • Endpoint configuration: Supports configuring the Tavily API endpoint via baseURL (default: https://api.tavily.com).

Installation and Activation

This plugin is an npm package and is installed through DSH’s profile bundle mechanism.

  1. Ensure that the target profile already includes the web search seam (for example, the default web profile).
  2. Run the installation command:
dsh plugin --profile web add <path-to-dsh-tavily-search>

Typical Usage

After installation, the Provider can be invoked by the Harness.

  • GUI configuration: Go to Settings -> Plugins, expand tavily-search, enter the key in the API key field, and save.
  • YAML configuration: Control the state through a configuration file, for example, disabling the plugin:
web-search-tavily:
  enabled: false
  • API key configuration: The API key resolution priority is as follows:
    1. A literal apiKey field.
    2. Credentials Service (by default referencing the credential named TAVILY_API_KEY).
    3. The process environment variable TAVILY_API_KEY.

Applicable Scenarios and Notes

  • Use cases: Suitable for developers who need to integrate Tavily search into DeepSeek Harness quickly and prefer simple GUI-based configuration.
  • Environment variable conflicts: If TAVILY_API_KEY already exists in the process environment, the Credentials Service reports the key as inherited. In this case, the key input field in the GUI card is disabled (read-only) and cannot be changed in the UI. To modify it through the UI, store the key in the credentials file instead.
  • Permission security: The plugin runs with the permissions of the current DSH process. Before using it, review the source code and license.

Conclusion

This plugin simplifies the process of integrating Tavily search into DeepSeek Harness through its GUI and plugin-based mechanism.

  • Directory page: https://www.skillhub.cn/plugins/libinghui55/dsh-tavily-search
  • Source code: https://github.com/libinghui55/dsh-tavily-search