@brilliant751/dsh-web-search-litellm

English | 中文

A LiteLLM /v1/search-backed web search provider for the DeepSeek Harness (dsh) web capability seam (ctx.web).

One search is one HTTP request to LiteLLM's search endpoint — no model turn, unlike the shipped DeepSeek Anthropic-compatible provider. It reuses your LiteLLM gateway and its virtual key, so chat and search go through the same proxy.

Install

dsh plugin --profile web add @brilliant751/dsh-web-search-litellm

Restart dsh web. The bundle declares dsh.bundle.patch, so dsh plugin add appends it to dsh.profile.bundles, which registers the litellm provider and selects it as the active search backend.

How it works

• Registers a WebSearchProvider with id litellm into ctx.web.
• Calls POST {baseURL}/search with { query, search_tool_name } and Authorization: Bearer <key>.
• Maps LiteLLM's results[] (title / url / snippet / date) into the seam's normalized sources[].
• The model-facing web_search tool is unchanged (@deepseek-ai/dsh-tool-web); results keep the native citation card.

Configuration

Defaults live in cordis.patch.yml:

Key	Default	Meaning
baseURL	https://your-litellm.example.com/v1	LiteLLM base; /search is appended. OpenAI-compatible base, not the Anthropic passthrough.
apiKeyEnv	DEEPSEEK_API_KEY	Credential reference, resolved per search through ctx.credentials (the Models page writes it), then the environment.
searchToolName	google	The LiteLLM search tool to invoke (see GET {baseURL}/search/tools).

Override any value from your profile's own cordis.patch.yml or a --patch overlay. A patch replaces a targeted row's whole config (it does not merge), so restate the complete config when overriding:

- insert:
    - id: web-search-litellm
      name: '@brilliant751/dsh-web-search-litellm'
      config:
        baseURL: https://your-litellm.example.com/v1
        apiKeyEnv: DEEPSEEK_API_KEY
        searchToolName: google

To switch back to the shipped DeepSeek provider, override web.searchProvider back to deepseek-official (or uninstall this bundle).

Credential resolution

1. A literal apiKey in the config (not recommended — prefer the credential store).
2. ctx.credentials resolving apiKeyEnv (the Web UI's Models/Web-search card writes $DSH_HOME/.credentials.yaml).
3. process.env[apiKeyEnv].

Security note

Installing this plugin runs its code with your permissions. It sends your LiteLLM key to the configured baseURL only. Point baseURL only at a gateway you trust.

License

MIT