dsh-free-search
Web search across many engines with no API key.
Version 0.9.48 of dsh-free-search, last published 2026-11-13; the install command and the range come from its own manifest.
Install
dsh plugin add dsh-free-search writes one dependency line into the profile manifest; pnpm then unpacks it under $DSH_HOME/profiles/<name>/node_modules.
dsh plugin --profile web add dsh-free-searchCompatibility
dsh-free-search ships no engines.dsh entry, so nothing checks it against your CLI version at boot. Read the npm page before installing.
If two plugins fight
Adds search tools into @deepseek-ai/dsh-tools and peers dsh-client-ui-commands. With @liustack/modsearch installed you have two web-search providers registered; the model picks one, and the pick is not deterministic — keep one.
Who made it
Author: DDDMUC. Repository: https://github.com/DDDMUC/dsh-free-search. Package page: https://www.npmjs.com/package/dsh-free-search.
After install
It declares @deepseek-ai/cordis as a peer and renders a search tool in the tool list; after dsh plugin add dsh-free-search, dsh --profile web --dump-config lists the row that mounts it.
Files it touches
dsh-free-search routes whatever it persists through @deepseek-ai/dsh-settings under $DSH_HOME, and its own dependency line sits in $DSH_HOME/profiles/<name>/package.json.
Removing it
Removing dsh-free-search is the mirror command, dsh plugin --profile web remove dsh-free-search; the surface goes with it, and whatever it stored under $DSH_HOME stays until you delete it.
Common questions
Does it collide with @liustack/modsearch?
dsh-free-search is the one to keep here: It peers @deepseek-ai/dsh-tools and the command palette, so the provider is reachable from the UI; modsearch declares no peers at all.
What happens when dsh upgrades?
Nothing declares a version window for dsh-free-search: dsh --version tells you what you are running, and no check will tell you whether dsh-free-search matches it.