dsh-websearch-stack

LIMITATIONS

Known limitations

- **Live services partially verified.** Tavily keyless and Parallel MCP verified live. Brave, TinyFish, Exa and SearXNG are not yet: they need API keys or a local instance. - **The chain is not editable from the web client.** The Plugins page renders a bundle's configuration card (the API keys here) but not a form for the bundle's own config fields: in `@deepseek-ai/dsh-client-ui-plugin-manager` 0.2.0-rc.2, `plugins.bundle.config` is rendered without the `form` prop, while `plugins.row.config` receives it. A `plugins.row.config` entry for the plugin's row could close this gap; until then, edit `$DSH_HOME/profiles/<profile>/cordis.patch.yml` and restart the profile (see [Configuration](#configuration)). - **Pinned seam, by design.** The bundle patch pins `web.searchProvider` to `websearch-stack`, because the base profile pins it to the DeepSeek provider, which is `available()` without a key. Consequence: with an empty chain `web_search` fails with `WEB_PROVIDER_CONFIGURED_UNAVAILABLE` instead of falling back to the native provider (see [Coexisting with the native DeepSeek provider](#coexisting-with-the-native-deepseek-provider)). - **No fetch.** Page fetching is handled by DSH's `dsh-web-fetch-http` provider, not this plugin. - **Not a sandbox.** The code runs inside the host process with its privileges, like every dsh plugin.