dsh-web-search

DeepSeek Harness agents that need to search the web or read public pages often lack a safe, governed channel. dsh-web-search fills that gap by consolidating web_search, web_fetch, and a constrained web_source tool into a single plugin-scoped boundary. Administrators pick a backend, store credentials, and test the draft in the settings panel — all without restarting DSH.

The core design centers on security boundaries. Five search backends are supported: self-hosted SearXNG, keyless Chinese Wikipedia, agent-oriented Tavily, traditional Brave Search for web and news, and Gemini Grounded Search with URL context. Each query is dispatched to exactly one selected provider; there is no silent fan-out or fallback quota spending. On the fetch side, only credential-free public HTTP(S) URLs are accepted. Loopback, link-local, private, and reserved destinations are rejected outright. Redirects are capped at five hops with revalidation at every step, binary bodies are discarded, and response payloads are limited to 2 MiB. web_source further restricts access to bounded range reads or a bounded set of exact source markers, capping output at 120,000 characters. API keys are resolved through the DSH Credential Store and appear only in provider-defined authorization headers; browser settings routes enforce exact same-origin writes and never return secret values.

Who is it for? If your team needs agents on the web but demands strict boundaries — especially if you prefer a self-hosted SearXNG instance, want to switch among multiple search backends, or require proxy and credential isolation to stay within a single plugin scope — dsh-web-search delivers a complete, security-first path from configuration to runtime.