dsh-web-search-order

By default, DSH web_search relies on a single search provider. When that provider times out, throws an error, or returns an empty result, the entire tool call fails with no fallback. dsh-web-search-order inserts an ordered fallback chain at that point: it strings together the multiple providers already registered on ctx.web (exa, deepseek-official, etc.) so that when one is unavailable, the next one is tried automatically. The model-side call shape, agent presets, and web_fetch remain untouched.

The plugin does not implement a search backend or manage credentials. It only sorts and chains the providers you have already installed. You set the order of preference, permanently exclude providers, and cap each attempt with an independent timeout budget (default 20 seconds). Every attempt races the budget deadline against caller cancellation and the provider response; whichever comes first wins, and a late-arriving result is discarded. If the entire chain fails, the raised error lists each provider result verbatim (401, missing key, etc.) so the root cause is immediately visible. A caller-initiated cancellation short-circuits with WEB_ABORTED, keeping the semantics unambiguous.

This is for teams that have registered multiple search services in their DSH deployment and want redundancy with minimal change: no model-side code edits, no custom routing logic, just a few config keys and search requests flow between providers automatically.